All,
During Connect the suggestion was made that each working group should have
its own IRC Channel for discussions and topics relating to the group in
particular (as opposed to #linaro which is 'generic' Linaro conversations).
Therefore I have just set up #linaro-tcwg on Freenode for the Toolchain
Working Group.
This channel is public and open to anyone who wants to talk with the TCWG
group about anything toolchain related.
Thanks,
Matt
--
Matthew Gretton-Dann
Toolchain Working Group, Linaro
I spoke with Ramana about these at HKG18, and I'm finally getting back to
these. I have routines for
-rw-rw-r--. 1 rth rth 2538 May 30 19:12 memchr.S
-rw-rw-r--. 1 rth rth 2405 May 30 20:49 memcmp.S
-rw-rw-r--. 1 rth rth 2385 May 30 19:12 rawmemchr.S
-rw-rw-r--. 1 rth rth 2470 May 30 19:12 strchrnul.S
-rw-rw-r--. 1 rth rth 2588 May 30 19:12 strchr.S
-rw-rw-r--. 1 rth rth 2370 May 30 19:12 strcmp.S
-rw-rw-r--. 1 rth rth 2403 May 30 19:12 strcpy.S
-rw-rw-r--. 1 rth rth 2263 May 30 19:12 strlen.S
-rw-rw-r--. 1 rth rth 2595 May 30 19:12 strncmp.S
-rw-rw-r--. 1 rth rth 2344 May 30 19:12 strnlen.S
-rw-rw-r--. 1 rth rth 3105 May 30 19:12 strrchr.S
The tests pass when run under Foundation Platform 11.3. What is the best way
to submit these for review and upstreaming? There's nothing in the git README
about an upstream mailing list...
FWIW, my code is at
https://github.com/rth7680/cortex-strings/tree/rth/sve
r~
== Progress ==
o GNU release transition
* 6.4 and 7.3 2018.05 RC1 deployed
o LLVM
* Thumbv8 bot failures [TCWG-1400]:
- Testing fix on arm, armhf, armv7 and armv8.
o Misc
* Various meetings and discussions.
== This Week ==
* TCWG-1234: Code hoisting and register pressure (8/10)
- Created patches for restricting hoisting out of blocks on loop exit
but that was false alarm.
- Investigating interaction of forwprop, code hoisting and register pressure.
- Started upstream discussion.
* GCC bugs (1/10)
- TCWG-125: static_cast not working on ARM hardfp: Asked upstream on
libvolk list for help to reproduce.
- PR85787: Created patch, investigating regressions caused due to it.
* Misc (1/10)
- Meetings
== Next Week ==
- TCWG-1234
- GCC bugs
Progress:
* VIRT-65 [QEMU upstream maintainership]
+ sent patch for minor bug where FRECPX was not honouring FPCR.FZ
+ looking at migration failure for TCG VMs using Secure mode. I know
what the bug is, but need to figure out how to fix it without breaking
migration compatibility for TCG VMs which don't use Secure mode...
+ various miscellaneous minor bug fixing and code review
* VIRT-164 [improve Cortex-M emulation]
+ MPC emulation:
- sent out first version of patchset that implements the required
IOMMU core code features and the MPC device that uses them; fielded
various code review discussions on it
thanks
-- PMM
Half of the week spent investigating identical code folding -icf=safe.
Turns out that upstream have a proposal that is much further along so
shifted focus on to doing as much as I can to help it along.
Found out that for some use cases of AArch64 PIC the small code model
is inappropriate as the code segments may not be 4k aligned. Started
looking into what it would take to implement the tiny code model in
LLVM (supports only small and large at the moment). Built a small
prototype to handle the easiest absolute addressing case, much more
work needed to handle PIC and TLS.
Not a lot of tangible progress, but I think I have learned a bit more
about LLVM.
Planned Absences
- Friday 25th May (holiday).
- Monday 28th May (UK public holiday)
Hello,
I just noticed that the manifest file of the Linaro gcc-5.5-2017.10 release under http://releases.linaro.org/components/toolchain/gcc-linaro/5.5-2017.10/x86_… from January, 13th 2018 differs from the original version from October 2017: the binutils, gdb and abe versions are different.
Could you please tell me the reason for the changes?
Thank you very much!
Andrej Gantvorg