# Progress #
* GDB 8.1 release. [2/10]
Triage regressions on aarch64 and arm.
* PR 21698. [3/10]
During the patch review, I doubt the patch fixes an invalid
python use in gdb. The GDB doc is quite unclear on how
that python api should be used. Ask the python api owner to
clarify.
* Misc, [5/10]
Two days travel to Manchester.
# Plan #
* GDB 8.1 release. Fix regressions.
--
Yao Qi
# Progress #
* TCWG-1125, ARMv8 tagged address support in GDB.
Finish v3, and committed. Done. [5/10]
* TCWG-1040,
Update my patches to remove the last use of MAX_REGISTER_SIZE.
No response, people are busy on release.
* GDB 8.1 release. [2/10]
PR gdb/21698. It is a regression. Fixed.
* Misc, [3/10]
# Plan #
* GDB 8.1 release, testing for ARM and AArch64.
--
Yao Qi
== Progress ==
o Linaro GCC/Validation
* 6.4 an 7.2 2017.11 snapshots deployed.
o LLVM ramp-up
* Buildbots babysitting:
- Investigate and reported upstream regressions
* Patch benchmarking job (TCWG-1306):
- Start to look at it
* Upstream BZ 32999:
- Still on-going
o Misc
* Various meetings and discussions.
== Progress ==
* GCC
- FDPIC
- debugged linker assert while building gcc target libs
- now debugging crash during program startup (self-relocation)
* GCC upstream validation:
- reported a couple of regressions
- a few more improvements to handle random infrastructure problems
- experimenting with new builders
* Infrastructure:
- updated Jenkins job for GCC upstream monitoring
* misc (conf-calls, meetings, emails, ....)
== Next ==
* GCC/FDPIC
* GCC upstream validation
The Linaro Toolchain Working Group (TCWG) is pleased to announce the 2017.11
snapshot of Linaro GCC 6 and 7 source packages.
o The GCC 7 series introduced an ABI change for ARM targets by fixing a bug
(present since GCC 5, see link below) that affects conformance to the procedure
call standard (AAPCS). The bug affects some C++ code where class objects are
passed by value to functions and could result in incorrect or inconsistent code
being generated. If the option -Wpsabi is enabled (on by default) the compiler
will emit a diagnostic note for code that might be affected by this ABI change.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77728
For an explanation of the changes please see the following website:
https://gcc.gnu.org/gcc-7/changes.html
o Linaro GCC 7 monthly snapshot[1] is based on FSF GCC 7.2+svn254792 and
includes performance improvements and bug fixes backported from mainline GCC.
The contents of this snapshot will be part of the 2018.02 stable[2] quarterly
release.
This snapshot tarball is available on:
http://snapshots.linaro.org/components/toolchain/gcc-linaro/7.2-2017.11/
Interesting changes in this GCC source package snapshot include:
* Updates to GCC 7.2+svn254792
o Linaro GCC 6 monthly snapshot[1] is based on FSF GCC 6.4+svn254791 and
includes performance improvements and bug fixes backported from mainline GCC.
This snapshot contents will be part of the next maintenance release.
This snapshot tarball is available on:
http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2017.11/
Interesting changes in this GCC source package snapshot include:
* Updates to GCC 6.4+svn254791
o 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
* Interested in commercial support? inquire at "Linaro support":
mailto:support@linaro.org
[1]. Source package snapshots are defined when the compiler is only
put through unit-testing and full validation is not performed.
[2]. Stable source package releases are defined as releases where the
full Linaro Toolchain validation plan is executed.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
* One day off
* One day sick and half one in the snow
== Progress ==
o Linaro GCC/Validation
* GCC 6.4 and 7.2 binary releases deployed
* 2017.11 snapshots:
- 6.4 and 7.2 ready to be deployed
o LLVM ramp-up
* Upstream BZ 32999:
- Struggled to construct the testcases which
produce the DAGs needed for a good coverage
- Re-working sub-vectors indexes logic to handle
these testcases.
o Misc
* Various meetings and discussions.
# Progress #
* TCWG-1040, [6/10]
Update my patches to remove the last use of MAX_REGISTER_SIZE.
Post the whole patch series as an RFC. There are 15 patches, but I
rewrote them in seven times. This version is quite satisfying.
Targeting to GDB 8.2. One patch can't be merged until 8.1 is
branched.
* TCWG-1125, ARMv8 tagged address support in GDB.
Writing v3. [2/10]
* Misc, [2/10]
# Plan #
* TCWG-1125,
* GDB 8.1 release. Testing for ARM and AArch64.
--
Yao Qi
== This Week ==
* TCWG-1234 (6/10)
- Using dfs to compute bb dist
- Reading through rest of PRE/SCCVN to better understand the infrastructure
* PR82808 (2/10)
- Trying to find an approach to pass parm_type from all callers.
- Martin posted a patch to address the parm_type issue.
* Misc (2/10)
- Meetings
- Filed PR83194, browsing through other PR's.
== Next Week ==
- Continue ongoing tasks
The Linaro Binary Toolchain
============================
The Linaro GCC 6.4-2017.11 Release is now available.
The GCC 6 Release series has significant changes from the GCC 5
release series. For an explanation of the changes please see the
following website:
https://gcc.gnu.org/gcc-6/changes.html
For help in porting to GCC 6 please see the following explanation:
https://gcc.gnu.org/gcc-6/porting_to.html
Download release packages from:
(sources) http://releases.linaro.org/components/toolchain/gcc-linaro/6.4-2017.11/
(binaries) http://releases.linaro.org/components/toolchain/binaries/6.4-2017.11/
Previous snapshots and release-candidates are at:
http://snapshots.linaro.org/components/toolchain/binaries/
Previous releases are at:
http://releases.linaro.org/components/toolchain/binaries/
A description of the arm and AArch64 target triples can be found at:
https://collaborate.linaro.org/display/TCWGPUB/ARM+and+AArch64+Target+Tripl…
Host Requirements
==================
Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release). This does not mean that
the toolchain will not work on other/older Linux distributions. See
the following for the life-time of Ubuntu LTS releases.
https://wiki.ubuntu.com/Releases
The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.
https://bugs.linaro.org/show_bug.cgi?id=1869
Package Versions
=================
Linaro GCC 6.4-2017.11
http://releases.linaro.org/components/toolchain/gcc-linaro/6.4-2017.11/
Linaro glibc 2.23 (linaro/2.23/master)
https://lists.gnu.org/archive/html/info-gnu/2016-02/msg00009.html
Linaro newlib 2.4-2016.03 (linaro_2.4-branch)
https://sourceware.org/ml/newlib/2016/msg00370.html
Linaro binutils 2.27 (users/linaro/binutils-2_27-branch)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=bin…
Linaro GDB 8.0 (gdb-8.0-branch)
https://lists.gnu.org/archive/html/info-gnu/2016-10/msg00007.html
Linaro toolchain package git branches are hosted at:
http://git.linaro.org/toolchain
NEWS for GCC 6 (as of Linaro GCC 6.4-2017.11)
==============================================
* Previous MinGW hosted version of Linaro GCC C preprocessor failed to
convert character set used for string, character constants, etc. This
is fixed in this release.
Linaro bugzilla #3040 : CC1 and cc1plus cannot convert UTF-8.
https://bugs.linaro.org/show_bug.cgi?id=3040
* The Linaro GCC 6.3-2017.05 snapshot added support for -mpure-code
option to ARMv7-M and ARMv8-M targets. This option ensures functions
are put into sections that contain only code and no data.
* The GDB version was upgraded from GDB 8.0.
* Previous versions of the Linaro GCC 6 toolchain, when -static
-E/—dynamic-list are passed to the linker, might create executables
with dynamic sections which aren’t supported by run-time. This was
exhibited in Perf Tools build system and has been fixed upstream and
backported into Linaro Binutils 2.27 branch.
Linaro bugzilla #2926 : Perf tools compiled statically for AArch64
with Linaro release 6.1 and later ones was not statically linked.
https://bugs.linaro.org/show_bug.cgi?id=2926
* The Linaro GCC 6.3-2017.03 snapshot fixed some ILP32 issues (TLS,
exception handling, …) and these have been incorporated into this
release.
* Previous versions of the Linaro GCC 6 toolchain were incorrectly
generating floating-point code for soft-float Linux targets
(arm-linux-gnueabi, and armeb-linux-gnueabi). This escaped detection
until recently because the soft-float targeted toolchains were
configured to use general-purpose registers for passing floating-point
values (which is what you would expect for soft-float toolchains) and
the intra-routine floating-code was not noticed.
The issue would only show up on targets that were run on hardware that
truly didn't have floating-point hardware where the kernel did not
trap and emulate floating-point routines. This has been solved in
Linaro GCC 6.3-2017.02-rc2 by configuring the toolchain (using
--with-float=soft) to generate code without any floating-point
instructions at all (-mfloat-abi=soft).
https://review.linaro.org/#/c/16968/2
This change should not break compatibility between existing binaries
compiled with these toolchains since the float-point parameter passing
ABI is still the same.
* A bug/regression in the compiler has been identified whereby the
target function that is invoked when calling a "weak" function
directly is the "strong" override, whereas when calling the function
via a pointer the "weak" implementation is used. This would be
noticed as inconsistent function invocation when invoking directly vs.
invoking via function pointer. This issue only affected 32-bit arm
targets. This regression has been fixed upstream and backported into
Linaro GCC 6.3-2017.02-rc2.
GCC PR target/78253: [5/6/7 Regression] [ARM] call weak function
instead of strong when called through pointer.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78253
Linaro bugzilla #2562: ARM GCC 5.2 call weak function instead of
strong when called through pointer
https://bugs.linaro.org/show_bug.cgi?id=2562
* MS Windows does not support symlinks and the MS Windows archive
extractor does not properly deep copy the symlink target
files/directories into the symlinked directory structure when
unpacking the toolchain archive. This causes problems with missing
dependencies when using the Linaro mingw toolchains, as identified in
the following bugs:
https://bugs.linaro.org/show_bug.cgi?id=2684https://bugs.linaro.org/show_bug.cgi?id=2192https://bugs.linaro.org/show_bug.cgi?id=2762
This has been solved by copying files rather than using symlinks when
the mingw targetted toolchain archives are created.
https://review.linaro.org/#/c/16415/
* Users of Linaro's toolchain have encountered problems when building
projects with Autotools (specifically libtool):
https://bugs.linaro.org/show_bug.cgi?id=2764
The Linaro binary toolchain release contained files with a .la suffix
as artifacts of the toolchain build process. These .la files are
helper files for libtool, but unlike a gcc install tree, they are not
position independent and contain full paths. Since these artifacts
contain absolute paths they can actually mislead user invocation of
libtool into not finding required libraries (because they reference
the build tree, not the install location) and hence breaking Autotools
builds. These *.la file artifacts have been removed from Linaro
toolchain binaries because they are unnecessary for users.
* The Linaro GCC 6.3-2017.01 snapshot added further enablement for
ARMv8-M and these have been incorporated into this release.
* Compiling and statically linking some SPEC2006int tests against
tcmalloc have been failing due to a problem with glibc's memory
allocator function overrides. This was fixed upstream:
https://sourceware.org/bugzilla/show_bug.cgi?id=20432
Backported into Linaro glibc 2.23:
commit 058b5a41d56b9a8860dede14d97dd443792d064b
Author: Florian Weimer <fweimer(a)redhat.com>
Date: Fri Aug 26 22:40:27 2016 +0200
malloc: Simplify static malloc interposition [BZ #20432]
* Host binaries for x86_64 linux hosts now have symbols and debug
information stripped in order to reduce the size of the toolchain
binary archives. This reduces the archive size from 1.5G to 600M for
aarch64-linux-gnu target with the gcc-6-branch.
* The GDB version was upgraded from GDB 7.11 in the Linaro GCC
6.1-2016.08 release to GDB 7.12 in the Linaro GCC 6.2-2016.11 release.
* The Linaro GCC 6.2-2016.10 snapshot added AArch32 support for ARMv8.2
and ARMv8m, as well as some AArch64 fixes for ARMv8.2, and bug fixes
merged from FSF GCC 6.2. This is available in the binary toolchain as
of Linaro GCC 6.2-2016.11.
* Basic tuning support for the Qualcomm qdf24xx was added to the Linaro
GCC 6.2-2016.10 snapshot and is available in the binary toolchain as
of Linaro GCC 6.2-2016.11.
* IFUNC was disabled for baremetal targets, as it was causing test-suite
failures, and is presently a Linux only feature.
* The gold linker was added to this binary release.
* Backported malloc_lock fix into Linaro newlib 2.4.
commit 2665915cfc46aa6403bb2efd473c523d3167e0cb
Author: Andre Vieira (lists) <Andre.SimoesDiasVieira(a)arm.com>
Date: Thu Jun 16 12:23:51 2016 +0100
Re-enable malloc_lock for newlib-nano
* Backported rawmemchr patch into Linaro newlib 2.4.
commit e7b1ee2ea6aa3ee1da41976407410e6202a098c5
Author: Wilco Dijkstra <Wilco.Dijkstra(a)arm.com>
Date: Thu May 12 16:16:58 2016 +0000
Add rawmemchr
* Backported strlen fix when using Thumb-2 and -Os -marm into Linaro
newlib 2.4.
commit 5c02bcc086a96b174e1b9e1445a4a1770070107a
Author: Thomas Preud'homme <thomas.preudhomme(a)arm.com>
Date: Wed May 11 17:18:48 2016 -0400
Fix strlen using Thumb-2 with -Os -marm
* Backported fix for semihosting ARM when heapinfo not provided by
debugger into Linaro newlib 2.4.
commit 5c9403eaf40951f8a4f55ed65f661b485ff44be7
Author: David Hoover <spm2(a)dangerous.li>
Date: Thu Apr 21 07:12:24 2016 +0200
Fixed semihosting for ARM when heapinfo not provided by debugger.
* Merged latest FSF glibc release/2.23/master into Linaro glibc 2.23.
* Backported __ASSUME_REQUEUE_PI check Linaro glibc 2.23 branch.
commit 2d20c3bf918cd94ebd4106693adb3a5c9272baba
Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org>
Date: Tue May 17 10:16:39 2016 -0300
Add runtime check for __ASSUME_REQUEUE_PI (BZ# 18463)
* Backported removal of __ASSUME_SET_ROBUST_LIST from Linaro glibc 2.23
branch.
commit bb8f09d72756186a3d82a1f7b2adcf8bc1fbaed1
Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org>
Date: Mon May 16 19:01:10 2016 -0300
Remove __ASSUME_SET_ROBUST_LIST
* Backported removal of __ASSUME_FUTEX_LOCK_PI from Linaro glibc 2.23
branch.
commit e48b4e7fed0de06dd7832ead48bea8ebc813a204
Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org>
Date: Mon May 16 10:35:25 2016 -0300
Remove __ASSUME_FUTEX_LOCK_PI
* Merged latest FSF binutils-2_27-branch into
linaro_binutils-2_27-branch.
* The libwinpthread DLL is now copied into the host bin directory to
satisfy mingw package dependencies.
* Backported GNU Linker fix.
commit fbc6c6763e70cb2376e2de990c7fc54c0ee44a59
Author: Nick Clifton <nickc(a)redhat.com>
Date: Tue Aug 23 09:45:11 2016 +0100
Fix seg-fault in ARM linker when trying to parse a binary file.
* Backported GNU Assembler fix for PR 20364
commit 5fe7ebe5ab43750abf8f490b785d99a1e598e7fd
Author: Nick Clifton <nickc(a)redhat.com>
Date: Fri Aug 5 10:37:57 2016 +0100
Fix the generation of alignment frags in code sections for AArch64.
https://sourceware.org/bugzilla/show_bug.cgi?id=20364
* Performance related backports from the following snapshots have been
included: Linaro GCC 6.1-2016.06, Linaro GCC 6.1-2016.07, Linaro GCC
6.1-2016.08, Linaro GCC 6.2-2016.09, Linaro GCC 6.2-2016.10, Linaro
GCC 6.2-2016.11, Linaro GCC 6.2-2016.12, Linaro GCC 6.3-2017.01,
Linaro GCC 6.3-2017.02, Linaro GCC 6.3-2017.03, Linaro GCC
6.3-2017.04, Linaro GCC 6.3-2017.05, Linaro GCC 6.3-2017.06, Linaro
GCC 6.4-2017.07, Linaro GCC 6.4-2017.08, Linaro GCC 6.4-2017.09 and
Linaro GCC 6.4-2017.10 .
See the following Linaro GCC snapshots:
http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.1-2016.06/http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.1-2016.07/http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.1-2016.08/http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.2-2016.09/http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.2-2016.10/http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.2-2016.11/http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.2-2016.12/http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.01/http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.02/http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.03/http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.04/http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.05/http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.06/http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2017.07/http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2017.08/http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2017.09/http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2017.10/
Contact Linaro
===============
File bugs at http://bugs.linaro.org
For Linaro member support see http://support.linaro.org
For Linaro community support email linaro-toolchain(a)lists.linaro.org
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
* 2 days off (Internal Training)
== Progress ==
o Linaro GCC/Validation
* Final GCC 5.5 release deployed and announced
* GCC 6.4 and 7.2 deployed
* 2017.11 snapshots on-going (branch merges done)
o LLVM ramp-up
* Upstream BZ 32999:
- Addressing upstream comments.
* Upstream BZ 35272:
- Analysed and commented upstream.
o Misc
* Various meetings and discussions.
== Plan ==
o Continue on on-going LLVM Bugs.
o Wednesday off
# Progress #
* TCWG-1040, [4/10]
Update my patches to remove the last use of MAX_REGISTER_SIZE.
Commit my 1/6 patch series. Prepare 2/6 patch series. Need to be
sync'ed with GDB 8.1 release.
* TCWG-1159, [4/10] GDB flexible target description conversion.
Commit patch for tic6x, and ready to post patches for nios2.
* Run GDB testsuite with CLANG. [1/10]
Commit my patches, but leave some controversial patches in my tree.
Now, I get some reasonable GDB test result with clang.
* Upstream patches review. [1/10]
Approved four Alan's patches.
# Plan #
* ARMv8 tagged pointer support in GDB.
* Update my patches to remove the last use of MAX_REGISTER_SIZE.
--
Yao Qi
== Progress ==
* GCC
- FDPIC: hitting a linker assert while building gcc target libs
* GCC upstream validation:
- reported a few regressions, fixed a couple of obvious errors
- struggling with ST-internal infrastructure difficulties
* Infrastructure:
- looking at ABE & building a native toolchain from a manifest
* misc (conf-calls, meetings, emails, ....)
- became 1 year older :)
== Next ==
* GCC/FDPIC
* GCC upstream validation
== This Week ==
* PR82665 (3/10)
- Submitted patch upstream
- Blocked on POINTER_DIFF_EXPR patch by Marc Glisse.
* PR82808 (1/10)
- Submitted another fix but was rejected by Richard.
* TCWG-1234 (4/10)
- Tried tweaking with register allocator, but to no effect
- Trying to think about possible approaches for stage-3 fixes.
* Misc (2/10)
- Meetings
- Managed to get autofdo working
== Next Week ==
- Continue ongoing tasks
== Progress ==
* GCC
- FDPIC: rebased binutils patches, debugging CI loop.
* GCC upstream validation:
- iterating on qemu/sanitizers problems.
Found a bug in arm sanitizer libs, already fixed upstream.
Requested a new merge in GCC.
- reported a few regressions
* Infrastructure:
- looking at ABE & building a native toolchain from a manifest
* misc (conf-calls, meetings, emails, ....)
- started looking at hcqc
== Next ==
* GCC/FDPIC
* GCC upstream validation
# Progress #
* TCWG-1040, [4/10]
Update my patches to remove the last use of MAX_REGISTER_SIZE.
Get everything in shape. Post my 1/6 patch series.
* TCWG-1159, [4/10] GDB flexible target description conversion.
Post patch for tic6x, and write the patch for nios2.
* ILP32 GDB. [1/10]
Chat with Maxim, triage some test failures.
* Open GCC PR 83010.
AArch64 GCC doesn't generate DW_AT_location for TLS variable. It
causes some GDB test failures. CLANG+GOLD can correctly generate
DW_AT_location.
* Run GDB testsuite with CLANG. [1/10]
Post three patches to GDB testsuite to compile test cases with CLANG.
# Plan #
* TCWG-1125, ARMv8 tagged address support in GDB.
--
Yao Qi
Hi Linaro Team,
I'm currently using toolchain
gcc-linaro-7.1.1-2017.08-x86_64_arm-eabi.tar.xz
<https://releases.linaro.org/components/toolchain/binaries/latest/arm-eabi/g…>
to
develop my bera-metal programs.
My compile option is "-marm -march=armv7-a -mtune=cortex-a9 -mlittle-endian
-mfloat-abi=hard -mfpu=neon"
I found an issue, when I use memcpy, and if the DEST or SOURCE address is
not 4 bytes aligned, the system hangs.
It seems that this toolchain doesn't support using hard float and NEON ?
My question is does this toolchain support hard float and NEON in the
newlib C library?
If I want to use hard float and NEON, how can I do that?
Your reply is more appreciated!!
Over the last couple of months arm64 community and us have tested various aspects of ILP32 toolchain and, while most of toolchain works as expected, several features are still missing. Most of the work left is on GDB side, especially using LP64 GDB to debug ILP32 applications.
1. [GCC] GCC sanitizers (ASAN, UBSAN) are not supported for ILP32.
-- TCWG is working on implementing sanitizer support for ILP32.
2. [GLIBC] LP64 glibc libthread_db does not support ILP32. This causes failures when LP64 GDB is trying to debug ILP32 threaded application. It is expected by users to be able to use LP64 GDB to debug ILP32 applications (LP64 AArch64 GDB can successfully debug AArch32 applications already!).
-- Steve, do you plan to work on adding libthread_db support for ILP32?
3. [GDB] Handle ILP32 siginfo layout. Kernel siginfo layout is different between LP64 and ILP32.
4. [GDB] Inferior call passing pointer argument. GDB may need update to handle 32-bit pointer vs 64-bit pointer.
5. Handle shared libraries. GDB needs to read a linked list out of the inferior, and that list is about the libraries loaded already. LP64 and ILP32 may have different layouts.
6. [GDB] GDB resolves ifunc functions, needs to read auxv (HWCAP) from the inferior. auxv is different on LP64 and ILP32.
7. [GDB] Gdbserver support for ILP32.
--
Maxim Kuvyrkov
www.linaro.org
== This Week ==
* TCWG-1234 (2/10)
- Came up with another fix which works on my test-case but not on
actual regression
* PR82808 (2/10)
- Modified patch based on upstream suggestions.
* PR82665 (4/10)
- Untested fix
* Misc (2/10)
- Meetings
- Reading ipa mod/ref paper
- Looked at autofdo
== Next Week ==
- Continue ongoing tasks
== Progress ==
o Linaro GCC/Validation
* GCC 6 and 7 2017.11 RC1 deployed
* Fixed Binutils branch used for 5.5 release
* Investigate and fixed Python3 issues in release notes script
(patch under review)
o LLVM ramp-up
* Upstream bug 32999:
- Still tracking corner cases
* Looking at zero/sign-extension elimination status
o Misc
== Plan ==
o Release handover
o LLVM tasks (Bug 32999, sign-extension)
Hi all,
I just upload an sysroot image for ILP32 meant to be used on both testing
and development on dev-01.tcwglab [1]. It is based on out current ILP32
GCC 7 sysroot plus some tools and it is meant to easier development and
testing. It should have all native required tools for GNU development:
glibc 2.27 (arm/ilp32 branch)
gcc 7.2.1 (linaro/gcc-7-branch)
binutils 2.28.2 (linaro_binutils-2_28-branch)
gmp 6.1.2
mpfr 3.1.6
mpc 1.0.3
coreutils 8.28
bash 4.4.12
gnumake 4.2 (plus a patch to fix glob usage on glibc 2.27)
gawk 4.2
perl 5.26.1
textinfo 6.5
bison 3.0.3
m4 1.4.18
libtool 2.4.5
flex 2.6.4
tcl 8.6.7
expect 5.45.3
dejagnu 1.6
sed 4.4
diffutils 3.6
tar 1.29
gzip 1.8
finutils 4.6.0
I could build and check glibc and binutils and bootstrap gcc. The binutils
and gcc tests are working (dejagnu/expect/tcl is installed).
To actually get a working VMs to run ILP32 you need a kernel built with different
branch than either canonical Linus tree or linux stable. Easier way is to use
Maxim's automated script to start a qemu aarch64 instance on r1-a7:
$ WORKSPACE=`pwd` bash -x ~maxim.kuvyrkov/src/jenkins-scripts/start-container-qemu.sh \
--weight 2 --node r1-a7 --arch arm64 --distro xenial --task test --prefix ilp32_ \
--kernel_url https://people.linaro.org/~maxim.kuvyrkov/norov-Image --initrd_url \
https://cloud-images.ubuntu.com/releases/16.04/release/unpacked/ubuntu-16.0… \
--session-name ilp32-$USER --newuser $USER --cp_file ~/.ssh/authorized_keys
You can then log in the machine as usual ('ssh -P r1-a7.aus-colo') and download
the sysroot from dev-01.tcwglab. Just uncompress it and issue the usual
chroot command:
$ mkdir aarch64-linux-gnu_ilp32/proc; sudo mount -t proc proc aarch64-linux-gnu_ilp32/proc
$ mkdir aarch64-linux-gnu_ilp32/sys; sudo mount -t sysfs sys aarch64-linux-gnu_ilp32/sys
$ mkdir aarch64-linux-gnu_ilp32/dev; sudo mount -o bind /dev aarch64-linux-gnu_ilp32/dev
$ sudo chroot aarch64-linux-gnu_ilp32
A useful package missing is GDB and python, I plan to get them built and I will
update the image on dev-01.tcwglab during this week.
[1] /home/tcwg-buildslave/public_html/images/ilp32/aarch64-linux-gnu_ilp32.tar.bz2
