Hi,
I am using the following linaro toolchain and need to create a license
manifest in terms what are the packages are there, what license they use.
https://releases.linaro.org/components/toolchain/binaries/
5.2-2015.11-2/aarch64-linux-gnu/
I don't see any such manifest in the release archive nor in the toolchain
archive. If such manifest is available then would you please point me to it.
--
*Ronak A Desai*
1 day off (Friday)
== Progress ==
* GCC
- FDPIC
- debugging crash during program startup (self-relocation), and
linker assert when using -static
* GCC upstream validation:
- reported a couple of regressions, tested a couple of patches for upstream
- incremental improvements for more robustness, and easier
configuration of validations
* Infrastructure:
* misc (conf-calls, meetings, emails, ....)
== Next ==
Holidays until Jan 2nd, 2018
Merry Christmas and happy new year!
# 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.
