[ACTIVITY] 7-11 November 2016

2016-11-14 Thread Christophe Lyon
* 1 day off

== Progress ==
* Validation
  - patches & reviews (jenkins jobs, abe)
  - improving abe validation
  - abe cleanup

* GCC
  - bug #2562 (PR78253). GCC behaviour wrt weak handling changed on arm/aarch64
   between 4.9 and 5. Proposed a patch upstream but it needs more
  work/justification.

* misc (conf-calls, meetings, emails, )

== Next ==
* (try to) handle backlog of GCC trunk regressions
* ABE & Jenkins jobs patches reviews and bug fixes
* backports/reviews
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain


[ACTIVITY] 7-11 November 2016

2016-11-11 Thread Peter Smith
TCWG-901 Investigate lld as a system linker
- Installed lld as the system linker on my Chromebook and attempted to
build and run things to see what breaks
- Only one unknown concrete problem found so far, thunks to undefined
symbols with PLT entries don't work. This seems to be common in python
C extensions that are dlopened from python, and call back to the
interpreter.
-- I have a downstream fix (TCWG-919), with this fixed the test-suite
can run with lld as the linker through the pip install (SQLAlchemy has
C extensions).
- As thought previously, clang is too big to link without thunks.
- Attempted to make a simple add thunks to all branches to see if I
could get clang to link. Sadly this won't work as lld only permits one
thunk per symbol and this might be out of range of the caller as well.
- Some thoughts and experiments on how much of llvm, compiler-rt,
clang and libc++ can be linked with lld. I'm currently thinking of
altering my lld driver to automatically switch to ld.bfd after a
relocation out of range link error. I want to try and get a lld linked
clang + compiler-rt +libc++ system running.

TCWG-683 lld support for branches to unresolved weak references
- Now upstream

Also:
- A lot of rebasing of downstream patches as some refactoring is going
on to make lld more flexible.
- Some inconclusive investigation into weak reference behaviour in GNU
ld. The ARM and AArch64 ld.bfd linkers will put a dynamic relocation
on a got slot generated by for an unresolved weak reference. The x86
linkers do not, they statically resolve the got slot to 0.
- Some inconclusive investigations into trying to work out what
packages to build to test lld. With the exception of very large
programs ld seems to successfully complete the link for all programs.
Whether it has done so correctly or not is another matter.
-- Currently thinking about whether I can build a BSD make world on a
raspberry pi.

Plans for next week:
- Bring TCWG-901 to a close and work out what to work on next.
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain


[ACTIVITY] 7-11 November 2016

2016-11-11 Thread Diana Picus
== Progress ==

* Rewrite llvm-projs in Python [TCWG-833] [2/10]
  - Investigated clitest for testing the scripts
  - It seems to be a bit unwieldy for our purposes, so in the end it's
probably a better idea to abuse Python's unittest module even for higher
level tests (they'll be in a different directory though)

* [ARM GlobalISel] Select add instructions [TCWG-925] [6/10]
  - Committed a patch upstream with all the plumbing necessary for enabling
GlobalISel for ARM
  - Working towards selecting an add instruction on i32 types - currently
have some naive support for lowering arguments and selecting return and
copy instructions

* Misc [2/10]
  - Meetings, mailing lists, buildbot monitoring
  - Python trainings

== Plan ==

* [ARM GlobalISel] Select add instructions [TCWG-925]
  - Brush it up and send it upstream

* Rewrite llvm-projs in Python [TCWG-833]
  - Start a discussion on the interface / repo layout etc
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain