== Progress ==
* SD card purchased dumped ubuntu for chromebook on sd card and configured
chromebook for development.
* Created newly released GDB 7.6 test suite results by running on
chromebook and x86 machine in native-none,native-gdbserver and
remote-gdbserver configurations
* Created GDB 7.5.1 test suite results by running on chromebook and x86
machine in native-none,native-gdbserver and remote-gdbserver configurations
* Created comparisons of gdb 7.6 test suite results in different
configuration.
* Public Holiday on 1st of May
== Plan ==
* Fill up the googledoc comparison sheets of gdb 7.6 test suite run in
different configuration on chromebook and x86.
* Fill up the googledoc comparison sheets of gdb 7.5.1 test suite run in
different configuration on chromebook and x86.
* Analyse difference between test suite results between gdb 7.5.1 and gdb
7.6.
* Pakistan General Elections 2013 might have to take a day off.
== Progress ==
* AARCH64 - gprof support.
Make GCC generate profile information (Completed).
Defined macros in GCC to enable frame return address and insert profile call.
Changed glibc to use generic gprof calls. Now gmon.out is generated
when run in openembedded on V8 model.
Used PROFILE_HOOK and generated mcount call using emit_library_call.
Misc
-------
1 May was a holiday.
== Plan ==
* Continue AARCH64 gprof support
* Post patches in GCC for profile and RETURN_ADDR_RTX
* Look at gprof "-c" option support in binutils
* Run gcc testsuite with changes on openembeded/V8 model.
Hi,
I tried compiling a hello-world program for cortex -a53/57 but, gcc does not recognize the mcpu option.
Here is my command ...
aarch64-linux-gnu-gcc hello_world.c -mcpu=cortex-a53 -o hello_world
Does the compiler support these options? I see that lib/gcc/aarch64-linux-gnu/4.8.1/plugin/include/config/aarch64/aarch64-cores.def do have the entries for cortex a53 & a57.
Thanks,
Kalai
== Progress ==
* Committed binutils testsuite fix for precise, should be green in cbuild now.
* Comitted binutils fix for ARM IFUNC issue.
* Various small binutils fixes for AArch64.
* Lots of rework of glibc memcpy patch, now up to v6.
* Integrated latest bionic string functions into cortex-strings.
* AArch64 IFUNC code and tests beginning to take shape.
== Issues ==
* None.
== Plan ==
* Another respin of glibc memcpy patch (last one?).
* More work on AArch64 IFUNC.
* May get time to look into gdb bug Peter found.
* 4 day week due to bank holiday.
--
Will Newton
Toolchain Working Group, Linaro
Progress:
* office move
* checking up on status of licensing issues with QEMU's softfloat
* cleaned up obsolete qemu blueprints in launchpad [Matt G-D is
going to finish the last bits of transferring the backlog to
JIRA where appropriate]
* booked travel/hotel for Connect Dublin
* reviewed John Rigby's mach-virt and aarch64 patches
* VIRT-49
** can run KVM with this code now, need to test migration proper
(requires kernel to support arch timer state save/load),
and clean up some TODOs and other cruft
** GDB is behaving oddly connected to QEMU's stub, which I think is
a GDB bug (LP:1175525) but may also be a QEMU side issue
Plans:
* VIRT-49 debug & patch cleanup
* NB: UK bank holiday next week, will be 3 day week for me
-- PMM
== Issues ==
* None
== Progress ==
* Short week (only 2 days)
* Libunwind AArch64 support:
- Did some fixes and cleanups after review.
- re-submitted upstream
* LRA on ARM and AArch64:
- Enabled LRA on trunk for ARM target
- build doesn't complete, investigation ongoing
* Internal meetings
== Plan ==
* Short week too
* Continue on LRA
== Progress ==
* EuroLLVM 2013
- Conference Mon~Tue
- Analysing questionnaire's response
- Writing a blog entry, reports
* Shorter week, low progress
== Plan ==
* Release
- Start testing version 3.2
- Check-out frozen 3.3 and run the same tests
- Make sure calxeda node is up to the task
- Buy a Chromebook for further testing (?)
I'll probably spend all my time worrying about the release, one way or
another...
Hi,
I'm trying to build the aarch64 tool chain from source on a Redhat machine. I see that build.mk in the crosstool package requires a few .deb packages. If I want to build this on a Redhat machine, what are the changes I have to do?
Thanks,
Kalai
