== Progress ==
* US LLVM Dev Mtg (4/6)
* Buildbots (TCWG-76 1/6)
- Fixing last bugs of the libcxx bot
- One last failure being looked at
* Background (1/6)
- Code review, meetings, discussions, etc.
- Meeting with Google/ARM/Qualcomm about Android+LLVM
* Two days off
== Plan ==
* Investigate last libcxx bug
* Move lab/office
Thanks for the reply, Will Newton.
Then can we expect the fix to be included for the official Android
toolchain 2014.11?
And, thanks for explaining the culprit of this bug, Jongsung Kim! :)
On Wed, Oct 29, 2014 at 9:00 PM, <linaro-toolchain-request(a)lists.linaro.org>
wrote:
> Send linaro-toolchain mailing list submissions to
> linaro-toolchain(a)lists.linaro.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.linaro.org/mailman/listinfo/linaro-toolchain
> or, via email, send a message with subject or body 'help' to
> linaro-toolchain-request(a)lists.linaro.org
>
> You can reach the person managing the list at
> linaro-toolchain-owner(a)lists.linaro.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of linaro-toolchain digest..."
>
>
> Today's Topics:
>
> 1. RE: Enabling back linker plugin for Linaro Android toolchain
> (Jongsung Kim)
> 2. Re: Enabling back linker plugin for Linaro Android toolchain
> (Will Newton)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 29 Oct 2014 11:26:30 +0900
> From: "Jongsung Kim" <neidhard.kim(a)lge.com>
> To: '???' <qkrwngud825(a)gmail.com>, <linaro-android(a)lists.linaro.org>,
> <linaro-toolchain(a)lists.linaro.org>
> Subject: RE: Enabling back linker plugin for Linaro Android toolchain
> Message-ID: <012f01cff31f$c01cea90$4056bfb0$(a)lge.com>
> Content-Type: text/plain; charset="UTF-8"
>
> The version-string from binutils-linaro looks to be blamed. It once was:
>
> GNU ld (crosstool-NG linaro-1.13.1-4.7-2013.04-20130415 - Linaro GCC
> 2013.04) 2.23.1
>
> and the linker plugin works with this version of Linaro prebuilt
> toolchain. Now it is:
>
> GNU ld (crosstool-NG linaro-1.13.1-4.8-2014.04 - Linaro GCC 4.8-2014.04)
> 2.24.0.20140311 Linaro 2014.03
> GNU ld (crosstool-NG linaro-1.13.1-4.9-2014.08 - Linaro GCC 4.9-2014.08)
> 2.24.0.20140801 Linaro 2014.08
>
> and the linker plugin is not supported:
>
> $ arm-linux-gnueabihf-gcc -flto -fuse-linker-plugin -o hello hello.c
> arm-linux-gnueabihf-gcc: error: -fuse-linker-plugin is not supported in
> this configuration
>
> Look into gcc/configure script. It uses the version of ld to determine
> whether ld supports linker plugin. It extracts the version by doing
> something like:
>
> $ arm-linux-gnueabihf-ld --version | sed 1q | sed -n -e 's,^.*[
> ]\([0-9][0-9]*\.[0-9][0-9]*.*\)$,\1,p'
>
> and it will extract the last 2014.03 or 2014.08. By using proper
> substitution expression like 's,^GNU ld (.*) \([0-9][.0-9]*\).*$,\1,p', the
> script may enable linker plugin.
>
> However, patching the script looks like a bad idea, because it doesn?t
> help handling the version of gold:
>
> GNU gold (GNU Binutils for Ubuntu 2.24) 1.11
> GNU gold (crosstool-NG linaro-1.13.1-4.7-2013.04-20130415 - Linaro GCC
> 2013.04 2.23.1) 1.11
> GNU gold (crosstool-NG linaro-1.13.1-4.8-2014.04 - Linaro GCC 4.8-2014.04
> 2.24.0.20140311 Linaro 2014.03) 1.11
> GNU gold (crosstool-NG linaro-1.13.1-4.9-2014.08 - Linaro GCC 4.9-2014.08
> 2.24.0.20140801 Linaro 2014.08) 1.11
>
> I couldn?t find a reasonable general expression to extract the version.
>
>
> From: linaro-toolchain-bounces(a)lists.linaro.org [mailto:
> linaro-toolchain-bounces(a)lists.linaro.org] On Behalf Of ???
> Sent: Monday, October 27, 2014 10:15 PM
> To: linaro-android(a)lists.linaro.org; linaro-toolchain(a)lists.linaro.org
> Subject: Enabling back linker plugin for Linaro Android toolchain
>
> I'm using Linaro Android toolchain's arm-eabi- for compiling my Android
> Linux kernel with LTO.
>
> The main benefits of my kernel is that it uses
> LTO(Link-Time-Optimizations).
> (Patches found here: https://github.com/andikleen/linux-misc)
>
> But now, it's broken with Linaro Android toolchains from 2014.09~
>
> Building Linux kernel with LTO requires Linker plugin with the toolchain.
>
>
> But for some reason, linker plugin is disabled with 2014.09 and 2014.10
> (Which I used from here :
> https://android-build.linaro.org/builds/~linaro-android/toolchain-4.9-2014.…
> https://android-build.linaro.org/builds/~linaro-android/toolchain-4.9-2014.…
> )
>
> LTO build works flawlessly with 2014.08.
>
> With 2014.09 and 2014.10, I get the following error :
> cc1: error: -fno-fat-lto-objects are supported only with linker plugin
>
> If I explicitly remove " -fno-fat-lto-objects " from the Makefile, the
> linker fails to link all of the object files.
>
>
> I would like to ask Linaro to enable back the Linker plugin support :)
>
> Thanks in advance..
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 29 Oct 2014 09:12:53 +0000
> From: Will Newton <will.newton(a)linaro.org>
> To: Jongsung Kim <neidhard.kim(a)lge.com>
> Cc: ??? <qkrwngud825(a)gmail.com>, linaro-android(a)lists.linaro.org,
> Linaro Toolchain <linaro-toolchain(a)lists.linaro.org>
> Subject: Re: Enabling back linker plugin for Linaro Android toolchain
> Message-ID:
> <CANu=DmhPdCGYw0=hCs9tmkbCU6hMLLMJnYS-u_JGz=
> p17Bgonw(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On 29 October 2014 02:26, Jongsung Kim <neidhard.kim(a)lge.com> wrote:
> > The version-string from binutils-linaro looks to be blamed. It once was:
> >
> > GNU ld (crosstool-NG linaro-1.13.1-4.7-2013.04-20130415 - Linaro GCC
> 2013.04) 2.23.1
> >
> > and the linker plugin works with this version of Linaro prebuilt
> toolchain. Now it is:
> >
> > GNU ld (crosstool-NG linaro-1.13.1-4.8-2014.04 - Linaro GCC 4.8-2014.04)
> 2.24.0.20140311 Linaro 2014.03
> > GNU ld (crosstool-NG linaro-1.13.1-4.9-2014.08 - Linaro GCC 4.9-2014.08)
> 2.24.0.20140801 Linaro 2014.08
> >
> > and the linker plugin is not supported:
> >
> > $ arm-linux-gnueabihf-gcc -flto -fuse-linker-plugin -o hello hello.c
> > arm-linux-gnueabihf-gcc: error: -fuse-linker-plugin is not supported in
> this configuration
> >
> > Look into gcc/configure script. It uses the version of ld to determine
> whether ld supports linker plugin. It extracts the version by doing
> something like:
> >
> > $ arm-linux-gnueabihf-ld --version | sed 1q | sed -n -e 's,^.*[
> ]\([0-9][0-9]*\.[0-9][0-9]*.*\)$,\1,p'
> >
> > and it will extract the last 2014.03 or 2014.08. By using proper
> substitution expression like 's,^GNU ld (.*) \([0-9][.0-9]*\).*$,\1,p', the
> script may enable linker plugin.
> >
> > However, patching the script looks like a bad idea, because it doesn?t
> help handling the version of gold:
> >
> > GNU gold (GNU Binutils for Ubuntu 2.24) 1.11
> > GNU gold (crosstool-NG linaro-1.13.1-4.7-2013.04-20130415 - Linaro GCC
> 2013.04 2.23.1) 1.11
> > GNU gold (crosstool-NG linaro-1.13.1-4.8-2014.04 - Linaro GCC
> 4.8-2014.04 2.24.0.20140311 Linaro 2014.03) 1.11
> > GNU gold (crosstool-NG linaro-1.13.1-4.9-2014.08 - Linaro GCC
> 4.9-2014.08 2.24.0.20140801 Linaro 2014.08) 1.11
> >
> > I couldn?t find a reasonable general expression to extract the version.
>
> This should be fixed in binutils-linaro-2.24-2014.11.
>
> > From: linaro-toolchain-bounces(a)lists.linaro.org [mailto:
> linaro-toolchain-bounces(a)lists.linaro.org] On Behalf Of ???
> > Sent: Monday, October 27, 2014 10:15 PM
> > To: linaro-android(a)lists.linaro.org; linaro-toolchain(a)lists.linaro.org
> > Subject: Enabling back linker plugin for Linaro Android toolchain
> >
> > I'm using Linaro Android toolchain's arm-eabi- for compiling my Android
> Linux kernel with LTO.
> >
> > The main benefits of my kernel is that it uses
> LTO(Link-Time-Optimizations).
> > (Patches found here: https://github.com/andikleen/linux-misc)
> >
> > But now, it's broken with Linaro Android toolchains from 2014.09~
> >
> > Building Linux kernel with LTO requires Linker plugin with the toolchain.
> >
> >
> > But for some reason, linker plugin is disabled with 2014.09 and 2014.10
> > (Which I used from here :
> https://android-build.linaro.org/builds/~linaro-android/toolchain-4.9-2014.…
> https://android-build.linaro.org/builds/~linaro-android/toolchain-4.9-2014.…
> )
> >
> > LTO build works flawlessly with 2014.08.
> >
> > With 2014.09 and 2014.10, I get the following error :
> > cc1: error: -fno-fat-lto-objects are supported only with linker plugin
> >
> > If I explicitly remove " -fno-fat-lto-objects " from the Makefile, the
> linker fails to link all of the object files.
> >
> >
> > I would like to ask Linaro to enable back the Linker plugin support :)
> >
> > Thanks in advance..
> >
> >
> > _______________________________________________
> > linaro-toolchain mailing list
> > linaro-toolchain(a)lists.linaro.org
> > http://lists.linaro.org/mailman/listinfo/linaro-toolchain
>
>
>
> --
> Will Newton
> Toolchain Working Group, Linaro
>
>
>
> ------------------------------
>
> _______________________________________________
> linaro-toolchain mailing list
> linaro-toolchain(a)lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-toolchain
>
>
> End of linaro-toolchain Digest, Vol 52, Issue 16
> ************************************************
>
I'm using Linaro Android toolchain's arm-eabi- for compiling my Android
Linux kernel with LTO.
The main benefits of my kernel is that it uses LTO(Link-Time-Optimizations).
(Patches found here: https://github.com/andikleen/linux-misc)
But now, it's broken with Linaro Android toolchains from 2014.09~
Building Linux kernel with LTO requires Linker plugin with the toolchain.
But for some reason, linker plugin is disabled with 2014.09 and 2014.10
(Which I used from here :
https://android-build.linaro.org/builds/~linaro-android/toolchain-4.9-2014.…https://android-build.linaro.org/builds/~linaro-android/toolchain-4.9-2014.…
)
LTO build works flawlessly with 2014.08.
With 2014.09 and 2014.10, I get the following error :
cc1: error: -fno-fat-lto-objects are supported only with linker plugin
If I explicitly remove " -fno-fat-lto-objects " from the Makefile, the
linker fails to link all of the object files.
I would like to ask Linaro to enable back the Linker plugin support :)
Thanks in advance..
Hi All,
There will be lab downtime in the month of November, and rather than
jeopardize the November quarterly binary toolchain release we've decided to
take some steps to ensure that it takes place on time.
The November binary toolchain quarterly release will contain some ARM64
erratum fixes. These are already in the Linaro GCC 4.9 2014.10 source
package release.
The November binary toolchain quarterly release will contain these fixes,
and will be delivered as planned, but will be based on the Linaro GCC 4.9
2014.10 package. We will not have a November Linaro GCC 4.9 2014.11 source
package release.
The December release will be the next Linaro GCC 4.9 source package release.
--
Ryan S. Arnold
Linaro Toolchain Working Group - Engineering Manager
www.linaro.org
cbuild2 benchmarking - TCWG-360 [2/10]
* Figured out how to cook my own OE images
* Started remembering how to build spec
libm exercising - CARD-1693 [2/10]
* Borrowed a usable Juno
* Found that lapack tests segfault on AArch64
* Ran linpack hpl, didn't observe it exercising libm much
** Haven't ruled out Bernie-error yet, though
Upstream - CARD-341 [1/10]
* Respun lowlevellock.h comments
Meetings/mail/etc [5/10]
* A lot of time (>3/10) in performance review and other annual ARM admin
* Some back and forth about difficulties of userspace access to ID registers
=Plan=
Get spec2006 working via my scripts
Find a good HPL libm exerciser
Spend a lot less time on ARM admin
== Progress ==
Further progress on GDB Tracepoints/Fast Tracepoints support on arm
[TCWG-480] [6/10]
-- Debugging and trying out some code enabling tracepoints in gdbserver
-- Research on past tracepoint patches and x86 vs arm architecture comparison
ARM/AArch64 GDB testsuite failures investigation [2/10]
Miscellaneous [2/10]
-- Meetings, Emails etc
-- Fix SSH configurations
-- Patch Scrolling
-- Hong Kong visa process
-- Multiple Dr visits due to continued sickness
== Plan ==
Further progress on GDB Tracepoints/Fast Tracepoints support on arm [TCWG-480]
Fix internet latency issues from lab hardware.
= Progress ==
* Short week was in vacation (22-24 October)
* Updated perf profile numbers for instruction count and documented my
analysis for Linaro compiler's O3 + LTO comparison on Aarch64 vs X86_64
(TCWG-544) (2/10)
* Misc [2/10]
emails, AMD meetings and 1-1 with inline manger.
1-1 with christophe.
== Plan ==
* Coremark benchmark and profiling.
Investigate trunk degradation for O3+ PGO + LTO and report.
== Progress ==
* Zero/sign extension elimination with widening types (TCWG-546 - 10/10)
- Re-wrote the pass from the results of experiments so far
- Fixed most of the regression failures
- 5 tests are still failing from C/C++/Fortran regression suite.
== Plan ==
* Continue with Zero/sign extension pass.
- Get bootstrapping for ARM and AArch64 working
- Fix remaining regression failures
- Add detail dumps
- Remove unnecessary copies (it is now being removed dead code
elimination pass)
- Get patch ready for upstream discussion
== This week ==
* GCC Modularization Project (5/10)
- Reviewed Re-Architecture GNU Cauldron videos by Andrew Macleod
- Reviewed tree/gimple source base
* Linaro bugzilla 602 - gcc 4.7.3 compiler internal error while building
hsail components (2/10)
- Resolved bug by determining that 4.7 compiler was assinging a
incorrect VFP register to a parameter
- Issue was fixed in 4.8 by adding call to arm_hard_regno_ok which
disallowed register
* vector Extensions Project (2/10)
- Preliminary design work on C++ classes and libvpx review
* Misc. (1/10)
- Conducted interview with Prathamesh Kulkarni
- Conference calls
== Next week ==
- GCC Modularization draft plan to TCWG group for review
- Understand status of Re-Architecture work by Andrew Macleod
- Further review of libvpx and vector extensions design work
=== Progress ===
SPEC Benchmarking [5/10]
. managed to run SPEC2k
. managed to run integer parts of SPEC2k6
. spec2xxx-report fails
. can't run full suite as LAVA Junos have insufficient disk
NEON error reporting bugs #403/#418 [3/10]
. ongoing mailing list discussions
vldN_lane patches [1/10]
. respun and committed
Misc [1/10]
=== Plan ===
Talk to Tejas @ ARM about AArch64 NEON loads/stores
Review prep
Move office
Day off at some point (likely Wednesday)
Short week, 2 days off
== Progress ==
* GCC trunk/4.9 cross-validation (2/10)
- committed testsuite patch to support forcing -mword-relocations
option when compiling testglue.c
* Neon intrinsics tests (2/10)
- committed the 1st batch (21 commits)
* AArch64 sanitizer
- libsanitizer internal data depend on the kernel headers version
used to build the toolchain, old_[gu]id_t type changed in 3.15.3.
- discussing the best way to address this
* Misc (2/10)
- calls, meetings
== Next ==
* 4.8 branch merge for next release
* GCC trunk/4.9 cross-validation
- investigate abi_check test, probably another testsuite harness
configuration issue
* AArch64 sanitizer
* Neon intrinsics tests update
* cbuild2:
- analyze previous results
- look at backport-test script + logs
== Progress ==
* Automation Framework (CARD-1378 1/10)
- Setting up Junos with ARM
* Toolchain (CARD-862 1/10)
- Some progress on fpu parser issue
- Produced a lot more work for the near future
* Buildbots (TCWG-76 4/10)
- Setting up a libc++ buildbot, working on reducing failures
- Some bots broken, bisecting
* Background (4/10)
- Code review, meetings, discussions, etc.
- Annual review
- More lab move planning
- EuroLLVM meetings and planning
== Plan ==
* US LLVM whole next week
The Linaro Toolchain Working Group (TCWG) is pleased to announce the 2014.10
release of the Linaro GCC 4.9 source package.
Linaro GCC 4.9 2014.10 is the seventh Linaro GCC source package release. It is
based on FSF GCC 4.9.2-pre+svn216130 and includes performance improvements and
bug fixes.
With the imminent release of ARMv8 hardware and the recent release of the
GCC 4.9 compiler the Linaro TCWG will be focusing on stabilization and
performance of the compiler as the FSF GCC compiler. The Linaro TCWG provides
stable[1] quarterly releases and monthly enginering[2] releases.
Interesting changes in this GCC source package release include
* Updates to GCC 4.9.2-pre+svn216130
* Backport of [AArch64] Define TARGET_FLAGS_REGNUM
* Backport of PR target/61565
* Backport of [AArch64] libitm: Improve _ITM_beginTransaction
* Backport of [AArch64] Fix *extr_insv_lower_reg<mode> pattern
* Backport of [AArch64] Use CC_Z and CC_NZ with csinc and similar instructions
* Backport of [AArch32] Implement and vectorize lceil, lfloor, lround optabs
with new ARMv8-A instructions
* Backport of [AArch64] Improve epilogue unwind info rth
* Backport of [AArch64] Add a mode to operand 1 of sibcall_value_insn
* Backport of [AArch64] Add a builtin for rbit(q?)_p8; add intrinsics and tests
* Backport of [AArch32/AArch64] Schedule alu_ext for Cortex-A53
* Backport of [AArch64] Remove varargs from aarch64_simd_expand_args
* Backport of [AArch64] Tidy: remove unused qualifier_const_pointer
* Backport of [AArch32/AArch64] Add scheduling info for ARMv8-A FPU new
instructions in Cortex-A53
* Backport of [AArch32] Convert FP mnemonics to UAL.
* Backport of [AArch32] Enable auto-vectorization for copysignf
* Backport of [AArch32][tests] Make input and output arrays 128-bit aligned in
vectorisation tests
* Backport of [AArch64] Add crtfastmath
* Backport of PR target/56846 libstdc++
* Backport of PR target/63209
* Backport of [Ree] Ensure inserted copy don't change the number of hard
registers
* Backport of [AArch64] Fix force_simd macro in vdup_lane_2
* Backport of [AArch32] Disallow -mfpu=neon for unsuitable architectures
* Backport of [AArch32] movmisalign<mode>_neon_load
* Backport of [AArch64] Add constraint letter for stack_protect_test pattern
* Backport of [AArch64] Auto-generate the "BUILTIN_" macros
Feedback and Support
Subscribe to the important Linaro mailing lists and join our IRC channels to
stay on top of Linaro development.
** Linaro Toolchain Development "mailing list":
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
** Linaro Toolchain IRC channel on irc.freenode.net at @#linaro-tcwg@
* Bug reports should be filed in bugzilla against GCC product:
http://bugs.linaro.org/enter_bug.cgi?product=GCC
* Questions? "ask Linaro":
http://ask.linaro.org/.
* Interested in commercial support? inquire at "Linaro support":mailto:
support(a)linaro.org
[1] Stable source package releases are defined as releases where the full Linaro
Toolchain validation plan is executed.
[2] Engineering source package releases are defined as releases where the
compiler is only put through unit-testing and full validation is not
performed.
Hi,
I start to use Linary AArch64 toolchain recently and just joined this maillist. I went through some of the archived threads but didn't read all of them. So bear me if I'm asking dumb question or old question which had been answered before.
For our use case, we are running the gdb client at early state of boot. So the ARMv8 target might be running into any EL and into either AArch64 or AArch32 state. My questions are:
1) Is the aarch64-none-elf-gdb.exe good for both AArch64 and AArch32 or I have to run the arm-none-eabi-gdb.exe if the target running in AArch32 state?
2) If the target is in AArch64 state, can I use the aarch64-none-elf-gdb.exe to load binary built for AArch32 to the target?
I'm really appreciated if anybody can help me on these two questions.
Thanks in advance,
StrongQ
cbuild2 benchmarking - TCWG-360 [3/10]
* A few small enhancements and bug-fixes
* Tried to run spec2006 on Juno, looks tricky
libm profiling - CARD-1693 [3/10]
* Pulled together lapack + blas
* Looked a bit at how it exercises libm on x86
* Tried to look at how it exercises libm on Juno, looks tricky
Meetings/mail/etc [4/10]
* Featuring some fun with backups and ARM performance review season
=Plan=
* cbuild2 benchmarking - keep chipping away at spec/juno
* libm profiling - attempt to assemble an AArch64 setup that works for me
* further performance review/corporate admin will take up extra time
this week, but should then fall back to normal levels
=Issues=
State of the setup on our Junos
== Progress ==
* Part way through integrating Cbuild2/Jenkins with Gerrit. (#1692,
8/10)
- Implemented functions to use the REST API to Gerrit via SSH.
- Integrated into build and test processes.
* Meetings and Misc (2/10)
- Ordered 10 Snapdragon boards
== Plan ==
* Finish Gerrit integration with Cbuild2 and Jenkins. (#1692)
- Find a way the buildslave user can use the SSH connection to Gerrit.
* Start merging the linaro branch in DejaGnu to master to get
ready for the next release.
* Start getting ready for the lab move, do what I can ahead of time.
== Issues ==
* Gerrit comments via REST strip out all newlines, so I need to
limit the message size after a test run.
= Progress ==
* Core mark benchmark and report for PGO and PGO + LTO (TCWG-544) (6/10)
Going by CPU cycles adding LTO gains in x86 and degrades in Aarch64 .
Looked at hot functions and examining assembly the code generation seems to
be same. X86_64 does alignment of code. Also branch misses decreased in
X86_64 compared to Aarch64 with -flto + -O3.
Also profiled for instruction counts on Aarch64 with linaro compiler. These
profiles say that we are executing less instructions with LTO and PGO for
Aarch64.
* PR 63173- Reproduced the issue and changed the test case to work with
trunk. Now Looks like someone else has a patch for it. (1/10). so will
work on other bugs.
* Misc [3/10]
Internal work, emails, AMD meetings and 1-1 with inline manger.
1-1 with Maxim, christophe and 1-1 with ryan
== Plan ==
* Coremark benchmark and profiling.
Investigate trunk degradation for O3+ PGO + LTO and report.
== leaves ==
Diwali holiday (22-24)
== Issues ==
* Still no network at home and will not be fixed before at least one week :(
== Progress ==
* GCC 4.9 2014.10 (8/10)
- Merged FSF 4.9 branch
- Released Linaro 4.9 2014.10
* Misc: (2/10)
- Various meetings.
== Plan ==
* Analyse some failures that occur only in --enable-release.
== Progress ==
Catch up with work after return from Eid ul Adha and Annual Holidays [7/10]
* Hong Kong visa application
* UPS repairs and office cleanup
* Catching up with work, gdb roadmap and open/running cards.
* Emails/Patch scrolling/Meetings etc
* Sick day off on Monday
GDB Tracepoints/Fast Tracepoints support on arm [TCWG-480] [3/10]
* Getting re-synced with code where I left.
== Plan ==
Further progress on GDB Tracepoints/Fast Tracepoints support on arm [TCWG-480]
Investigate possibility of AArch64 trace-point work without
availability of hardware.
Check for GDB status on ARM and AArch64 vs x86.
== Progress ==
* Zero/sign extension elimination with widening types (TCWG-546 - 9/10)
- Fixed ICEs and now can build the cross compiler and do the regression
testing with qemu
- some test-cases are failing due to condition that rely on overflow;
this need fixing.
- Bootstrapping on AArch64 still fails (but much later than previously).
- Verified CRC is optimized
* Improve block memory operations by GCC (TCWG-142 - 1/10)
- Looked at the changes since the card was drafted
== Plan ==
* Continue with Zero/sign extension pass.
== Progress ==
* GCC trunk/4.9 validation (CARD-647) (3/10)
- committed testsuite patch to test if -shared is supported
- forcing -mword-relocations flags when compiling testglue works on
my Ubuntu machines, but does not in the Compute Farm RHEL5 servers.
- investigating why, all the more as it made me incorrectly report
failures in the 4.9 branch
* Validation (2/10)
- compared cbuild2 schroot-test branch and master
the results of this manual run does not seem to match Jenkins results
* Neon intrinsics tests (1/10)
- fixed .exp harness to support parallelization
- looking at how to pre-support fp16, will probably skip it for now,
and add dedicated tests later
* AArch64 sanitizer (1/10)
- GCC trunk seems to need to cherry pick a sanitizer patch when
building using recent kernel headers
- tried to use Jenkins to build trunk and trunk+cherry-pick, but the
results are not consistent
needs more investigation
* Misc (3/10)
- calls, meetings, irc
== Next ==
* GCC trunk/4.9 cross-validation
- fix -mword-relocations support
- investigate abi_check test
* AArch64 sanitizer
* Neon intrisics tests update
* cbuild2:
- analyze previous results (mostly check the logs....)
- look at backport-test script + logs
Short next week: off Wednesday/Thursday
== Progress ==
* Respin of malloc single-thread optimizations (4/10, TCWG-436)
- Create a generic header, include AArch64 in series
* Further work on malloc app benchmark framework (4/10, TCWG-441)
- Cleaned up, improved reliability, added comments
- Committed to cortex-malloc.git
* Email, meetings, etc. (1/10)
* Upstream work (1/10, CARD-341)
- glibc patch review and pings
- Look into some bug reports and testsuite failures
== Issues ==
* Electricians and gas engineers turning off power/heating at various points
== Plan ==
* Hopefully get some resolution of single thread atomic stuff for glibc
--
Will Newton
Toolchain Working Group, Linaro
