[TCWG-1375] Make sure MCSubtargetInfo is passed through to
ARMAsmBackend functions
Spent most of the week working on this and follow up patches. Have
submitted a patch for the most important functions. Nearly have one
ready for the correct Nop encoding, this is more complicated as Nops
can be used as padding.
[Plans]
In office Monday Tuesday only.
Progress [TCWG-1375]
Planned Absences:
- At ACCU conference Wednesday - Friday [Holiday]
- At Euro LLVM following Monday Tuesday
[VIRT-198 # QEMU: SVE Emulation Support ]
Cleaning up patches and fixing RISU failures.
Most of these have thankfully been errors in
last week's first pass reordering of the
sve_access_check. Typically wrt when we find
the address of a register vs the location of
the check vs assert_fp_access_checked.
[Upstream]
Examined a bug affecting aa64 guest on ppc64 host,
but only when using gcc 4.8.5 and not gcc 7.2.
Fixed; in the end a minor typo on the code,
but highly annoying to track down.
r~
o 1 day off
== Progress ==
o LLVM
* Buildbots babysitting:
- Investigate LNT failure due to virtualenv and pip versions (Now fixed).
* Working on LLVM benchmarking job
o Misc
* Various meetings and discussions.
Progress: (short week, 2 days)
* VIRT-65 [QEMU upstream maintainership]
+ email/code review/etc catchup following holiday
+ the usual run of admin work for the release process for rc2
+ investigated a problem where in 'icount' mode we weren't
firing timer interrupts in a timely manner; with assistance
from Paolo, tracked down the cause and sent a patch
(https://bugs.launchpad.net/qemu/+bug/1754038)
+ investigated a problem with v7M emulation reported by the LITE team;
this turned out to be a combination of a known limitation combined
with a badly worded warning message; sent QEMU patch which rewords
the message so it's clearer that it's telling you that you're running
into the limitation.
+ tracked down why aarch64 guest binaries run in icount mode on
a 32-bit host misbehave; I have a working but slightly ugly patch
which I'll send out next week unless somebody has a neater approach
thanks
-- PMM
Note1: working for Linaro every other week
Note2: had some important work to do on GCC this week so I'll do some LLVM
work next week as well to catch up
=== Work done during this LLVM+GCC week ===
* LLVM PR34170 (crashes with inline asm with double output operand in GPR):
upstream review
+ finish patch and submit for upstream review
=== Plan for next week (week 12) ===
* (maybe) follow-up patch for PR34170 to also support case with several
output operands
* investigate failure to build clang in shared lib mode with gcc
o 1 post-connect day off
== Progress ==
o GNU Release transition
* Supported Mark for 2018.04 RCs
o LLVM
* Catching-up on devpt (TCWG-1286, ...)
* Benchmarking job for LLVM
* Buildbots babysitting
o Misc
* Various meetings and discussions.
* HK18 debriefing
Progress:
[VIRT-198 # QEMU: SVE Emulation Support ]
Rebasing and addressing feedback from v2 posting.
- Finished first pass moving sve_access_check
after any checks for over decode.
- Still lots of cleanup to do across the 70 patches.
[Upstream]
Fixed a target/hppa bug affecting glibc 2.27.
Fixed a tcg optimization bug affecting high-part multiply.
r~
[LLVM]
- Submitted fix for PR36542, tracked down problem to LLVM not
considering the target triple of the MachineFunction when relaxing
branch instructions. [TCWG-1375].
- A lot of investigation of a difference in inline assembly between
GCC and LLVM, reviewed and approved upstream patch D44815.
- Review of upstream changes to support Short Thunks in LLD, managed
to find a problem in algorithm and provided a solution. Looks like
this could be approved soon.
- Review of BFD and Gold patches for my PR on missing support for
R_AARCH64_TLSLE_LDST family of relocations. I now need to implement
these in LLD.
[TCWG]
Some post connect note taking and writing up.
[Plans]
- Continue work on PR36542, address any review comments.
- Implement support for R_AARCH64_TLSLE_LDST family in lld.
- Get back to building Android with LLD.
Friday 30th and Monday the 1st are public holidays in UK.
The Linaro Binary Toolchain
============================
The Linaro GCC 6.4-2018.04-rc1 Release-Candidate 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-candidate packages from:
(sources) http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2018.04-rc1/
(binaries) http://snapshots.linaro.org/components/toolchain/binaries/6.4-2018.04-rc1/
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-2018.04-rc1
http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2018.04-rc1/
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.1 (gdb-8.1-branch)
https://lists.gnu.org/archive/html/info-gnu/2018-01/msg00016.html
Linaro toolchain package git branches are hosted at:
http://git.linaro.org/toolchain
NEWS for GCC 6 (as of Linaro GCC 6.4-2018.04-rc1)
==================================================
* 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,
Linaro GCC 6.4-2017.10, Linaro GCC 6.4-2018.01 and Linaro GCC
6.4-2018.03 .
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/http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2018.01/http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.4-2018.03/
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.
Progress:
* VIRT-65 [QEMU upstream maintainership]
+ raspi3: came up with plausible fix for sd controller model that makes
Linux driver work. Unfortunately it's pure guesswork since there's
no public documentation for the hardware :-(
+ drafted a blog post describing booting Linux on the raspi3 model
(for publication once we've got the sdcard fix in master)
+ tagged 2.12.0 rc0 (first release candidate), various other release work
* VIRT-164 [improve Cortex-M emulation]
+ a little more progress with the stack-limit checking feature
thanks
-- PMM
Hello
Can you recommend Cross GCC for Windows for
armv7a-vfp-neon-oe-linux-gnueabi
-march=armv7-a, -mfloat-abi=softfp, -mfpu=neon
Qualcomm ARM Cortex A7 MDM9x07&MDM9628
The device is Quectel EC20 GSM Module
Best regards
Georgi Angelov
Progress:
* VIRT-65 [QEMU upstream maintainership]
+ raspi3 board: tested with a Debian kernel, and fixed and sent
patches for various issues that were causing it to panic.
Unfortunately there's a more tricky issue with the sd controller
still that means it doesn't boot yet...
+ bug investigation week:
- LP:1748434: wrong logic for ICC_PMR and ICC_RPR accesses by NS code
when the GICv3 emulation has security extensions enabled. Sent patch.
- LP:1751674: segfault doing a VM memory dump on vexpress-a9. This is
a combination of user error and a longstanding bug where the GICv2
crashes if you try to read its banked-per-CPU registers from a context
that isn't a guest CPU (like the monitor or the gdbstub)
- LP:1755479: confirmed that crash when using -icount is one that has
been fixed by a patch from Pavel that was lurking in a record/replay series
+ handling all the merge requests for softfreeze
* VIRT-164 [improve Cortex-M emulation]
+ started to look at implementing the stack-limit checking feature
thanks
-- PMM
Note: working for Linaro every other week
=== Work done during this LLVM week ===
* finish slides for bswap/store merging passes presentation in hacker room
at Connect HK2018
* Continue working on fix for PR34170 / TCWG1137 (cannot select truncate in
ARMv7 backend):
-> better understanding of generation of ISD node for inline asm, finally
seeing a way forward
=== Plan for next Linaro week (week 12) ===
* Linaro connect
If time permits:
* finish fix for PR34170 / TCWG1137 (cannot select truncate in ARMv7
backend)
* investigate failure to build clang in shared lib mode with gcc
Hi.
gdb doesn't run due to there is no libpython2.7.so on the system.
$ ./gdb/gdb --version
./gdb/gdb: error while loading shared libraries: libpython2.7.so: cannot open shared object file: No such file or directory
There is only static python library available. Is there a way to build gdb with static python library?
Regards,
Martins
== Progress ==
* GCC
- FDPIC
- reworking/cleaning binutils patches
* GCC upstream validation:
* Infrastructure:
- TCWG-1335: updated builder dockerfiles with postfix config. ABE
patch under review to send test results. Sent a patch for
contrib/test_summary script.
- Enabling use of Linaro binary release on old distro: unsuccessful
experiment with LD_PRELOAD so far.
* misc (conf-calls, meetings, emails, ....)
== Next ==
* GCC/FDPIC
* GCC upstream validation
* Off on Friday afternoon.
# Progress #
* Fix non-gdbserver issue and GDB buildbot issue.
Intel people committed a patch breaks every non-x86 gdbserver. Test
with GDBserver is slowed down from 20~40 minutes to 6~12 hours.
The fix is pushed in,
requested upstream GDB buildbot maintainer to get rid of pending
builds until the fix.
# Plan #
* Review Alan H.'s patches.
--
Yao Qi
== This Week ==
* Coremark regression (TCWG-1234) (6/10)
- Working on defining a cost model for hoisting.
* Public Holiday (2/10)
* Misc (2/10)
- Meetings
- Slides
== Next Week ==
- Continue ongoing tasks.
Note: working for Linaro every other week
* start looking at fix for PR34170 / TCWG1137 (cannot select truncate in
ARMv7 backend):
+ inline asm with >=64bit floating-point output is not handled
+ wrote a tentative patch which crashes later in the code, need to
investigate
* Start slides for technical talk in TCWG room @ Linaro connect:
+ bswap done, started to refamiliarize myself with store merging pass and
its latest improvement
* Merge the two patches for TCWG-1308 (missing pseudo expansion + crash in
instruction selection of vector load/store with register writeback)
=== Plan for next Linaro week (week 10) ===
* finish fix for PR34170 / TCWG1137 (cannot select truncate in ARMv7
backend)
* finish slides for bswap/store merging passes presentation in hacker room
at Connect HK2018
* Off on Monday [1/5]
# Progress #
* GDB is confused by the line table generated by GCC with -gcolumn-info
PR 22531. [2/5]
Preparatory patches v2 are posted.
* Merge my patches on removing MAX_REGISTER_SIZE. Done. [2/5]
# Plan #
* PR 22531,
* Upstream patches review.
--
Yao Qi
== Progress ==
* GCC
- FDPIC
- reworking/cleaning binutils patches
* GCC upstream validation:
- no regression to report this week :-)
* Infrastructure:
- tcwg-buildapp + lava now triggered daily, to check lava/lab reliability.
- updated builder dockerfiles with postfix config. Patch under review
- some progress on enabling use of Linaro binary release on old
distro. My proposal was rejected, but the discussion moved forward.
- fixed toolchain build not to ship 'runtest' anymore, and moved
gdbserver from bin/ to sysroot dir
* misc (conf-calls, meetings, emails, ....)
== Next ==
* GCC/FDPIC
* GCC upstream validation
# Progress #
* GDB is confused by the line table generated by GCC with -gcolumn-info
PR 22531. [2/5]
Tested one patch again, committed. Keep going on the rest
of them.
* Fix one GDB issue with OpenOCD, which is a long standing issue. [2/5]
Commit patch to both GDB master and 8.1 branch. Done.
* Misc, patches review, meeting. [1/5]
# Plan #
* One day off on Monday,
* PR 22531,
* Resume my pending patches on removing MAX_REGISTER_SIZE.
--
Yao Qi
== Progress ==
* GCC
- FDPIC
- rebased GCC and GDB patches on top of recent master branches.
- adjusted some of the GDB (gdbserver) patches to cope with gcc-8
complaints.
- adjusted CI testsuite to cope with gcc-8
* GCC upstream validation:
- no regression to report this week :-)
- still checking go/libgo random results on some tests
* Infrastructure:
- improved tcwg-buildapp (Using Lava, thanks to Remi). Now retries
lava job several times if needed.
- managed to configure postfix to send emails from our build
containers (thanks Ben). Once this is properly configured/deployed,
we'll finally be able to send GCC validation results to the
appropriate list
- resurrected my old work to force use of the old memcpy version
such that our binary toolchains work on older distros (such as
RHEL6...)
* misc (conf-calls, meetings, emails, ....)
== Next ==
* GCC/FDPIC
* GCC upstream validation
== This Week ==
* Code hoisting (TCWG-1234) (6/10)
- Working on approach to add basic block info to ANTIC sets
* GCC bugs (3/10)
- Extend sincos to handle sin 2x (PR83661): Patch completed.
* Misc (1/10)
- Meetings
# Progress #
* GDB is confused by the line table generated by GCC with -gcolumn-info
PR 22531. [2/5]
Override operator new/delete, patch is OK'ed but Tom still believes
classes must be is_trivially_destructible.
* Resume my pending patches on removing MAX_REGISTER_SIZE.
[2/5]
Patches v2 are updated and posted.
* Fix one GDB issue with OpenOCD, which is a long standing issue. [1/5]
Patch is tested, but not committed yet.
# Plan #
* PR 22531,
* Resume my pending patches on removing MAX_REGISTER_SIZE.
* More patches review,
--
Yao Qi
== Progress ==
* GCC
- FDPIC
- updated binutils ref results in CI. There are a couple of new
failures to investigate
- started GCC upgrade: rebased the FDPIC GCC pile of patches on top of
trunk.
- debugging ICE while building libgcc
* GCC upstream validation:
- helped reproduce a bugzilla on armeb
- reported random go/libgo test failures. Intel confirmed they also see
similar random results.
* Infrastructure:
- improved tcwg-buildapp script/job to actually boot arm/arm64 boards
after building a kernel with a given toolchain. (Using Lava, thanks to Remi)
* misc (conf-calls, meetings, emails, ....)
== Next ==
* GCC/FDPIC
* GCC upstream validation
== Progress ==
o LLVM
* "unpredictable" handling:
- Bugzilla 33011: Fix committed
- Working on unpredictable cases when using PC as operand.
* Buildbots failures:
- Analyzed regressions, due to D42574
- Tested and reviewed proposed tix
* 6.0.0 release test failure:
- Investigate Bug 35996 (asan_rt_conflict_test segfaults)
- Issue due to hardcoded filename;s lenght is too short
- Validating a fix
* Got commit after approval access granted
o Misc
* Various meetings and discussions.
# Progress #
* gfortran 7.2 vs 8.0 debug information difference. [2/5]
Open GCC bug to get more attention, PR debug/84131. It is a GCC 8
regression. Jakub fixed it two hours after I opened the bug. Now,
there is no gdb.fortran test fails with truk gcc.
* GDB is confused by the line table generated by GCC with -gcolumn-info
PR 22531. [2/5]
Patches are done, to be posted for review. Investigate how to
override new/delete operator in C++.
* Resume my pending patches on removing MAX_REGISTER_SIZE.
[1/5]
Update patch series v2 per reviewers' comments.
# Plan #
* GDB 8.1 is released! Bump up GDB version in Linaro toolchain.
* PR 22531,
* Resume my pending patches on removing MAX_REGISTER_SIZE.
--
Yao Qi
== This Week ==
* GCC bugs (5/10)
a) Extend malloc_candidate_p to handle multiple phi's (TCWG-1331):
Fixed testsuite regressions
b) Extend sincos to handle sin 2x (PR83661): Started working on patch.
* TCWG-1234 (2/10)
- A one liner patch that pessimizes hoisting by requiring an
expression to be in AVAIL blocks of all immediate successors works for
improving the regression.
- Working to make the patch more general to avoid pessimizing hoisting.
* Public holiday (2/10)
* Misc (1/10)
- Meetings
== Progress ==
o Linaro GCC/Validation
* 2018.01 snapshots deployed
* 2018.02 release candidates will be done when CVE mitigation will
be contributed upstream.
o LLVM
* "unpredictable" handling (Bugzilla 33011, ...): on-going
* Investigated OOM issue further... without much success.
* Python scripts reviews
o Misc
* Various meetings and discussions.
* Preparing Connect presentations
Note: working for Linaro every other week
== Progress ==
* PR35157 / TCWG-1308 (crash in ARM backend for VST1d64TPseudoWB_fixed
instruction):
+ after 2 attempts got now a clean patch with no testsuite regression
+ need to add testcase and it will be good to go upstream
* Track down why xdg-open launches libreoffice for .dot files and opened
Launchpad LP#1744953.
* Misc meetings
== Plan ==
* submit fix for PR35157 (crash in ARM backend for VST1d64TPseudoWB_fixed
instruction)
* fix for PR34170 / TCWG1137 (cannot select truncate in ARMv7 backend)
* start preparing slide for bswap/store merging passes presentation in
hacker room at Connect HK2018
# Progress #
* GDB is confused by the line table generated by GCC with -gcolumn-info
PR 22531. [2/5]
My preparatory patches are reviewed, mostly on C++, get encouraged to
use more fancy C++ features.
* gfortran 7.2 vs 8.0 debug information difference. [2/5]
Many gdb.fortran test fails with gfortran 8 but gfotran 7.2 is OK. I
'git bisect' gcc and find the commit causing the debug info change,
it is like a bug to me, but my compiler/fortran knowledge is too few
to claim it is a 7.2 -> 8.0 regression.
Posted my analysis to gcc@ and fortran@ mail list.
* TCWG-1040, SVE patches review. [1/5]
Review Alan's patches.
# Plan #
* PR 22531, upstream preparatory patches,
* Write patch series v2 for TCWG-1292.
--
Yao Qi
== Progress ==
* GCC
- FDPIC
- debugging CI loop
* GCC upstream validation:
- reported a few regressions
- contributed to jenkins jobs
* Infrastructure:
- looking at how to use lava to boot boards in gcc validation (with Remi)
* misc (conf-calls, meetings, emails, ....)
== Next ==
* GCC/FDPIC
* GCC upstream validation
Hi,
given the following code:
-- isystem_test.cpp -------------
#include < isystem_test.h>
bool dummy_function( void )
{
return false;
}
-----------------------------------------
-- isystem_test.h ------------------
template <class _CS_cT>
class allocator
{
};
-----------------------------------------
and g++ version: arm-eabi-g++.exe (Linaro GCC 7.2-2017.11)
1. compiling with "arm-eabi-g++ -I . -g -c isystem_test.cpp"
--> OK
2. compiling with " arm-eabi-g++ -isystem . -g -c isystem_test.cpp "
--> output error:
In file included from isystem_test.cpp:3:0:
./isystem_test.h:3:1: error: template with C linkage
template <class _CS_cT>
^~~~~~~~
It seams that the option -isystem changes the include of isystems_test.h into a C include, i.e. the header content seems to be handled as C-Code
Same error behavior with arm-eabi Linaro GCC 6.4-2017.11, Linaro GCC 6.3-2017.05
-----------------
Testing the same with the mingw msys g++ compiler outputs no error:
g++.exe (Rev2, Built by MSYS2 project) 7.2.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
---------------
Also no errors for:
arm-linux-gnueabihf-g++.exe (Linaro GCC 6.3-2017.05)
---------------
Is there a special behavior for arm-eabi g++ compiler?
Best regards
Martin Kaul
The Linaro Toolchain Working Group (TCWG) is pleased to announce the 2018.01
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-2018.01/
Interesting changes in this GCC source package snapshot include:
* Updates to GCC 7.2+svn256695
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-2018.01/
Interesting changes in this GCC source package snapshot include:
* Updates to GCC 6.4+svn256699
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.
