- linaro-toolchain - lists.linaro.org

by Zhenqiang Chen

Summary: * Linaro binary toolchain 2012.04 release. * Code size benchmark analysis. Details: 1. Validate and bug fix for linaro binary toolchain 2012.04 release. 2. Investigate code size regressions in 4.7 Find more regression cases due to loop invariant hoisting, and tests should we can reduce some codesize with option -fno-move-loop-invariants. Some regressions are due to pass_reorder_blocks, which is disabled for -Os in 4.7. For some cases, ivopt will introduce to more codes and function inline might lead to more spilling. We also try linaro 2012.04 baremetal build. But there is a few bytes regression compared with 4.7 trunk. 3. Setup the qemu env following Michael’s instructions (https://wiki.linaro.org/MichaelHope/Sandbox/QEMUCrossTest) and tests show it work. 4. Try to build gcc-linaro-2012.04 configured with "--with-fpu=neon --with-float=hard" based on a precise sysroot (precise-sysroot-armhf-r0.tar.bz2) from http://people.linaro.org/~michaelh/incoming * Linux build is OK without any change. * Mingw32 build reports error. After removing the code, the build PASS. [ERROR] .../libc/usr/include/arm-linux-gnueabihf/sys/types.h:117:19: error: two or more data types in declaration specifiers Plans: * Investigate other code size regressions in 4.7. Planed leaves: * Labor Day holiday: April 30 and May 1. Best regards! -Zhenqiang

13 years, 4 months

2
1
0 0

[ACTIVITY] weekly status

by Ken Werner

Hi, OpenEmbedded-Core/meta-linaro: * pushed support for Linaro GCC 4.6.4 2012.04 and for the 2012.03-20120326 binary toolchain * updated the wiki * created a branch to support GCC 4.7 * built several images using several GCC 4.7 based toolchains (OE, linaro 4.7.1, binary toolchain 2012-04) * minimal images are working * sato image shows splash screen forever (won't bring up the matchbox window manager) * only when using the binary toolchain 2012-04 ? -> needs to be analyzed * Qt 4.8 requires small patches (posted and merged into oe-core/master-next) Libunwind: * User reports issues when backtracing through signal frame * reason: the lib falls back on APCS frame parsing which usually segfaults on EABI systems * provided debugging hints and insights on how libunwind handles signal frames * posted a reduced testcase Regards, Ken

13 years, 4 months

1
0
0 0

[ACTIVITY] Apr 23 - Apr 27

by Ulrich Weigand

== GCC == * Fixed regression (ICE when building EEMBC) with patch to use vld1/vstd1 instead of vldm/vstdm for vector moves. Updated merge request and restarted testing. * Implemented patch to fix LP #959242; backported to Linaro GCC 4.7 and created merge request for regression testing and benchmarking. * Ongoing discussions on -fsched-pressure; worked on patch to enable it by default on s390. * Ongoing work on improving end-of-loop value computation. Mit freundlichen Gruessen / Best Regards Ulrich Weigand -- Dr. Ulrich Weigand | Phone: +49-7031/16-3727 STSM, GNU compiler and toolchain for Linux on System z and Cell/B.E. IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter | Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen | Registergericht: Amtsgericht Stuttgart, HRB 243294

13 years, 4 months

1
0
0 0

[ACTIVITY] report week 17

by Peter Maydell

Current Milestones: || || Planned || Estimate || Actual || ||cp15-rework || 2012-01-06 || 2012-06-23 || || Historical Milestones: ||initial-a15-system-model || 2012-01-27 || 2012-01-27 || 2012-01-17 || ||qemu-kvm-getting-started || 2012-03-04?|| 2012-03-04 || 2012-02-01 || == cp15-rework == * have had no review feedback on this patchset yet, and we're now into QEMU 1.1 hardfreeze. I'm hoping to get review during the month we're in freeze and then commit early June when 1.2 opens. However since that coincides with me being on holiday I've set the Estimate date to allow for that plus a week or so of buffer. Actual further work required is probably 1 week max, most of this is waiting-for-other-people or being-away. == kvm-boot-wrapper == * pushed dtb support changes to git repo == other == * basic QEMU side support for the VGIC kernel implementation Marc Z has been working on. I have something that seems to work but it's still a bit prototype and missing features. * investigated why my guest kernel was causing kvm to exit: turns out that we haven't implemented the kernel support for gracefully not using KVM if not booted in hyp mode, so trying to boot a KVM-aware kernel as a KVM guest doesn't work yet. * sent off the final few patches which I want in QEMU 1.1 before hardfreeze at the start of next week * tested a beagle board linaro snapshot image (it panics on bootup, LP:989737) * trying to clarify the KVM todo list... -- PMM

13 years, 4 months

1
0
0 0

Board boots Linux built with 4.5.3 TC but not 4.6.3

by Dan Donahue

Greetings, I successfully built and booted Linux 3.1 for the beaglebone (TI am335x) using the 4.5.2 toolchain. I rebuild the same kernel using the same config with the 4.6.3 toolchain, but the board hangs at "Uncompressing Linux... done, booting the kernel." I halt the beaglebone at the U-Boot prompt and have it download and run uImage from an NFS mounted RFS. The Linaro 4.5.2 toolchain was installed in my Ubuntu 11.04 distro using aptitude. The Linaro 4.6.3 toolchain binaries, downloaded via Launchpad, were installed into my own tools directory. 4.5.2 INFO: ./gcc-linaro-arm-linux-gnueabi-2012.01-20120125_linux/bin/arm-linux-gnueabi-gcc --version arm-linux-gnueabi-gcc (crosstool-NG linaro-1.13.1-2012.01-20120125 - Linaro GCC 2012.01) 4.6.3 20120105 (prerelease) Copyright (C) 2011 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. Built with: $ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage 4.6.3 INFO: ./bin/arm-linux-gnueabi-gcc --version arm-linux-gnueabi-gcc (crosstool-NG linaro-1.13.1-2012.01-20120125 - Linaro GCC 2012.01) 4.6.3 20120105 (prerelease) Copyright (C) 2011 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. Built with: $ make ARCH=arm CROSS_COMPILE=<mytoolsdir>/gcc-linaro-arm-linux-gnueabi-2012.01-20120125_linux/bin/arm-linux-gnueabi- uImage Could it have anything to do with my binutils and/or U-Boot version? Any debugging tips? U-Boot INFO: U-Boot# version U-Boot 2011.09-00010-g81c8c79 (Feb 13 2012 - 14:48:03) arm-angstrom-linux-gnueabi-gcc (GCC) 4.5.4 20111126 (prerelease) GNU ld (GNU Binutils) 2.20.1.20100303 Thanks for reading this far.

13 years, 4 months

2
1
0 0

Cross testing applications under QEMU

by Michael Hope

We use QEMU to test programs built by the toolchain binary release for correctness. I've written up the instructions for spinning up your own at: https://wiki.linaro.org/MichaelHope/Sandbox/QEMUCrossTest It's focused on simplicity - getting a running, SSH only Cortex-A9 up and going as soon as possible. It's not the latest, not graphical, and doesn't replace the deeper documentation at: https://wiki.linaro.org/Resources/HowTo/Qemu -- Michael

13 years, 4 months

2
2
0 0

[ANNOUNCE] Linaro Toolchain Binaries 2012.04 released

by Michael Hope

The Linaro Toolchain Working Group is pleased to announce the 2012.04 release of the Linaro Toolchain Binaries, a pre-built version of Linaro GCC and Linaro GDB that runs on generic Linux or Windows and targets the glibc Linaro Evaluation Build. Uses include: * Cross compiling ARM applications from your laptop * Remote debugging * Build the Linux kernel for your board What's included: * Linaro GCC 4.7 2012.04 * Linaro GDB 7.4 2012.04 * A statically linked gdbserver * A system root * Manuals under share/doc/ The system root contains the basic header files and libraries to link your programs against. Interesting changes include: * Switches to the new GCC 4.7 based Linaro GCC * Adds native language support to most of the programs * Adds the mudflap, ssp, and gomp runtime libraries * Enables gnu_unique_object support in GCC Please see the README about running 4.7 based programs on a system with 4.6 based runtime libraries. The Linux version is supported on Ubuntu 10.04.3 and 11.10, Debian 6.0.2, Fedora 16, openSUSE 12.1, Red Hat Enterprise Linux Workstation 5.7 and later, and should run on any Linux Standard Base 3.0 compatible distribution. Please see the README about running on x86_64 hosts. The Windows version is supported on Windows XP Pro SP3, Windows Vista Business SP2, and Windows 7 Pro SP1. The binaries and build scripts are available from: https://launchpad.net/linaro-toolchain-binaries/trunk/20yy.mm Need help? Ask a question on https://ask.linaro.org/ Already on Launchpad? Submit a bug at https://bugs.launchpad.net/linaro-toolchain-binaries On IRC? See us on #linaro on Freenode. Other ways that you can contact us or get involved are listed at https://wiki.linaro.org/GettingInvolved. -- Michael

13 years, 4 months

1
0
0 0

[ACTIVITY] April 16 - April 20

by Thiago Jung Bauermann

Hi, GDB for Android: * Wrote patch for bionic adding .note.ABI-tag to the crtbegin object files. Sent to Google engineers, They think it's going in the right direction and I will submit via gerrit. * Isolated Android-related changes in diff between AOSP's GDB 7.3.x and FSF GDB 7.3. There are a lot of unrelated changes there. * Sent e-mail asking for comments about the Android extension to .note.ABI-tag to the LSB and binutils mailing lists. Got only one e-mail of feedback. -- []'s Thiago Jung Bauermann Linaro Toolchain Working Group

13 years, 4 months

1
0
0 0

[ACTIVITY] weekly status

by Ken Werner

Hi, * catching up with emails * rebased against current OE-core * OE is planning a release in april (following the yocto schedule) * noticed the libc of our binary toolchain is lacking i18n * caused a packaging issue for meta-linaro but easy to workaround * contents of the i18n folder are only used at runtime (not relevant for compiliation time) * updates in order to support for the 2012.03-20120326 binary toolchain * locations of sibgcc_s.so and libstdc++.so are different * added support for linaro gcc 2012.04 * looked at the meta-linaro patches made by Khem Regards, Ken

13 years, 4 months

2
2
0 0

Fix for EEMBC build problems

by Michael Hope

The EEMBC supplied build system has a couple of bugs with library order (putting -lrt at the start of the command line instead of the end) and the harness library (depending on THOBJS but linking against THLIB). I've fixed these and pushed to our private branch. Ulrich, I've spawned builds of your vld1.64 branch and its ancestor. Once those are done I'll spawn a benchmark run against them. -- Michael

13 years, 4 months

1
0
0 0

[Activity] Week 16

by Zhenqiang Chen

Summary: * Code size benchmark analysis. * Linaro binary toolchain 2012.04 release. Details: 1. Tuning the heuristic to assign register for copies. * Take the CONFLICT_HARD_REGS and HARD_REG_COSTS of copies into account when conflict_costs is NULL in update_conflict_hard_regno_costs, which handles the following case: a = ... ... b = a // a can be assigned with r3 or r5 which have the same min_cost. ... // b is conflicted with r3 or the cost of r3 is very high = b In this case, if a is assigned with r3, b can not be assigned with r3, so the copy "b = a" can not be optimized. When taking the CONFLICT_HARD_REGS or HARD_REG_COSTS of b into account, we can assign a with r5. 2. Linaro binary toolchain 2012.04 release. * Update gdb/TOOLCHAIN_PKGVERSION/README to 2012.04. * Test workaround localization patch to fix lp:918926. * Local build and tests show the toolchain can find the corresponding .mo file. * But if the host system does not have the corresponding font packages, it will show some mess characters. * gdb does not have gdb.mo. 3. Investigate code size regressions in 4.7. * Loop invariant hoisting might increase register pressure, which leads to much more spilling. Plans: * Finalize Linaro binary toolchain 2012.04 release * Investigate other code size regressions in 4.7. Planed leaves: * Labor Day’s holiday: April 30 and May 1. Best regards! -Zhenqiang

13 years, 4 months

1
0
0 0

Issue with libgcc_s.so.1 location

by Felipe Contreras

Hi, I have been using CodeSourcery tool-chains since forever, and I decided to try Linaro's tool-chain. So far I haven't had any issues, except one: libgcc_s.so.1 is located in arm-linux-gnueabi/lib, which is not available from arm-linux-gnueabi/libc. The CodeSourcer tool-chain has all those files inside the 'libc' directory, which is useful for Scratchbox2, because you need to specify a "target root" which is basically the libc directory which acts in a similar fashion to /. I've managed to create a rule to workaround this issue, but I wonder why are those files in that location, why not in 'libc/lib'? Cheers. -- Felipe Contreras

13 years, 4 months

2
1
0 0

[Activity] Week 15 / 16

by Ramana Radhakrishnan

=== Progress === * Worked on the VFP addressing modes patch upstream. Handled most comments. Final version has finished testing and looks almost ready to commit. * Investigated an issue with min type transformations for loop terminating conditions. Wrote up a small patch which appears to do the right thing - passed a bootstrap on x86 but that probably means it never got triggered :( . The particular case of interest was not vectorizing : #define min(x,y) ((x) <= (y) ? (x) : (y)) int a[256] __attribute__((aligned (16))); int b[256] __attribute__((aligned (16))); int c[256] __attribute__((aligned (16))); void foo (int x, int y) { int i; for (i = 0; i < x && i < y; // i < min (x, y); i++) a[i] = b[i] * c[i]; } but vectorizing the commented region. I've tentatively worked out a fix in tree-loop-im.c which looks like a bit of a grotesque hack .... * Attended LLVM devcon in Week 15. Useful and interesting and conference. == Plans == * Pursue backporting gnu_unique_object upstream. * Look at some of the existing blueprints and start discussions around prioritizing this. * Investigate some of the SEGVs with h-c partitioning. * Finish off the VFP addressing modes patch. Absences. * 03 May 2012 - 08 May 2012. * Linaro Connect Q2.12 - May 28 - June 1 -

13 years, 5 months

1
0
0 0

[ACTIVITY] Apr 16 - Apr 20

by Ulrich Weigand

== GCC == * Checked in backport patch to fix LP #972648 into Linaro GCC 4.6. * Checked in fix for incorrect vld alignment hints to FSF mainline and 4.7 branch. * Investigated options to fix stack re-alignment. * Ongoing investigation of LP #959242: design problem in vectorizer pattern detection logic causes ICE in certain cases where an original sequence is recognized as part of *two* potential patterns simultaneously. * Ongoing work on improving end-of-loop value computation. Mit freundlichen Gruessen / Best Regards Ulrich Weigand -- Dr. Ulrich Weigand | Phone: +49-7031/16-3727 STSM, GNU compiler and toolchain for Linux on System z and Cell/B.E. IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter | Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen | Registergericht: Amtsgericht Stuttgart, HRB 243294

13 years, 5 months

1
0
0 0

[ACTIVITY] report week 16

by Peter Maydell

Current Milestones: || || Planned || Estimate || Actual || ||cp15-rework || 2012-01-06 || 2012-04-10 || || Historical Milestones: ||initial-a15-system-model || 2012-01-27 || 2012-01-27 || 2012-01-17 || ||qemu-kvm-getting-started || 2012-03-04?|| 2012-03-04?|| 2012-02-01 || == cp15-rework == * sent out v1 patchseries for cp15 cleanup to the mailing list, finally * handled review comments on drop-cpu-reset-model-id patchseries == kvm-boot-wrapper == * imported libfdt device tree library and Dave Martin's code from the big.LITTLE boot-wrapper, to add support to the KVM boot wrapper for handling device tree blobs. Patch series sent, will probably commit next week unless there are review issues * that will more or less wrap this blueprint up == other == * usual upstream patch review; QEMU 1.1 soft feature freeze was start of this week, hardfreeze will be beginning of May, people (including me :-)) are trying to squeeze things in under the wire... -- PMM

13 years, 5 months

1
0
0 0

[ACTIVITY] 16th - 19th April

by Andrew Stubbs

* Linaro GCC Investigated the latest test failure for the neon-extend patch. The test for GCC Bugzilla 43137 is failing again. It turns out to be because my switching sign_extend to use a DImode output, rather than two SImode subreg outputs has exposed a bug in the lower-subreg pass. I've spent most of the week trying to figure what can be done about this and discussing the problem with Richard Sandiford upstream. Richard Earnshaw approved my neon-negate patch. That patch depends on the neon-immediates patch which is not approved yet, so I'll have to wait to commit it. Continued looking at NEON-v-core register allocation. Not much progress this week though. * Other Created a patch to make the GCC RTL dumps easier to diff. Posted it upstream and discussed it on the list. Vacation on Friday. * Next week Vacation Monday and Tuesday

13 years, 5 months

1
0
0 0

Update on stack (re-)alignment issues

by Ulrich Weigand

Hello, I've been following up on the discussion we had on Monday regarding stack alignment, and noticed that I had mis-remembered the current state of affairs. Ramana asked me on Tuesday to provide a write-up of the actual status, so here we go ... To summarize the background of the problem: on ARM, the incoming stack pointer is only guaranteed to be aligned to an 8 byte boundary. This means that objects on the stack (local variables, spill slots, temporaries etc.) cannot easily be aligned to more than 8 bytes. This can potentially cause problems in two situations: 1) The object's default alignment (according to its type) is larger than 8 bytes 2) The object has a forced non-default alignment that is larger than 8 bytes The first situation should in theory never appear, since according to the ARM ABI all types have a default alignment of at most 8 bytes. However, due to the current mix-up in GCC, vector types actually are considered to have a 16-byte alignment requirement in GCC. The second situation can only appear with local variables that are declared using attribute ((aligned)). We had discussed on Monday that we need to fix the second situation, since this can always occur and is supported on other platforms. By doing so, we would then automatically fix the first situation as well. However, this reasoning turns out to be incorrect. There are currently in GCC *two* completely separate mechanisms that can be used to align objects on the stack to larger than the ABI guaranteed stack pointer alignment: A) Re-alignment of the full stack frame. This is what is used by the Intel back-end (and only the Intel back-end). At function entry, generated code will align the stack pointer itself to whatever is necessary to fulfil alignment requirements of all objects on the stack. This may necessitate follow-on changes: the frame pointer, if there is one, will likewise need to be aligned at runtime. Also, since incoming stack arguments are now no longer at a fixed offset relative to the stack pointer *or* frame pointer in some cases, we might need an extra register as argument pointer. This method allows extra alignment for *any* object on the stack, but needs significant back-end support in order to be enabled on any non-Intel architecture. B) Dynamic allocation of selected stack variables. This is implemented by common code with no involvement of the back-end. In effect, the code in cfgexpand.c:expand_stack_vars that decides on how to allocate local variables on the stack will remove all variables that require extra alignment and place them into an extra structure. Generated prologue code will then in effect dynamically allocate and align that structure on the stack, and just store a pointer to it as "variable" into the normal stack frame. All other areas of the frame are unaffected. Since this method just simulates code the programmer could have written themselves using alloca, it does not require *any* back-end support and is enabled by default everywhere. However, it only works for regular local variables, and not for any other objects on the stack. Objects on the stack *except* local variables always use default alignment. Since on most platforms, except Intel and *currently* ARM, the ABI stack pointer alignment is sufficient to implement default alignments, method B) as above is able to fulfil all stack alignments. Intel uses method A), so they're also OK. In effect, it's only ARM due to the vector type alignment problem that runs into the situation that neither method works. Under those circumstances, given that: - we want to fix vector type alignment in order to become ABI compliant - once we've fixed this, we're in the same situation as other platforms and method B) already fixes stack alignment problems - implementing method A) is therefore both quite involved *and* actually superfluous I'd now rather recommend that we *don't* try to implement method A) (full stack-frame re-alignment) on ARM. Comments? Mit freundlichen Gruessen / Best Regards Ulrich Weigand -- Dr. Ulrich Weigand | Phone: +49-7031/16-3727 STSM, GNU compiler and toolchain for Linux on System z and Cell/B.E. IBM Deutschland Research & Development GmbH Vorsitzende des Aufsichtsrats: Martina Koederitz | Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen | Registergericht: Amtsgericht Stuttgart, HRB 243294

13 years, 5 months

2
1
0 0

[ACTIVITY] April 9 - April 13

by Thiago Jung Bauermann

Hi, GDB for Android: * Continued conversation about .note.ABI-tag. * Committed upsream the second of three patches for building gdbserver on Android. * Continued working on a crtbrand.c for bionic. 2012.04 release: * Tested the gdb-linaro/7.4 branch on armv5tel, x86 and x86_64, both natively and remotely. Compared results against the 2012.02 release. * Ran the release process, made the release. -- []'s Thiago Jung Bauermann Linaro Toolchain Working Group

13 years, 5 months

1
0
0 0

[ACTIVITY] April 2 - April 6

by Thiago Jung Bauermann

Hi, GDB for Android: * Investigated .note.ABI-tag generation in glibc and FreeBSD. Wrote crtbrand.c for bionic based on FreeBSD's crtbrand.c. Tried to integrate it with bionic's build system. * Contacted Google engineers about adding .note.ABI-tag to Android binaries. 2012.04 release: * Started working on the release. Applied the latest patches from the FSF 7.4 branch to gdb-linaro/7.4 and also my patches to compile gdbserver with the Android toolchain. -- []'s Thiago Jung Bauermann Linaro Toolchain Working Group

13 years, 5 months

1
0
0 0

[ACTIVITY] 9th - 13th April

by Andrew Stubbs

* Linaro GCC Spun release tarballs for Linaro GCC 4.6 and 4.7. Pushed them to Michael's servers and launched the testing. Continued trying to get the 64-bit NEON stuff to work. The negdi2 patch needed some reworking following upstream review, and the extend patch has mysteriously reintroduced a performance regression when the operation is done in core-registers, which needs to be solved, but the other patches seem ok at the moment, although the shift stuff is blocked on benchmarking. I've begun looking at how my changes affect spec2000, and whether the register allocation could be done better. Unfortunately, given that the test systems are currently giving spec results with a low level of consistency (and therefore confidence), this has mostly been by visual inspection, so far. * Other Public Holiday on Monday.

13 years, 5 months

1
0
0 0

getting armv7 linker to emit armv4t thumb interworking

by Allen Martin

I have a cross toolchain I configured with "--with-arch=armv7-a --with-cpu=cortex-a9 --with-tune=cortex-a9" and I want the linker to emit armv4t compatible thumb interworking, but I can't seem to get it to. I noticed that if I create a armv4t toolchain with "--with-arch=armv4t --with-cpu=arm7tdmi --with-tune=arm7tdmi" and then I pass "--use-blx" to the linker it will emit armv7 thumb interworking. There doesn't seem to be any inverse "--no-use-blx" type switch though. Is this a bug/limitation of the linker or am I misunderstanding something? -Allen nvpublic

13 years, 5 months

5
7
0 0

[PATCH] ld: add switch to disable use of BLX instructions

by Allen Martin

Add --no-use-blx switch to force disabling of BLX instructions for thumb interworking. This allows ld to emit code that is armv4t safe even if configured for armv5 or later. --- bfd/bfd-in.h | 4 ++-- bfd/bfd-in2.h | 4 ++-- bfd/elf32-arm.c | 10 +++++++++- ld/emultempl/armelf.em | 11 +++++++++-- 4 files changed, 22 insertions(+), 7 deletions(-) diff --git a/bfd/bfd-in.h b/bfd/bfd-in.h index a477b49..0a81327 100644 --- a/bfd/bfd-in.h +++ b/bfd/bfd-in.h @@ -872,8 +872,8 @@ extern bfd_boolean bfd_elf32_arm_process_before_allocation (bfd *, struct bfd_link_info *); void bfd_elf32_arm_set_target_relocs - (bfd *, struct bfd_link_info *, int, char *, int, int, bfd_arm_vfp11_fix, - int, int, int, int, int); + (bfd *, struct bfd_link_info *, int, char *, int, int, int, + bfd_arm_vfp11_fix, int, int, int, int, int); extern bfd_boolean bfd_elf32_arm_get_bfd_for_interworking (bfd *, struct bfd_link_info *); diff --git a/bfd/bfd-in2.h b/bfd/bfd-in2.h index 22fcdf6..45c5376 100644 --- a/bfd/bfd-in2.h +++ b/bfd/bfd-in2.h @@ -879,8 +879,8 @@ extern bfd_boolean bfd_elf32_arm_process_before_allocation (bfd *, struct bfd_link_info *); void bfd_elf32_arm_set_target_relocs - (bfd *, struct bfd_link_info *, int, char *, int, int, bfd_arm_vfp11_fix, - int, int, int, int, int); + (bfd *, struct bfd_link_info *, int, char *, int, int, int, + bfd_arm_vfp11_fix, int, int, int, int, int); extern bfd_boolean bfd_elf32_arm_get_bfd_for_interworking (bfd *, struct bfd_link_info *); diff --git a/bfd/elf32-arm.c b/bfd/elf32-arm.c index 1f6c1a0..7cbb5f8 100644 --- a/bfd/elf32-arm.c +++ b/bfd/elf32-arm.c @@ -2782,6 +2782,9 @@ struct elf32_arm_link_hash_table /* Nonzero if the ARM/Thumb BLX instructions are available for use. */ int use_blx; + /* Nonzero to prevent BLX instructions from being used. */ + int no_use_blx; + /* What sort of code sequences we should look for which may trigger the VFP11 denorm erratum. */ bfd_arm_vfp11_fix vfp11_fix; @@ -3332,6 +3335,7 @@ elf32_arm_link_hash_table_create (bfd *abfd) #endif ret->fix_v4bx = 0; ret->use_blx = 0; + ret->no_use_blx = 0; ret->vxworks_p = 0; ret->symbian_p = 0; ret->use_rel = 1; @@ -5939,7 +5943,9 @@ check_use_blx (struct elf32_arm_link_hash_table *globals) cpu_arch = bfd_elf_get_obj_attr_int (globals->obfd, OBJ_ATTR_PROC, Tag_CPU_arch); - if (globals->fix_arm1176) + if (globals->no_use_blx) + globals->use_blx = 0; + else if (globals->fix_arm1176) { if (cpu_arch == TAG_CPU_ARCH_V6T2 || cpu_arch > TAG_CPU_ARCH_V6K) globals->use_blx = 1; @@ -6800,6 +6806,7 @@ bfd_elf32_arm_set_target_relocs (struct bfd *output_bfd, char * target2_type, int fix_v4bx, int use_blx, + int no_use_blx, bfd_arm_vfp11_fix vfp11_fix, int no_enum_warn, int no_wchar_warn, int pic_veneer, int fix_cortex_a8, @@ -6825,6 +6832,7 @@ bfd_elf32_arm_set_target_relocs (struct bfd *output_bfd, } globals->fix_v4bx = fix_v4bx; globals->use_blx |= use_blx; + globals->no_use_blx = no_use_blx; globals->vfp11_fix = vfp11_fix; globals->pic_veneer = pic_veneer; globals->fix_cortex_a8 = fix_cortex_a8; diff --git a/ld/emultempl/armelf.em b/ld/emultempl/armelf.em index d29da59..14a0dcf 100644 --- a/ld/emultempl/armelf.em +++ b/ld/emultempl/armelf.em @@ -36,6 +36,7 @@ static int target1_is_rel = 0${TARGET1_IS_REL}; static char *target2_type = "${TARGET2_TYPE}"; static int fix_v4bx = 0; static int use_blx = 0; +static int no_use_blx = 0; static bfd_arm_vfp11_fix vfp11_denorm_fix = BFD_ARM_VFP11_FIX_DEFAULT; static int fix_cortex_a8 = -1; static int no_enum_size_warning = 0; @@ -462,7 +463,7 @@ arm_elf_create_output_section_statements (void) bfd_elf32_arm_set_target_relocs (link_info.output_bfd, &link_info, target1_is_rel, - target2_type, fix_v4bx, use_blx, + target2_type, fix_v4bx, use_blx, no_use_blx, vfp11_denorm_fix, no_enum_size_warning, no_wchar_size_warning, pic_veneer, fix_cortex_a8, @@ -533,6 +534,7 @@ PARSE_AND_LIST_PROLOGUE=' #define OPTION_NO_MERGE_EXIDX_ENTRIES 316 #define OPTION_FIX_ARM1176 317 #define OPTION_NO_FIX_ARM1176 318 +#define OPTION_NO_USE_BLX 319 ' PARSE_AND_LIST_SHORTOPTS=p @@ -547,6 +549,7 @@ PARSE_AND_LIST_LONGOPTS=' { "fix-v4bx", no_argument, NULL, OPTION_FIX_V4BX}, { "fix-v4bx-interworking", no_argument, NULL, OPTION_FIX_V4BX_INTERWORKING}, { "use-blx", no_argument, NULL, OPTION_USE_BLX}, + { "no-use-blx", no_argument, NULL, OPTION_NO_USE_BLX}, { "vfp11-denorm-fix", required_argument, NULL, OPTION_VFP11_DENORM_FIX}, { "no-enum-size-warning", no_argument, NULL, OPTION_NO_ENUM_SIZE_WARNING}, { "pic-veneer", no_argument, NULL, OPTION_PIC_VENEER}, @@ -567,7 +570,7 @@ PARSE_AND_LIST_OPTIONS=' fprintf (file, _(" --target2=<type> Specify definition of R_ARM_TARGET2\n")); fprintf (file, _(" --fix-v4bx Rewrite BX rn as MOV pc, rn for ARMv4\n")); fprintf (file, _(" --fix-v4bx-interworking Rewrite BX rn branch to ARMv4 interworking veneer\n")); - fprintf (file, _(" --use-blx Enable use of BLX instructions\n")); + fprintf (file, _(" --[no-]use-blx Disable/enable use of BLX instructions\n")); fprintf (file, _(" --vfp11-denorm-fix Specify how to fix VFP11 denorm erratum\n")); fprintf (file, _(" --no-enum-size-warning Don'\''t warn about objects with incompatible\n" " enum sizes\n")); @@ -625,6 +628,10 @@ PARSE_AND_LIST_ARGS_CASES=' use_blx = 1; break; + case OPTION_NO_USE_BLX: + no_use_blx = 1; + break; + case OPTION_VFP11_DENORM_FIX: if (strcmp (optarg, "none") == 0) vfp11_denorm_fix = BFD_ARM_VFP11_FIX_NONE; -- 1.7.5.4

13 years, 5 months

2
1
0 0

[ACTIVITY] report week 15

by Peter Maydell

Current Milestones: || || Planned || Estimate || Actual || ||cp15-rework || 2012-01-06 || 2012-04-10 || || Historical Milestones: ||initial-a15-system-model || 2012-01-27 || 2012-01-27 || 2012-01-17 || ||qemu-kvm-getting-started || 2012-03-04?|| 2012-03-04?|| 2012-02-01 || == cp15-rework == * completed last of the register conversions, started on the final check-through and polish before it goes out to the mailing list * implemented changes following review of the clean-up-reset patchset == other == * qemu-linaro 2012.04 final testing (confirming an audio issue on the vexpress model LP:977610 wasn't a regresion) and release * patch review: pl330 dma controller model * patch review: samsung's sd card model overhaul * minor patch: fix compile failure on bsd * minor patch: fix failure to reset timer on a9 mptimer reset * minor patch: diagnose attempts to use python3 at configure time * sent arm-devs.next pullreq * put together a bug report in the form of a youtube video (!) as requested by the gmail folks -- PMM

13 years, 5 months

1
0
0 0

[ACTIVITY] Apr 11 - Apr 13

by Ulrich Weigand

== GCC == * Committed fix for LP #968766 (PR tree-optimization/52880) to FSF mainline and Linaro GCC 4.6 and 4.7. * Created merge reqest to fix LP #972648 for Linaro GCC 4.6 by backporting mainline patch; pending approval. * Updated patch to use vld1.64/vst1.64 instead of vldm/vstm for vector moves. Testing detected problems in GCC core memory alignment logic (GCC assumes vector types are naturally aligned, which contradicts ARM ABI and ARM back-end assumptions). Started discussion on possible fixes. * Updated and retested patch to use vld1/vst1 to implement vec_set/vec_extract for cases where the scalar operand resides in memory. * Ongoing work on fixing LP #959242. * Ongoing work on improving end-of-loop value computation. Mit freundlichen Gruessen / Best Regards Ulrich Weigand -- Dr. Ulrich Weigand | Phone: +49-7031/16-3727 STSM, GNU compiler and toolchain for Linux on System z and Cell/B.E. IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter | Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen | Registergericht: Amtsgericht Stuttgart, HRB 243294

13 years, 5 months

1
0
0 0

Linaro GDB 7.4 2012.04 released

by Thiago Jung Bauermann

The Linaro Toolchain Working Group is pleased to announce the release of Linaro GDB 7.4 2012.04. Linaro GDB 7.4 2012.04 is the second release in the 7.4 series. Based off the latest GDB 7.4, it includes a number of ARM-focused bug fixes and enhancements. Interesting changes include: * gdbserver can now be compiled with Android's toolchain. * Additional fixes from the GDB 7.4 branch, one of them being that it doesn't require makeinfo to build anymore. The source tarball is available at: https://launchpad.net/gdb-linaro/+milestone/7.4-2012.04 More information on Linaro GDB is available at: https://launchpad.net/gdb-linaro -- []'s Thiago Jung Bauermann Linaro Toolchain Working Group

13 years, 5 months

1
0
0 0

[ANNOUNCE] Linaro QEMU 2012.04 released

by Peter Maydell

The Linaro Toolchain Working Group is pleased to announce the release of Linaro QEMU 2012.04. Linaro QEMU 2012.04 is the latest monthly release of qemu-linaro. Based off upstream (trunk) QEMU, it includes a number of ARM-focused bug fixes and enhancements. New in this month's release: - ppoll syscall now supported in ARM linux-user mode - the SETEND instruction in the Thumb encoding now UNDEFs to match behaviour for the ARM encoding - the OMAP36xx UART FIFO status registers are now implemented (thanks to Jan Vesely) Known issues: - Graphics do not work for OMAP3 based models (beagle, overo) with 11.10 Linaro images. - Audio may not work on Versatile Express models with the latest Linaro kernel/hardware packs (LP:977610). The source tarball is available at: https://launchpad.net/qemu-linaro/+milestone/2012.03 More information on Linaro QEMU is available at: https://launchpad.net/qemu-linaro

13 years, 5 months

1
1
0 0

[ANNOUNCE] Linaro GCC 4.7 and 4.6 2012.04 released

by Michael Hope

The Linaro Toolchain Working Group is pleased to announce the 2012.04 release of both Linaro GCC 4.7 and Linaro GCC 4.6. Linaro GCC 4.7 2012.04 is the first release in the 4.7 series. Based off the latest GCC 4.7.0+svn186061 release, it includes performance improvements especially around 64 bit operations. Interesting changes include: * Our first 4.7 based release * Updates to GCC 4.7.0+svn186061 * Better use of 16 bit Thumb-2 instructions for smaller code size * Implements 64 bit ones complement in NEON * Adds support for the ARMv6 saturation instructions * Backports the NEON lexer improvements for faster compilation * Backports the 64 bit multiply, divide, and mod improvements Fixes: * LP: #960283 slp pass assert when compiler configure with --enable-checking Linaro GCC 4.6 2012.04 is the fourteenth release in the 4.6 series. Based off the latest GCC 4.6.3+svn186060 release, this is the first release after entering maintenance. Interesting changes include: * Updates to 4.6.3+svn186060 Fixes: * LP: #960283 slp pass assert when compiler configure with --enable-checking The source tarballs are available from: https://launchpad.net/gcc-linaro/+milestone/4.7-2012.04 https://launchpad.net/gcc-linaro/+milestone/4.6-2012.04 Downloads are available from the Linaro GCC page on Launchpad: https://launchpad.net/gcc-linaro More information on the features and issues are available from the release page: https://launchpad.net/gcc-linaro/4.7/4.7-2012.04 Mailing list: http://lists.linaro.org/mailman/listinfo/linaro-toolchain Bugs: https://bugs.launchpad.net/gcc-linaro/ Questions? https://ask.linaro.org/ Interested in commercial support? Inquire at support(a)linaro.org -- Michael

13 years, 5 months

1
0
0 0

O2 optimization with vectorize

by Singh, Ravi Kumar (Ravi)

All, In the below code, I tried few compiler options and got following observations: 1) arm-linux-gnueabi-gcc -O2 -mcpu=cortex-a15 -mfpu=neon -ftree-vectorizer-verbose=6 -ftree-vectorize Compiler throws following info messages: foo.c:16: note: not vectorized: unsupported use in stmt. foo.c:16: note: not vectorized: unsupported use in stmt. foo.c:18: note: not vectorized: unsupported use in stmt. foo.c:18: note: not vectorized: unsupported use in stmt. 2) -O2 -mcpu=cortex-a15 -mfpu=neon None of the generated code contains the NEON instructions. Code generated with case 1 is taking 3000 cycles, and code generated by option 2 is taking 2500 cycles. Even if vectorization failed in case1, it should not generate more inefficient code than case 2. My belief was that the executables from both would take same cycles, any thing done for doing unsuccessful vectorization must be reverted if it did not succeed. ################################################################### #define SIZE1 20 #define SIZE2 26 unsigned int array[SIZE1][SIZE2]; void foo() { unsigned int i,j; unsigned int max = 0; for(i = 0; i < SIZE1; i++) { for(j = 0; j < SIZE2; j++) { if (array[i][j] > max) { max = array[i][j]; index = j; } } } printf("Max value: %u Index: %u\n", max, index); } Regards RKS

13 years, 5 months

2
3
0 0

2012.04 release prep

by Michael Hope

Hi there. The 2012.04 toolchain release is this week. Ulrich, I see your fix for LP: #968766 has been approved upstream. In theory it's too late but I'm happy to land it if you are. Could you decide and let Andrew know by the middle of Tuesday? Andrew, if you don't hear from Ulrich then spin away. Andrew, could you run the release process on Tuesday please? There's one extra step this month: once you've uploaded and spawned the job, go to the scheduler screen and click on 'Release' beside each of the ursas. I reserved them to make sure they'd be idle and ready to pick up the release build when ready. Thiago, let us know if Ulrich or I can lend a hand with the GDB release. -- Michael

13 years, 5 months

2
2
0 0

Changing the time of the fortnightly performance call

by Ramana Radhakrishnan

Hi there, At the last call Michael asked if we could push this call back by 30 minutes given the changes due to daylight savings. Does anyone have any objections to a new time of 10 a.m. BST - 11 a.m. Central European - 9 p.m. New Zealand. ? cheers Ramana

13 years, 5 months

3
3
0 0

[ACTIVITY] 2nd - 5th April

by Andrew Stubbs

* GCC Identified the latent bug that's upset my NEON-shifts testing. It turns out the define-insn-and-shift patterns in arm/sync.md have no length attributes set. Now that the NEON 64-bit shifts appear to be not broken, I've relaunched the 64-bit extend testing. Identified the problem with my NEON-64-bit-negate patch: I already knew it works better (produces more optimal code) with my NEON-immediates patch, but it turns out that at -O0 the other patch is a hard requirement or else bad things happen in output_move_vfp. Backported Ramana's patch for ARM-mode testing of my recent Thumb 64-bit test cases. I've applied it to Linaro GCC directly, without a merge proposal, as it's a very low-risk patch. Caught up with some launchpad blueprint fiddling. Completed the merges from 4.6 and 4.7 FSF. The 4.7 merge was tricky as it required working around a BZR bug; I've posted the workaround to the toolchain list. * Other On leave on Tuesday Public holiday on Friday. Attached a copy of the ARM Linux ABI document to KBentry 39 so we're hosting it somewhere, at least. Posted an internal Mentor/CS question about getting its old home restored, and getting a relicensed edition to allow others to use it as the basis for a hard-float equivalent.

13 years, 5 months

1
0
0 0

[Activity] Week 14

by Ramana Radhakrishnan

=== Progress === * Worked on VFP addressing patch and corrected the failures. * Got SPEC2k up and running with hot cold partitioning. Some SEGVs that need investigation. In general results appear to be better in quite a few cases. * Investigated an issue with a merge request for upstream 4.7 branch into our tree. There was a testsuite failure and I wasn't able to reproduce it with a local i386 rebuild of the toolchain. Therefore we'll have to let this go in. == Plans == * I will be away for 2 days this week attending the LLVM conference in London. * Pursue backporting gnu_unique_object upstream. * Finish off the VFP addressing modes patch upstream. * Look at some of the existing blueprints and start discussions around prioritizing this. * Investigate some of the SEGVs with h-c partitioning. Absences. * Apr 12-13 : Euro-LLVM London. * Linaro Connect Q2.12 - May 28 - June 1 -

13 years, 5 months

1
0
0 0

[Activity] Week 14

by Zhenqiang Chen

Summary: * Revise the patch for relocatable NLS support. * Code size benchmark analysis. Details: 1. Revise the patch for relocatable NLS support: lp:918926. * Read the gcc configure and makefile. * It seams hard to get the relative dir if the gcc is configured with --bindir=... --datadir/datarootdir. E.g. --bindir=/opt/bin --datarootdir=/tmp/data 2. Code size benchmark analysis with -Os * Investigate regression in small cases. 3. Try to build linaro gcc trunk with crosstool-ng. But it reports error when configuring libquadmath. * configure:9829: error: Link tests are not allowed after GCC_NO_EXECUTABLES. * Manual check or a simple case show libc.so can be linked. Plans: * Tuning optimization heuristics for -Os Planed leaves: * April 9 - 11: Vacations Best regards! -Zhenqiang

13 years, 5 months

1
0
0 0

[ACTIVITY] report week 14

by Peter Maydell

Current Milestones: || || Planned || Estimate || Actual || ||cp15-rework || 2012-01-06 || 2012-04-10 || || Historical Milestones: ||initial-a15-system-model || 2012-01-27 || 2012-01-27 || 2012-01-17 || ||qemu-kvm-getting-started || 2012-03-04?|| 2012-03-04?|| 2012-02-01 || == other == * LP:970252 got a beagle board booting so I could read the UART version register; reviewed and applied to qemu-linaro the set of patches provided by Jan Vesely (thanks!) * sent a patchset cleaning up the GIC model so it is a self-contained sysbus device; this should make it easier to just drop in a functionally equivalent device which is a shim for an in-kernel GIC model that uses the hardware VGIC features * upstream review: save/load support for sd.c [patchset from Samsung] SPI bus [patchset from Petalogix] * put together qemu-linaro prerelease tarball and did some testing * performance evaluation finished and submitted

13 years, 5 months

1
0
0 0

[ACTIVITY] 26th - 30th March

by Andrew Stubbs

Continued work on neon 64-bit correctness. This is really dragging out now. I had hoped to have had it fixed by now, but subtle bugs are subtle. The 16-bit opcodes patch is now committed both upstream and in Linaro GCC 4.7, however, so that's some progress at least. Posted benchmark results for the the 64-bit shifts in core registers. The results are inconclusive: the benchmark runs are too noisy.

13 years, 5 months

1
0
0 0

Binary build release process

by Michael Hope

As part of closing out the Windows toolchain card, I've documented the binary build release process at: https://wiki.linaro.org/WorkingGroups/ToolChain/BinaryBuild/ReleaseProcess The interesting thing is a script that pulls builds from S3 and posts them to Launchpad. There's a curl command at the end that does the upload and might be useful. -- Michael

13 years, 5 months

1
0
0 0

Re: [Linaro-toolchain-builds] [cbuild] eglibc-2.16~svn17843 armv7l completed

by Michael Hope

On 1 April 2012 05:56, Ramana Radhakrishnan <ramana.radhakrishnan(a)linaro.org> wrote: > I find it a bit worrying that all the nptl tests are failing with a > common error message > > http://builds.linaro.org/toolchain/eglibc-2.16~svn17843 > > Aborted' > make[6]: *** [/scratch/cbuild/slave/slaves/tcpanda05/eglibc-2.16~svn17843/eglibc/default/build/nptl/tst-cond7.out] > Error 1 > libgcc_s.so.1 must be installed for pthread_cancel to work > Didn't expect signal from child: got `Aborted' > > Why don't we have libgcc_s.so.1 installed on the system - shouldn't > that be there if there was a gcc properly installed on the system ? This is a bug on my side. I believe EGLIBC likes to have libgcc_s.so in the top of the build directory - at least that's the impression I got from reading the cross-test documentation the other day. I've logged LP: #971064 and will look into it. -- Michael

13 years, 5 months

1
1
0 0

GCC 4.7 runtime library plans

by Michael Hope

Hi Ricardo, Matthias. GCC 4.7 is almost here and it's likely that Linaro GCC 4.7 will come out for next month's 2012.04 milestone. For the binary toolchain to work we need the 4.7 runtime libraries on the target. Matthias, what are your plans? How much of 4.7 is packaged so far? Ricardo, could we pull these updates to libgcc, libstdc++, and others into the LEB? These should be backwards compatible but there's always a risk. Using the 4.5 runtime with a 4.4 compiler back on Maverick was OK. -- Michaele

13 years, 5 months

3
6
0 0

[ACTIVITY] March 26 - March 30

by Thiago Jung Bauermann

Hi, GDB for Android: * Submitted upstream three patches for building gdbserver on Android. Reworked two of them based on review comments, and committed one. * Investigated ARM EABI build attributes and .note.ABI-tag as ways of marking binaries as Android apps so that GDB can differentiate them from regular Linux ARM binaries. Build attributes are quite sophisticate and overkill for this purpose, and would also be out of place for Android on x86. .note.ABI-tag is simpler and more appropriate. Now experimenting with generating the .note.ABI-tag section on Android binaries. * Tried to find ARM GNU/Linux ABI supplement [1] but couldn't, contacted Mentor Graphics' webmaster about the problem. No response so far. Obs: This Friday (04/06) will be a holiday in Brazil and hopefully I will be AFK. [1] http://www.codesourcery.com/gnu_toolchains/arm/arm_gnu_linux_abi.pdf -- []'s Thiago Jung Bauermann Linaro Toolchain Working Group

13 years, 5 months

1
0
0 0

[ACTIVITY] Mar 26 - Mar 30

by Ulrich Weigand

== GCC == * Committed fix for LP #960283 (PR tree-optimization/52686) to FSF mainline as well as Linaro GCC 4.6 and 4.7. * Worked on patch to use vld1.64/vst1.64 instead of vldm/vstm for vector moves. Created merge request for testing. * Worked on patch to use vld1/vst1 to implement vec_set/vec_extract for cases where the scalar operand resides in memory. Created merge request for testing. * Ongoing work on fixing LP #959242. * Ongoing work on improving end-of-loop value computation. == Misc == * I'll be attending the Linux Foundation Collaboration Summit in San Francisco next week, and present on "GDB on ARM". Mit freundlichen Gruessen / Best Regards Ulrich Weigand -- Dr. Ulrich Weigand | Phone: +49-7031/16-3727 STSM, GNU compiler and toolchain for Linux on System z and Cell/B.E. IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter | Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen | Registergericht: Amtsgericht Stuttgart, HRB 243294

13 years, 5 months

1
0
0 0

[Activity] Week 13

by Zhenqiang Chen

Summary: * Linaro binary toolchain 2012.03 release. * Investigate relocatable NLS support. * Code size benchmark analysis. Details: 1. Linaro binary toolchain 2012.03 release. * Bump and spawn 2012.02-20120326 build. * Validate the release candidate. * Update wiki for binary build tasks. 2. Investigate relocatable NLS support: lp:918926. * Root cause: gcc and binutils use a fixed LOCALEDIR (which is $prefix/share/locale) to call bindtextdomain. * Workout a reference patch for gcc to use relative dir (.../bin/../share/locale) to call bindtextdomain. 3. Code size benchmark analysis with -Os * Collect code size benchmark data. * In most cases, gcc 4.7 gets better result than gcc 4.6. * Investigate regression in several small cases. 4. Read the tree and rtl dump files to learn the optimizations and impacts on code size. Plans: * Fix lp:918926. * Investigate code size regression in gcc 4.7. * Tuning optimization heuristics for -Os. Planed leaves: * April 2 - 4: Chinese Qingming Festival. * April 9 - 11: Vacations Best regards! -Zhenqiang

13 years, 5 months

1
0
0 0

[Activity] Week 13

by Ramana Radhakrishnan

=== Progress === * Caught up on email backlog. * Reworked the ARM backend specific bits of the VFP addressing modes patch and submitted again for some benchmarking and testing. Finished the PRE_MODIFY and POST_MODIFY bits of that as well. * Wrote up a small blueprint on the shrink-wrapping work. * Wrote up my Linaro performance review and sent it for review. * Looked at lower-subreg work that Kenneth Zadeck posted very quickly to see if it addressed some of the issues around and old intrinsics patch that Richard Sandiford submitted last year. It looks promising and might even have some impact on our 64 bit neon work . It fixes the 2 cases where things didn't look good. ( Upstream bug reports PR48941 and PR51980) but it falls over while building glibc. Sent a bug report to Kenneth about this. * The perf packages on OMAP4 in our latest releases from 12.03 are just broken, they don't work. Reported the issue to Paul Larson on IRC to check what's going on. perf top doesn't work reliably on the kernels and there appears to be some issues with interrupt support for some of these . I specifically ran into https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/956693 . * Answered a few questions from Uli about my prototypes for the vld1 replacing vldm instructions and a vget_lane patch. == Plans == * Work through some of the blueprints before the call next week. * Set up perf on my panda. It works on my AC100 - so the inclination was to also have something that worked on my panda but clearly it doesn't. * Finish off the VFP addressing modes patch and get it in. * Look at Partial Partial PRE next or attempt the next project. Absences. * Apr 12-13 : Euro-LLVM London. * 1 week holiday sometime before that - to be booked * Linaro Connect Q2.12 - May 28 - June 1 - travel booked - hotel to be booked.

13 years, 5 months

1
0
0 0

[ACTIVITY] report week 13

by Peter Maydell

Current Milestones: || || Planned || Estimate || Actual || ||cp15-rework || 2012-01-06 || 2012-04-10 || || Historical Milestones: ||initial-a15-system-model || 2012-01-27 || 2012-01-27 || 2012-01-17 || ||qemu-kvm-getting-started || 2012-03-04?|| 2012-03-04?|| 2012-02-01 || == cp15-rework == * posted 14-patch patchset which creates a QOM class per CPU type and moves a lot of the reset/constant-feature-register setup to the init functions for these new classes. This is then a much nicer base to sit cp15 rework on. * solved the final design knot of how to handle registers whose reset value depends on the CPU type (the QOM patches make this much more straightforward) == other == * upstream patch review * updated Paul Brook's BE8 userspace support patch and sent out a v2 * ran through qemu-linaro buglist identifying fixes to go into next release * linaro performance review ate up a lot of time this week and will probably do so next week too :-(

13 years, 5 months

1
0
0 0

Shrink wrapping blueprint.

by Ramana Radhakrishnan

I've written up a blueprint for Shrink-wrapping here. https://blueprints.launchpad.net/gcc-linaro/+spec/shrink-wrapping Comments are welcome. Ramana

13 years, 5 months

1
0
0 0

Agenda for performance call on April 3.

by Ramana Radhakrishnan

https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2012-04-03 If there's anything people would like to add please do so on the wiki page. Ramana

13 years, 5 months

1
0
0 0

Agenda for Monday

by Michael Hope

...is up at: https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2012-04-02 Feel free to add items. Andrew, could you look into the 4.7 bzr merge problem before then? -- Michael

13 years, 5 months

1
0
0 0

4.7 is now the Launchpad dev focus

by Michael Hope

I've changed the development focus in the Launchpad project to Linaro GCC 4.7. This means that: * Checking out lp:gcc-linaro now gives you the 4.7 branch * New merge requests are targeted to 4.7 by default This doesn't affect any already checked out branches or pending merge requests. -- Michael

13 years, 5 months

1
0
0 0

[ACTIVITY] March 19 - March 23

by Thiago Jung Bauermann

Hi, GDB for Android: * Wrote three patches for the build system allowing gdbserver to be cross-compiled on Android [which were submitted upstream this Monday]. * Started studying the ARM EABI to work on a way to mark a binary as an Android application as opposed to a regular Linux EABI one. * Wrote self-evaluation for Linaro performance review. -- []'s Thiago Jung Bauermann Linaro Toolchain Working Group

13 years, 5 months

1
0
0 0

GCC build speed and backlog

by Michael Hope

The PandaBoard auto builders are having a hard time keeping with longer build and test times of 4.7 and the re-enabled libstdc++ tests. For reference, here's how much each step costs: Bootstrap GCC with C, C++, Fortran, and Obj-C: 9 hours Test GCC: 9.5 hours Test libstdc++: 4.4 hours Test libgomp: 0.9 hours Other tests: 0.2 hours for a grand total of 23.8 hours. Every new commit gives a merge request and trunk build for both A9 and ARMv5 giving 95 hours of compute time. GCC 4.6 takes five hours to build and 5.5 to test. This is just a FYI. I'll think about ways of speeding things up or adding capacity. An i.MX6 with 2 GB of RAM and SATA would be nice... -- Michael

13 years, 5 months

2
2
0 0

Once again bogus testsuite failures

by Ulrich Weigand

Hi Michael, I'm seeing what looks like bogus testsuite failures again: https://code.launchpad.net/~uweigand/gcc-linaro/lp-960283-4.7/+merge/99069 I suspect this is still caused by the .ident version string, which now appears to be: [gcc-linaro/~uweigand revision 114974] While it no longer contains the branch name, it still contains my user name, which happens to include the string "and" ... Mit freundlichen Gruessen / Best Regards Ulrich Weigand -- Dr. Ulrich Weigand | Phone: +49-7031/16-3727 STSM, GNU compiler and toolchain for Linux on System z and Cell/B.E. IBM Deutschland Research & Development GmbH Vorsitzende des Aufsichtsrats: Martina Koederitz | Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen | Registergericht: Amtsgericht Stuttgart, HRB 243294

13 years, 5 months

2
1
0 0

[Activity] Week 12

by Ramana Radhakrishnan

== Progress === * Off sick for 4 days last week. * Looked at the results for the vfp writeback modes and caught up with some analysis on the one day I did work. === Plans === * Catch up on email after absences. * Catch up on patches backlog Absences. * Apr 12-13 : Euro-LLVM London. * 1 week holiday sometime before that - to be booked * Linaro Connect Q2.12 - May 28 - June 1 - travel booked - hotel to be booked. ---

13 years, 5 months

1
0
0 0

[ACTIVITY] 19th 23rd March

by Andrew Stubbs

* Linaro GCC Applied my ARM conditional-execution and thumb 16-bit instruction size optimization patch to upstream and Linaro 4.7. Continued work on (slowly) working the bugs out of my 64-bit NEON patches. Figuring out bootstrap failures is not easy! Eventually discovered that: * the NEON shifts patch was broken because combine was using the patterns in ways they weren't intended. * the NEON neg patch was broken because it needed an early-clobber marker on the scratch register. I've also reworked the use of insn_enabled to make it a little less clunky. It's just an aesthetic change though. If all goes well with my weekend bootstrap builds I should have the patches reposted next week. * Other Richard Earnshaw asked me to bless use of a CS patch submitted to gcc-patches@ by a third party. I dug out the original patch from the CS archives and posted that to the message thread.

13 years, 5 months

1
0
0 0

[Activity] Week 12

by Zhenqiang Chen

Summary: * Validation for embedded toolchain 2012q1 update release and Linaro binary toolchain 2012.03 release. * Failed case analysis for -Os. * Read benchmark code Details: 1. Validation for embedded toolchain 2012q1 update release and Linaro binary toolchain 2012.03 release. 2. Root cause the new failed cased pr30951.c with -Os. In function tree_swap_operands_p (fold-const.c), there is a check if (optimize_function_for_size_p (cfun)) return 0; which blocks to swap (x != x + 10) to (x + 10 != x). And the following optimization can only handle (x + 10 != x). 3. Read some benchmark codes to find the opportunities for code size optimization. Plans: * Finalize Linaro binary toolchain 2012.03 release. * Read benchmark codes. Best regards! -Zhenqiang

13 years, 5 months

1
0
0 0

KVM blueprints

by Michael Hope

I've finished creating the KVM blueprints for the remains of this quarter. You can find them by burrowing down from the top level category blueprints: Everything that is new development: https://blueprints.launchpad.net/linaro-toolchain-misc/+spec/kvm-development Everything that is platforms and integration: https://blueprints.launchpad.net/linaro-toolchain-misc/+spec/kvm-integration I've also marked up the original wiki page with links to the blueprints: https://wiki.linaro.org/MichaelHope/Sandbox/Q1.12ToDo Some are placeholders pending agreement or being superceeded by existing cards in other teams. Now I need to figure out how to track them. -- Michael

13 years, 5 months

1
0
0 0

[ACTIVITY] report week 11

by Peter Maydell

Current Milestones: || || Planned || Estimate || Actual || ||cp15-rework || 2012-01-06 || 2012-03-30 || || Historical Milestones: ||initial-a15-system-model || 2012-01-27 || 2012-01-27 || 2012-01-17 || ||qemu-kvm-getting-started || 2012-03-04?|| 2012-03-04?|| 2012-02-01 || == cp15-rework == * more progress, mostly in figuring out how to connect the cp15 patches with work by Andreas Färber to convert CPUs to QEMU's new object model. * Patch series is now 36 patches long... (will probably split into two parts for submission) == other == * upstream patch review * linaro performance review time again... -- PMM

13 years, 5 months

1
0
0 0

[ACTIVITY] Mar 19 - Mar 23

by Ulrich Weigand

== GCC == * Posted second part of fwprop-subreg patch to gcc-patches. * Investigated LP #960283, determined root cause, created patch, and opened merge requests against Linaro GCC 4.6 and 4.7. Opened mainline bugzilla PR tree-optimization/52686. * Investigated LP #960274 and LP #960817, identified both as duplicates of LP #960283. * Investigated LP #959242, determined root cause. Ongoing investigation of possible fixes. * Ongoing work on improving end-of-loop value computation. Mit freundlichen Gruessen / Best Regards Ulrich Weigand -- Dr. Ulrich Weigand | Phone: +49-7031/16-3727 STSM, GNU compiler and toolchain for Linux on System z and Cell/B.E. IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter | Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen | Registergericht: Amtsgericht Stuttgart, HRB 243294

13 years, 5 months

1
0
0 0

Agenda for Monday

by Michael Hope

The draft agenda for Monday's call is at: https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2012-03-26 and is: * Review action items from last meeting * Validation lab move is delayed * Daylight savings changes done * KVM * Blueprints are (half) spawned * Rusty away prep * Other business * multiarch * [[MichaelHope/Sandbox/MultiarchNotes]] * Want to get upstream(s) * Richard's thoughts * Interaction with multilib * Reducing the number of builds * 4.7 status * Import/merge working? * Keep an eye out for other improvements/regressions Feel free to edit! -- Michael

13 years, 5 months

1
0
0 0

Getting multiarch upstream

by Michael Hope

Konstantinos, Loïc, and I talked last night about multiarch. Linaro want multiarch and will use it in all our products and hence need to get it upstream. There's another meeting in a week to figure out what's next. I've written a page on the uses, issues, and history at: https://wiki.linaro.org/MichaelHope/Sandbox/MultiarchNotes Please edit and add and correct things. The page isn't Linaro's position but we need to have answers for the arguments. I see no particular blockers especially if we separate the concerns. -- Michael

13 years, 5 months

1
0
0 0

Basic porter access to the tcpandas

by Michael Hope

I've added a new job called 'porter' which reserves the first tcpanda that comes free. This can be used to reproduce a bug or benchmark result against an existing binary build. For example, say you want to see if a fault exists on recent trunk: * Go to http://ex.seabright.co.nz/helpers/buildlog/gcc-4.8 * See the last successful ARM build was gcc-4.8~svn185503 * Go to http://ex.seabright.co.nz/helpers/scheduler/spawn * Spawn a job called 'porter' into the a9-builder queue * Keep polling http://ex.seabright.co.nz/helpers/scheduler until a board shows as 'porter/ready' * Log into the board using ssh cbuild(a)board.v * Change to /scratch/cbuild/slave/slaves * rsync the binary across using rsync control:~/cbuild/build/gcc-4.8~svn185503/gcc-*cortexa9*xz . * Extract the binary and have at it The board will drop back into the queue after 48 hours. You can release it early by doing a 'killall sleep'. Please do any work under /scratch/cbuild/slave/slaves as this is automatically deleted when the next job starts. Zhenqiang, could you add this to the jobs page please? -- Michael

13 years, 6 months

1
0
0 0

libav inline assembly

by Michael Hope

I've create a blueprint covering the basic functions in libav that are implemented as inline assembly: https://blueprints.launchpad.net/gcc-linaro/+spec/investigate-libav-inline-… These are a mix of multiplies, clipping, byte swap, and unaligned access. We do OK on half of them but at least byte swap and 32x32 -> top half of 64 aren't as good as they could be. Let's discuss the investigation at the next performance meeting. -- Michael

13 years, 6 months

2
2
0 0

[ACTIVITY] March 12 - March 16

by Thiago Jung Bauermann

Hi, Linaro bugs: - #926472: Native gdb can't know multithreads of Android processes Tried to reproduce but couldn't do a GDB build similar to the bug reporter's. Found a workaround for him anyway. - #942529: gdb failed to debug application (gdb reports about internal error) Reproduced the bug and found out it's fixed in GDB 7.4. It's a bug in Ubuntu GDB not Linaro, so reassigned to the Ubuntu project. Linaro GDB is already at version 7.4 so we're good. - #954714: dropped patch reintroduces gcore relro backtrace problem Reviewed the proposed patch. It's good. GDB for Android: - Started creating patches for build problems when trying to compile gdbserver for Android. Will have patches to submit in the next few days. - Studied libthread_db.c to see what's special about it that it has to be statically linked. Didn't find anything and indeed Android's own libthread_db.so works fine. Didn't get an answer yet when I asked about it on the Android mailing list. -- []'s Thiago Jung Bauermann Linaro Toolchain Working Group

13 years, 6 months

2
1
0 0

[ACTIVITY] w12

by Asa Sandahl

Hi! * Moved the v8 wiki page the the Benchmark section, and corrected the documentation a bit: https://wiki.linaro.org/WorkingGroups/ToolChain/Benchmarks/V8_And_SunSpider * Pushed the v8 cbuild make file to: https://code.launchpad.net/~linaro-toolchain-dev/cbuild/trunk Note that the file containing the v8 source code and SunSpider must be added under cbuild/files. You can find the file attached to the wiki page above. * Pushed the parser for the SunSpider results: https://code.launchpad.net/~linaro-toolchain-dev/linaro-toolchain-benchmark… * Pushed the v8 benchmarking results: https://code.launchpad.net/~linaro-toolchain-wg/linaro-toolchain-benchmarks… Regards Åsa

13 years, 6 months

1
0
0 0

[Activity] Week 11

by Ramana Radhakrishnan

==Progress=== * Did some work to improve code generation for addressing modes in VFP registers. * Looked at some more cases and detected that there are 2 areas of improvement for the future * shrink-wrapping * Too many unnecessary ldm / stm stacking for cases with small structures being passed . * Committed configure.ac changes. * Committed MALLOC_ABI_ALIGNMENT changes. * Looked at some upstream testsuite failures. There are about 54 too many test failures in vect.exp that need to be looked at at some point. === Plans === * Push vfp wb patches upstream. * Resurrect partial-partial PRE Absences. * 1 week holiday sometime before that - to be booked * Linaro Connect Q2.12 - May 28 - June 1 - travel booked - hotel to be booked.

13 years, 6 months

1
0
0 0

libav blueprints

by Michael Hope

I've created blueprints for the libav missed optimisations and added references to Ramana's page at: https://wiki.linaro.org/RamanaRadhakrishnan/Sandbox/RRQ112ConnectLibavgcc46… Those that are new and in progress I've assigned to the relevant person. Ulrich, I couldn't find a end of loop counter blueprint so I created a new one. -- Michael

13 years, 6 months

1
0
0 0

Linaro GCC 4.6 entering maintenance; 4.5 end of life

by Michael Hope

This is the first announcement on upcoming changes to the supported Linaro GCC versions. GCC 4.7 is expected out in the next two weeks. We plan to switch to 4.7 for the Linaro GCC 2012.04 release and, as part of that, will put Linaro GCC 4.6 into maintenance and retire Linaro GCC 4.5. While in maintenance we will continue to update, fix bugs, and do releases on 4.6. No further changes or releases will be made to 4.5. All historical releases and branches will stay available. For more informatio, please see the flyer at: https://wiki.linaro.org/WorkingGroups/ToolChain/Flyer especially the section on Lifecycle: https://wiki.linaro.org/WorkingGroups/ToolChain/Flyer#Lifecycle The formal change notes will be sent after the 2012.04 release. -- Michael

13 years, 6 months

2
2
0 0

[ACTIVITY] weekly status

by Ken Werner

Hi, OpenEmbedded: * rebased against current OE-core * my patch that introduces an image fs alignment is now upstream * noticed that the newly introduced bdwgc recipe (the Hans Boehm Garbage collector which is needed by guile) uses a version of libatomic that fails when building in Thumb mode * has been fixed upstream already * pulseaudio/libatomics-ops_1.2.bb has the same issue and just sets ARM_INSTRUCTION_SET to "arm" (probably until a new version gets pulled in) * we can use the same workaround till then * found a bug in the recipe for the Linaro external binary toolchain where some header files are placed into a wrong directory during the install step * which prevents python from being built * now fixed Please note that I'll be on vacation till 04/13/2012. Regards, Ken

13 years, 6 months

1
0
0 0

OpenEmbedded blueprints

by Michael Hope

Hi Ken. I've made a meta-linaro project on Launchpad and created the near term blueprints. See: https://blueprints.launchpad.net/meta-linaro You're almost done with the initial layer work. Next is scripting up the build and integrating with LAVA followed by turning on the build for other architectures. I've dropped the build in the cloud investigation. Let's use tcserver01 as it works and is fast enough. Keep an eye on the validation lab cloud the Validation guys are talking about - we might shift there later. I've sent the draft card to Loïc who will massage the text and get it on the TSC agenda. The current blueprints focus on toolchain validation and come to a hard stop past there. Once we have TSC approval we can go further and talk with the Platforms guys about who does what. -- Michael

13 years, 6 months

2
1
0 0

tcpanda auto builders going offline

by Michael Hope

The Validation lab is shifting to a new location this week so I've started a graceful shutdown of the tcpanda boards. Merge requests will continue to queue and run on x86 but will back up until the lab comes online at the end of this week. If the backlog gets too big then I'll re-enable an ursa board or two. Please work as normal but expect the builds results to take longer to come through. -- Michael

13 years, 6 months

1
0
0 0

Plan for changing the binary toolchain to 4.7 and hardfloat

by Michael Hope

Hi there. Over the next three months both GCC 4.7 and Ubuntu 12.04 'Precise' are coming out. We'll switch over to these pretty quickly which will affect our internal testing and anyone using the binary toolchain. The changeover plan including dates, details of what's happening, and backwards compatibility is at: https://wiki.linaro.org/MichaelHope/Sandbox/BinariesMigration Comments and concerns are welcome, -- Michael

13 years, 6 months

6
8
0 0

[ACTIVITY] 12th - 17th March

by Andrew Stubbs

* Linaro GCC Spun release tarballs for Linaro GCC 4.5 and 4.6. Launched the build and test runs. When those completed, briefly checked the results, and launched the package build tests and benchmark runs. Continued trying to figure out how my NEON 64-bit immediates patch had caused a bootstrap failure. The problem turned out to be an assembler bug ([1]). I've adjusted my patch to work around the problem. This is the only real way to do it given that, even if I fixed the assembler right away, there'll be broken assemblers knocking around for some time to come. The compiler now bootstraps correctly in a manual build. I've submitted it for testing on Michael's systems, so hopefully this patch will be ready to post back upstream soonish. Continued trying to figure out the neon shifts bootstrap failure. I ran a cross-compiler test suite run, but didn't witness any obvious problems. Launched a manual bootstrap to reproduce the problem (once the board because available after testing the immediates patch), so I should have something to work with next week. Attempted to merge lp:gcc/4.7 to lp:gcc-linaro/4.7, but got a bzr error. I asked for help on #bzr, and 'jelmer' is looking into it. Apparently the history didn't import in quite the same way as lp:gcc/trunk, or something. Helped Dmitry Antipov with a relocation (possible) bug. * Other Two days leave (Thursday and Friday). Booked flights and hotels to Hong Kong for Linaro Connect Q2.12 [1] http://sourceware.org/bugzilla/show_bug.cgi?id=13843

13 years, 6 months

1
0
0 0

[Activity] Week 11

by Zhenqiang Chen

Summary: * Linaro binary toolchain 2012.03 release. * Make multilib and multiarch work together. * Failed case analysis for -Os. Details: 1. Handover Asa's linaro day-to-day jobs (check auto build health, proposals health and ticket triage) 2. Linaro binary toolchain 2012.03 release. * Update config to 2012.03 * Fix lp:939008 and patch for lp:939143 3. Multilib/multiarch investigation for linaro toolchain. * Update the logic in set_multilib_dir to set multiarch_dir when it matches the format (.:.:$(MULTIARCH_DIRNAME)). Now multilib and multiarch can work together. A reference build to support marm/march=armv5t is at http://people.linaro.org/~zhenqiangchen/ * Try to build -mfoat-abi=hard/-fpu=neon. But libgcc build fails with message "ld: error ... uses VFP register arguments, ..." 4. Investigate new failed cases in -Os regression test. * For gcc.dg/pr30951.c, both option -O0 and -O2 can optimize (x == x + 10) to (0). But -Os can not. * For gcc.dg/atomic-lockfree.c and gcc.dg/atomic-noinline.c, the optimization is correct. The test cases can only be test with -O0. Plans: * Code size benchmark tuning. Best regards! -Zhenqiang

13 years, 6 months

1
0
0 0

[ACTIVITY] w11

by Asa Sandahl

Hi! * V8 - SunSpider The pieces for building in cbuild and parsing with the linaro-toolchain-benchmark scripts are in place. Ran the SunSpider benchmark across a few toolchains with the o2-neon and o3-neon variants. I have documented my work on this page, but not analyzed the results yet. https://wiki.linaro.org/AsaSandahl/Sandbox/JavaScriptBenchmark What worries me is that there is too much variation in some of the test results. Probably caused by the garbage collection kicking in at unpredictable times. I will try to monitor the gc and investigate if it can be controlled somehow. I would like to do a gcc-4.4 run as well. Android's original toolchain is based on gcc-4.4.3(?) and that is what I compared against when doing measurements internally. However, I have problem compiling C++ with gcc-4.4 - it is this one again: home/asa-san/cbuild/slaves/ursa3/gcc-4.4.5/gcc-binary/bin/../libexec/gcc/armv7l-unknown-linux-gnueabi/4.4.5/cc1plus: /home/asa-san/cbuild/slaves/ursa3/gcc-4.4.5/gcc-binary/lib/libstdc++.so.6: version `GLIBCXX_3.4.14' not found (required by /usr/lib/libppl.so.7) * Handed over daily tasks to Zhenqiang. Regards Åsa

13 years, 6 months

2
2
0 0

[ACTIVITY] weekly status

by Ken Werner

Hi, OpenEmbedded: * verified that the release candidate of our 2012.03 toolchain (both source and binary) is able to build the sato and qt4e images of oe-core+meta-linaro - they are booting fine using QEMU * out sick starting from Tue :/ Regards, Ken

13 years, 6 months

1
0
0 0

[ACTIVITY] report week 11

by Peter Maydell

Current Milestones: || || Planned || Estimate || Actual || ||cp15-rework || 2012-01-06 || 2012-03-30 || || Historical Milestones: ||initial-a15-system-model || 2012-01-27 || 2012-01-27 || 2012-01-17 || ||qemu-kvm-getting-started || 2012-03-04?|| 2012-03-04?|| 2012-02-01 || == cp15-rework == * converted crn=1; still TODO: crn=0, some loose ends; then reassess the design in the light of experience doing register conversion * I've estimated another two weeks here but this might be out, because in practice much of my time is sucked up by 'other' issues == other == * tracked down cause of LP:947888 gpg crash bug: newer glibc use /proc/self/maps to decide whether a printf format string using '%n' is in writable memory, and qemu's maps emulation wasn't good enough * fixed a thumb decoder bug where we were treating 'setend' like 'cps' * investigated whether we had any conveniently testable cores which take advantage of the ARM ARM latitude for UNDEFfing even on failed condition code checks (answer, not really but the KVM code to handle this case should be small enough not to worry about its not-yet-tested nature) * qemu-linaro 2012.03 release (lots of bug fixes, plus exynos4 and highbank models thanks to Samsung and Calxeda) * code review: imx31 board patches * rebased qemu-linaro on upstream and applied some new patches from Christoffer for ARM KVM support * LP:956799: added ppoll to QEMU arm-linux-user (a one liner...) * boot-wrapper: moved initrd load address up so we can handle large kernels (like Android!) * sent pullreqs for target-arm, arm-devs patchqueues

13 years, 6 months

1
0
0 0

[ACTIVITY] Mar 15 - Mar 16

by Ulrich Weigand

== GCC == * Checked first part of fwprop-subreg patch into mainline. * Checked Ira's vectorizer patches into mainline. * Ongoing work on improving end-of-loop value computation. Mit freundlichen Gruessen / Best Regards Ulrich Weigand -- Dr. Ulrich Weigand | Phone: +49-7031/16-3727 STSM, GNU compiler and toolchain for Linux on System z and Cell/B.E. IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter | Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen | Registergericht: Amtsgericht Stuttgart, HRB 243294

13 years, 6 months

1
0
0 0

Final Building at -O3 writeup

by Michael Hope

The final version of the 'Building at -O3' writeup is at: https://wiki.linaro.org/Internal/ToolChain/BuildingAtO3 This updates the SPEC 2000 results to show that there is a net win which is held back by a bad (but understood) regression in one benchmark. Thank you all for your work on this, -- Michael

13 years, 6 months

2
1
0 0

[ANNOUNCE] Linaro QEMU 2012.03 released

by Peter Maydell

The Linaro Toolchain Working Group is pleased to announce the release of Linaro QEMU 2012.03. Linaro QEMU 2012.03 is the latest monthly release of qemu-linaro. Based off upstream (trunk) QEMU, it includes a number of ARM-focused bug fixes and enhancements. Highlights in this month's release: - we now default to enabling 'reserve memory for guest' on 64 bit hosts in linux-user-mode. This significantly reduces the chances of QEMU being unable to satisfy a guest process mmap() request. - Fix for a bug that was causing spurious failures of the glibc check for "%n in a format string must be in a read-only area of memory" when running in linux-user-mode. - QEMU's built-in boot loader now supports passing a device tree blob to the kernel: if you boot with -kernel mykernel (and optionally -initrd myinitrd) you can now also use the new command line option -dtb my.dtb to pass a device tree. - This version includes an initial implementation of a model of the Samsung Exynos4210 SoC, used by board models 'nuri' and 'smdkc210' (thanks to Evgeny Voevodin, Maksim Kozlov, Igor Mitsyanko and Dmitry Solodkiy from Samsung, who submitted this work to upstream QEMU). - This version includes an initial implementation of a model of the Calxeda Highbank SoC, used by board model 'highbank' (thanks to Rob Herring and Mark Langsdorf of Calxeda, who submitted this work to upstream QEMU). - various other minor bug fixes (detailed in the Changelog.LINARO). Known issues: - Graphics do not work for OMAP3 based models (beagle, overo) with 11.10 Linaro images. The source tarball is available at: https://launchpad.net/qemu-linaro/+milestone/2012.03 More information on Linaro QEMU is available at: https://launchpad.net/qemu-linaro

13 years, 6 months

1
0
0 0

Release done, branch is open

by Michael Hope

The GCC release tested up just fine. The branch is now open for commits. The next release is Thursday the 12th of April. Note that this is the week after Easter. -- Michael

13 years, 6 months

1
0
0 0

[ANNOUNCE] Linaro GCC 4.6 and 4.5 2012.03 released

by Michael Hope

The Linaro Toolchain Working Group is pleased to announce the 2012.03 release of both Linaro GCC 4.6 and Linaro GCC 4.5. Linaro GCC 4.6 2012.03 is the thirteenth release in the 4.6 series. Based off the latest GCC 4.6.3 release, it contains a new scheduler pressure pass, implements new instructions, and contains a number of bug fixes. Interesting changes include: * Updates to 4.6.3. * Better performance by accounting for register pressure when scheduling instructions. * Support for the ARMv6 USAT/SSAT saturation instructions. * Support for the VFP VCVT fixed to floating point conversion instruction. Fixes: * LP: #922474 Bug in __sync_lock_release with 64 bit primitives * LP: #923397 Alignment attribute has no effect under certain conditions * LP: #926855 [ARMhf] gcc produces assembler it can't compile * LP: #936863 ICE in constprop.2 (ARM NEON related?) * LP: #942307 'asm' operand requires impossible reload * LP: #952565 Not compliant with the ABI for multi-register NEON intrinsics Linaro GCC 4.5 2012.03 is the nineteenth release in the 4.5 series. Based off the latest GCC 4.5.3+svn184976 release, this is a maintenance only update. Interesting changes include: * Updates to 4.5.3+svn184976. The source tarballs are available from: https://launchpad.net/gcc-linaro/+milestone/4.6-2012.03 https://launchpad.net/gcc-linaro/+milestone/4.5-2012.03 Downloads are available from the Linaro GCC page on Launchpad: https://launchpad.net/gcc-linaro More information on the features and issues are available from the release page: https://launchpad.net/gcc-linaro/4.6/4.6-2012.03 Mailing list: http://lists.linaro.org/mailman/listinfo/linaro-toolchain Bugs: https://bugs.launchpad.net/gcc-linaro/ Questions? https://ask.linaro.org/ Interested in commercial support? Inquire at support(a)linaro.org -- Michael

13 years, 6 months

1
0
0 0

EEMBC AndEBench

by Michael Hope

EEMBC have announced AndEBench, a mixed native/Java benchmark for Android. It's available on the Market. I don't know much more. It seems to be CPU bound and the test names sound a bit like CoreMark. The source is available for license and might be worth the Android guys looking into. The awesome thing is they used the 2012.01 Linaro Binary toolchain release to build the native parts - see the compiler version string in the log :) -- Michael

13 years, 6 months

1
0
0 0

[ACTIVITY] May 5 - May 9

by Thiago Jung Bauermann

Hi, GDB for Android: * Wrote first draft of the GDB for Android card. * Found out that there actually is a libthread_db.so in /system/lib and was able to compile (after a small hack) an FSF gdbserver 7.3 which uses the libthread_db.so from Android and correctly shows all threads in the process. So the libthread_db.so from Android actually works, still have to learn why they don't use it. * Tried to compile a native GDB which uses libthread_db.so but no luck so far. There are many differences in bionic's header files which upset libiberty and gnulib which are not easy to work around. -- []'s Thiago Jung Bauermann Linaro Toolchain Working Group

13 years, 6 months

1
0
0 0

SPEC shifted to ref runs

by Michael Hope

We now do a SPEC ref run when benchmarking. I've updated the linaro-toolchain-benchmarks scripts to handle the changes and spawned some historical builds to do comparisons. All earlier builds have been archived to prevent confusion. The human readable summary is now also included in the results. See: http://ex.seabright.co.nz/benchmarks/gcc-linaro-4.6-2012.02/logs/armv7l-nat… for an example. Half an hour to build, 26 hours to run. Not too bad. -- Michael

13 years, 6 months

1
0
0 0

Running benchmark variants

by Michael Hope

Here's brief notes on running different benchmark variants across the auto builders. Asa, could you pull these plus your notes into a wiki page? Spawn a job: http://ex.seabright.co.nz/helpers/scheduler/spawn Merge requests are automatically built. Otherwise, drop arbitrary tarballs into cbuild@orion:~/snapshots and spawn <tarball name minus extension>. For example, scp gcc-4.6.3.tar.gz cbuild@orion:~/snapshots; spawn gcc-4.6.3 into a9-builder. Jobs: * gcc-version - build and test GCC * benchmarks-gcc-version - run coremark, denbench, eembc against the already built version * benchmarks-spec2000-gcc-version - run spec2000 Queues: * a9-builders: anything that can naive build a A9 compiler * a9-ref: reference A9 boards * a8-ref: reference A8 boards Variables: * BENCHMARKS = list, such as coremark spec2000 pybench - run these benchmarks instead of the defaults Variants: * By default we build o3-neon * See http://bazaar.launchpad.net/~linaro-toolchain-dev/cbuild/trunk/view/head:/l… for all names * Spawn a job with VARIANT_SRC = all and VARIANT_LIST = glob-pattern Examples: * VARIANT_LIST = o3-neon o3-vfpv3 (compare NEON with VFPv3D32) * VARIANT_LIST = o3-neon-cortexa8 o3-neon-cortexa9 (compare -mtune=cortexa8 vs -mtune=cortexa9( * VARIANT_LIST = o3-neon-novect o3-neon (compare with/without the vectoriser) -- Michael

13 years, 6 months

2
2
0 0

Change in Linaro Toolchain announcements

by Michael Hope

I'd like to announce a change in how the Linaro Toolchain group notify about our monthly releases. In the past we've sent one email per product to the linaro-announce list. From this week forward a summary of all products will be included in the main, end of month announcement instead. We'll continue to send a per product emails to the linaro-toolchain list when the mid-month release is available. If you'd like to get things two weeks early, please subscribe[1]. You can filter on the word '[ANNOUNCE]' to filter out the development chatter. A RSS feed is also available[2]. -- Michael [1] http://lists.linaro.org/mailman/listinfo/linaro-toolchain [2] http://feeds.launchpad.net/linaro-toolchain/announcements.atom

13 years, 6 months

1
0
0 0

Bare metal toolchain for A15

by William Mills

All, I need to supply a Linaro toolchain "aligned" (same source code) bare-metal compiler to a group doing benchmarking on A15. First off my assumption is that we will write our own boot and semi hosting code. (semi-hosting for TI emulators/simulators is different than ARM RDI semi-hosting.) I was planning on looking at the two toolchains here[1] and here [2]: [1] https://launchpad.net/linaro-toolchain-binaries [2] https://launchpad.net/gcc-arm-embedded I was then going to build a hybrid that was newlib based but appropriate for armv7-a (instead of cortext-m3) and maybe even -mtune'ed for A15. However looking at the gcc-arm-embedded release more[3] I see that it supports ARMv7-R. It supports both thumb and non-thumb modes, both softfp and hardfp ABIs. What would I really gain by building my own? For app code the user should be able to add -mtune=cortex-a15 and still be compatible with the pre-built R4/R5 libraries. The only performance difference should be in the library code and that should be only pipeline tuning if I understand the difference between armv7-a and armv7-r correctly. Am I missing something? Should I build my hybrid anyway? [1] https://launchpadlibrarian.net/88152755/readme.txt [BTW: has the below project been obsoleted by the gcc-arm-embedded one? Perhaps gcc-arm-embedded should be referenced in the description of the page below. https://launchpad.net/linaro-toolchain-unsupported ] Thanks, Bill

13 years, 6 months

4
9
0 0

[ACTIVITY] 5th - 9th March

by Andrew Stubbs

Committed the 4.6.3 merge to Linaro GCC 4.6. Merged from FSF 4.5 to Linaro GCC 4.5. Thought about how to do register-class allocation for NEON v. core registers case. Discussed the problem at the GCC performance meeting. Lots of interesting discussion was had. I have some interesting experiments to do, but the first step needs to be to get my 64-bit operator patch to work correctly. Tried to track down the problems in my NEON-immediates patch. The problem is that it's putting constants in different pools in stage 3 to what it does in stage 2. Presumably this is something to do with the pool-offset attributes in the instruction patterns? My patch has caused it to switch from using 'fldd' to using 'vmov' in some cases (the instructions are aliases, but it's indicative of a different machine description pattern in the compiler), but I don't know why the change would be different between the different bootstrap stages? I made some alterations to switch it back to `fldd` when it wasn't supposed to change, but bootstrap still fails. More investigation required...again. Rewrote the NEON one's-complement patch and posted it upstream. Tracked down the cause of the bootstrap failures in my NEON 64-bit shifts patch: out-of-range shift amounts were not handled leading to ICEs. Reworked the constant shift handling cases, and resumbitted the patch for testing. It's failed again. A job for next week.

13 years, 6 months

1
0
0 0

[Activity] Week 10

by Zhenqiang Chen

Summary: * Multilib test for linaro toolchain. * Code size test for embedded toolchain. Details: 1. Multilib test for linaro toolchain. * Workaround the marm/march=armv5t build by setting the MULTILIB_DEFAULT to mthumb. * Investigate how to make multiarch and multilib work together. Based on current multiarch/multilib patches, it is hard to make them work together. Trying to set the default multilib dir to the multiarch dir to workaround it. Need more work to build libgcc. 2. Code size investigation for embedded toolchain. * Try to test benchmarks. * Run gcc regression test with –mthumb/-mcpu=cortex=m3/-Os and analyze the new failed cases. After skipping the cases based on scan-assembler, warning/error message, etc, there are 5 new failed cases in three categories: (1) gcc.target/arm/neon/vst1_lanes64.c: known issue http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51631 (2) Wrong optimization for gcc.dg/atomic-lockfree.c, gcc.dg/atomic-noinline.c and gcc.dg/pr30951.c. (3) g++.dg/eh/filter1.C abort in libsupc++. Plans: * Root cause the new failed cases. * Continue to investigate the multilib/multiarch issue. Best regards! -Zhenqiang

13 years, 6 months

1
0
0 0

Draft release notes for 2012.03

by Michael Hope

I've put the draft release notes at: https://wiki.linaro.org/MichaelHope/Sandbox/GCC2012.03ReleaseNotes Feel free to edit. -- Michael

13 years, 6 months

1
0
0 0

Spec2000

by Andrew Stubbs

Hi Michael, Spec2000 is now running successfully: there are results at http://ex.seabright.co.nz/benchmarks/gcc-linaro-4.7%2bbzr114965/logs/armv7l… However, they seem to have been run in 'train' mode, and none of the runs are long enough for comparison. I thought the a9-ref queue was supposed to run in full 'ref' mode? Andrew

13 years, 6 months

2
1
0 0

[ACTIVITY] weekly status

by Ken Werner

Hi, OpenEmbedded: * removed the recipe for building the linux-linaro-3.1 kernel * add support for the default OE-core kernel * allows to build the linux-yocto_3.2 kernel for the qemuarmv7a MACHINE using a vexpress defconfig * updated the wiki on how to build OE-core with meta-linaro https://wiki.linaro.org/KenWerner/Sandbox/OpenEmbedded-Core * worked OEMetaLinaroCard * started to talk to CI folks about automating the oe-core+meta-linaro * wrote a script that automates the process * ran it on tcserver01 to build the qt4e and sato images against the source gcc-linaro-4.6-2012.02 Regards, Ken

13 years, 6 months

1
0
0 0

OpenEmbbedded as a test suite next steps

by Michael Hope

Hi Ken. In follow up to our 1-on-1 yesterday, here's what I'd like done next. The goal is to use OE Core as a release test suite. The releases are tarballs so we can keep the current recipe format and punt bzr support for later. The first step is to be able to reliably build a release in the cloud or validation lab. In all cases keep the other teams in mind. Much of this is related to Validation. Platform will be involved later. Ping them early. Kernel: We're starting with GCC and need a kernel to supply headers and to boot some type of ARMv7 image. I don't want a linux-linaro recipe as people will use it and it's too early for that. Find a kernel, preferably from OE Core, that is recent, ARMv7, >= 512 MB RAM, and works well with qemu-linaro. Prefer vexpress-a9, else OMAP? Talking: Say Hi to Validation re: EC2 and plans Say Hi to the ARM landing team re: vexpress upstream support Say Hi to Beth Flanagan re: Yocto's existing auto builders and any hints Cloud builds: Find out who is already doing OE builds in the cloud and how Run a build locally and time Push ~/downloads into the cloud, build, and time[1] Figure how much this build will cost in dollars [1] c1.xlarge might be best. Builds are normally I/O bound and the cloud is I/O poor. Put /tmp and other chunks in a tmpfs? EC2 rounds up to the nearest hour as well. If the cloud is too expensive then we'll get a machine installed. S3 for storage: (only proceed if affordable) Use S3 for storing the input tarballs Use S3 either as a pre-mirror by serving over HTTP, or use s3cmd to sync down the tarballs before starting the build Scripting: Re-use existing scripts if feasible. Integrate with LAVA providing we can run exactly the same scripts on a laptop for debugging. Script the bitbake, OE meta layer, and Linaro meta layer setup. Script the configuration including setting the release tarball URL and GCC preferred version. Script the build and result capture, especially the log, any ICEs, and the final sizes Future: OE can grab a repository seed then update based on that. Check if the bzr backend supports this. If so, play with seeding to do tip builds. Let me know what you think then we'll spawn blueprints. Let's keep an eye on this as it's sounding expensive. -- Michael

13 years, 6 months

6
9
0 0

Cards

by Michael Hope

Hi Ken, Thiago. Could you try your hand at writing cards for the OpenEmbedded Core meta-layer and GDB and Android? Here are some past cards: https://linaro-public.papyrs.com/TCWG2011-GCC-O3 https://linaro-public.papyrs.com/TCWG2011-OPENOCD-SUPPORT https://linaro-public.papyrs.com/TCWG2011-WINDOWS-TOOLCHAIN They cover: * An introduction * The why/advantages * The what/features * The how/steps * Dependencies * Acceptance criteria (which is a post-tense version of the body) A card should cover three calendar months. Check the unknowns - we need to investigate the acceptance criteria and make sure there is no unexpected side work in there. We use roadmap cards as the highest level of organising our work. Cards are the interface between working groups and the TSC and sit at the project brief / deep but concise level. Draft them on the wiki (cf https://wiki.linaro.org/KenWerner/Sandbox) and we'll go from there. -- Michael

13 years, 6 months

3
6
0 0

[Activity] Week 10

by Ramana Radhakrishnan

== Issues == It would be nice to have perf installed on the porter boxes in the canonical data center as well if we are allowed to run benchmarks there. Filed RT request. ==Progress=== * Understood STB_GNU_UNIQUE_NOTE - Helped fix a problem with compiz crashing but then it was a very nice testcase to investigate the toolchain issue with. Thanks Alexandros. * Merged pending patches. * ABI fix * Fix for ICE - LP bug 942307 * Off sick on Monday. * Did some work to improve code generation for addressing modes in VFP registers. * Did some work in setting up SPEC2k for running hc partitioning patches. Still needs to be completed. === Plans === * Ping configure.ac changes. * Complete pending benchmark run with hc partitioning and look at results with hc partitioning and run things. Was unable to run the vfp benchmarks today as ex.seabright.co.nz was down. * Resurrect partial-partial PRE Absences. * 1 week holiday sometime before that - to be booked. * Linaro Connect Q2.12 - May 28 - June 1 - travel booked - hotel to be booked.

13 years, 6 months

1
0
0 0

Using OpenEmbedded Core to check this month's release

by Michael Hope

Hi Ken. This month's release is next week. Let's be aggressive and see if we can use your meta-linaro layer to check the source release. I want to use tcserver01 in the validation lab instead of the cloud until we know how much it costs. I've added you an account and done a test build to check that the dependencies are there. There's a shared directory in /home/shared that includes downloads and a sstate-cache. The machine seems fast enough for the job. The tarball should be ready around Tuesday next week. Once ready, could you mix it in with the meta-linaro layer, do a build, boot the rootfs in qemu, and document as you go? Anything past that is welcome. It's all manual but a nice proof of concept. Can we check the binary build as well? -- Michael

13 years, 6 months

2
1
0 0

[ACTIVITY] report week 10

by Peter Maydell

Current Milestones: || || Planned || Estimate || Actual || ||cp15-rework || 2012-01-06 || 2012-??-?? || || (new blueprints & reestimate for this one pending still; will try to do this early next week) Historical Milestones: ||a15-usermode-support || 2011-11-10 || 2011-11-10 || 2011-10-27 || ||upstream-omap3-cleanup || 2011-11-10 || 2011-12-15 || 2011-12-12 || ||initial-a15-system-model || 2012-01-27 || 2012-01-27 || 2012-01-17 || ||qemu-kvm-getting-started || 2012-03-04?|| 2012-03-04?|| 2012-02-01 || == cp15-rework == * converted cp15 crn={6,7,9}, still TODO just crn={0,1}. These take longer than I was expecting because to find some useful compromise between QEMU's previous (usually broken) behaviour and reality I have to cross reference half a dozen different TRMs and several revisions of the ARM ARM. == other == * getting qemu-linaro into shape for next week's release: applying patches, writing changelog, etc * patch review for more exynos4 devices * tracked down a regression in the spitz (zaurus) model, sent patch * first pass comments on blueprints for this quarter * investigating LP:947888 (gpg crashes under qemu) -- PMM

13 years, 6 months

1
0
0 0

Re: Problem running updated compiz branches on ARM

by Andrew Stubbs

Hi Alexandros, Could you use the linaro-toolchain list for stuff like this please? You're more likely to find somebody who knows the answer that way. I'm pretty sure the problem is not the compiler because, as far as I can see, both architectures' compilers emit ".weak" directives. If there is a problem, I'd say it's in the linker. Your test case gives two different addresses on Lucid x86, and on ARM (so you say, I've not tested it), but the same address twice on Precise. This is a surprising result. *I* would have expected that static values in different dlopen'd libraries would not be unified, but apparently they are ... somtimes. I'm afraid I don't really have any insight here. :( Anyway, regardless of whether one is correct, or not, I'd suggest *not* relying on this behaviour - it's clearly not portable. I say leave it at arm's length in production software for a few years. Andrew On 06/03/12 14:27, Alexandros Frantzis wrote: > On Tue, Mar 06, 2012 at 09:51:01AM +0800, Sam Spilsbury wrote: >> On Mon, Mar 5, 2012 at 11:50 PM, Alexandros Frantzis >> <alexandros.frantzis(a)linaro.org> wrote: >>> Hi all, >>> >>> this is an update on my progress with the updated compiz branches. >>> >>> I have been trying to run our update compiz branches >>> (compiz-*/linaro-gles2-update) on ARM (precise armhf), but I have stumbled onto >>> the same issue Marc reported some days ago. In particular, I get: >>> >>> /usr/bin/compiz (core) - Fatal: Private index value "15CompositeWindow_index_4" already stored in screen. >>> /usr/bin/compiz (core) - Fatal: Private index value "15CompositeScreen_index_4" already stored in screen. >>> >>> and then a segfault when I try to run compiz. >>> >>> Note that I *don't* have this problem when running on x86_64 precise. >>> >>> The issue can be recreated with: >>> >>> $ compiz composite opengl >>> >>> I added some debugging messages to pluginclasshandler.h to get a better >>> feeling of what is going on, and ran on both my desktop and on ARM. >>> This is the output near the point when GLScreen get initialized: >>> >>> ... >>> >>> compiz (core) - Info: get(): mIndex.initiated for "8GLScreen_index_4" : 0 >>> compiz (core) - Info: initializeIndex(): Initializining index value "8GLScreen_index_4" >>> compiz (core) - Info: initializeIndex(): Private index value added for "8GLScreen_index_4" >>> compiz (core) - Info: getInstance(): Get instance for "8GLScreen_index_4" >>> compiz (core) - Info: getInstance(): Spawning new class for "8GLScreen_index_4" >>> compiz (core) - Info: ctor(): mIndex.initiated for "8GLScreen_index_4" : 1 >>> compiz (core) - Info: ctor(): Increasing reference count for "8GLScreen_index_4": 1 >>> >>> --- x86_64 --- >>> compiz (core) - Info: get(): mIndex.initiated for "15CompositeScreen_index_4" : 1 >>> --- armhf --- >>> compiz (core) - Info: get(): mIndex.initiated for "15CompositeScreen_index_4" : 0 >>> compiz (core) - Info: initializeIndex(): Initializining index value "15CompositeScreen_index_4" >>> compiz (core) - Fatal: initializeIndex(): Private index value "15CompositeScreen_index_4" already stored in screen. >> >> After the composite plugin loads and mIndex.initiated is set to 1, >> place a watchpoint on mIndex.initiated (it should be a separate >> template instantiation for each different class) and check if it >> changes, or check if we are reading mIndex.initiated from a different >> address, and if so, check the addresses of this for each constructor >> and destructor being called. (could be a compiler bug, I've hit these >> on this part of the code before). >> >>> ------------- >>> >>> In the armhf case, CompositeScreen is erroneously considered not >>> initialized, and is initialiazed again, therefore messing up the plugin system. >>> >>> I am trying to figure out if this is a manifestation of some kind of memory >>> corruption that doesn't affect us on x86_64 for whatever reason (alignment, >>> integer size etc), or something completely different. >>> >>> Thoughts? >>> >>> Thanks, >>> Alexandros >> >> >> >> -- >> Sam Spilsbury >> > > Hi all, > > (I have also added Michael, Andrew and Ulrich from the Linaro toolchain group > to the recipients. Hi!) > > Checking the addresses, as Sam suggested, I found that there are two different > PluginClassHandler<CompositeScreen, CompScreen, 4>::mIndex and > PluginClassHandler<CompositeWindow, CompWindow, 4>::mIndex objects. > > After a bit of investigation, objdump gave an explanation: > > objdump -t /usr/lib/compiz/libcomposite.so | c++filt | grep mIndex > > -- x86_64 -- > 0000000000277a80 u O .bss 0000000000000010 PluginClassHandler<CompositeWindow, CompWindow, 4>::mIndex > 0000000000277a70 u O .bss 0000000000000010 PluginClassHandler<CompositeScreen, CompScreen, 4>::mIndex > -- armhf -- > 00065648 w O .bss 00000010 PluginClassHandler<CompositeWindow, CompWindow, 4>::mIndex > 00065658 w O .bss 00000010 PluginClassHandler<CompositeScreen, CompScreen, 4>::mIndex > ------------ > > And the same kind of output for libopengl.so > > On x86_64 the symbols are marked 'u': 'unique global', whereas on armhf > they are marked 'w': 'weak'. This seems to be causing our troubles. > > I have produced a small test case for this: > > http://people.linaro.org/~afrantzis/cpp_unique_global.tar.gz > > Building and running 'LD_LIBRARY_PATH=. ./main' on x86_64 prints out f1 and f2 > with the same address, whereas on armhf the addresses are different (i.e. two > different objects). On x86_64 the symbol A<int>::a is 'u', on armhf it is 'w'. > > For completeness, when running without templates (edit a.h to change) the two > printed addresses are different on both x86_64 and armhf. Also A::a is 'g': > 'normal global' for both. > > Michael, Andrew, Ulrich can you please give us some insight into the situation? > Does this seem like a compiler or linker bug on ARM, or is the code depending > on undefined behavior, or something different? I have pasted the used g++ > versions at the end of the email. > > Thanks, > Alexandros > > --- g++ x86_64 -- > Using built-in specs. > COLLECT_GCC=g++ > COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.6/lto-wrapper > Target: x86_64-linux-gnu > Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.6.3-1ubuntu2' --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++,go --prefix=/usr --program-suffix=-4.6 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-plugin --enable-objc-gc --disable-werror --with-arch-32=i686 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu > Thread model: posix > gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu2) > > --- g++ armhf -- > Using built-in specs. > COLLECT_GCC=g++ > COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/4.6/lto-wrapper > Target: arm-linux-gnueabihf > Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.6.3-1ubuntu2' --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.6 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-plugin --enable-objc-gc --enable-multilib --disable-sjlj-exceptions --with-arch=armv7-a --with-float=hard --with-fpu=vfpv3-d16 --with-mode=thumb --disable-werror --enable-checking=release --build=arm-linux-gnueabihf --host=arm-linux-gnueabihf --target=arm-linux-gnueabihf > Thread model: posix > gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu2) >

13 years, 6 months

5
6
0 0

Fwd: [ACTIVITY] w10

by Asa Sandahl

Hi! * Bug reports Made an effort clean up among the remaining not-triaged bug. Michael will help out with 941676, where the failure is on power-pc. * Wiki Created a wiki page for running benchmarks in cbuild: https://wiki.linaro.org/WorkingGroups/ToolChain/Benchmarks/RunningBenchmark… * V8 Build system has changed in V8 from SCones to GYP. With GYP I can pass the normal flags like CXXFLAGS to control the build, so this looks like a good change. I have created a cbuild make file, patterned after the other benchmark make files. Working on x86 sofar, will go for arm next week. Will also add a parser for the results. Regards Åsa

13 years, 6 months

1
0
0 0

[ACTIVITY] Mar 5 - Mar 8

by Ulrich Weigand

== GCC == * Checked patch to generate usat/ssat instructions into Linaro GCC 4.6 and 4.7. * Submitted (first part of) fwprop-subreg patch for mainline. * Submitted Ira's vectorizer patches for mainline. * Ongoing work on improving end-of-loop value computation. * Patch review week. == Misc == * On leave 3/9 - 3/14. Mit freundlichen Gruessen / Best Regards Ulrich Weigand -- Dr. Ulrich Weigand | Phone: +49-7031/16-3727 STSM, GNU compiler and toolchain for Linux on System z and Cell/B.E. IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter | Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen | Registergericht: Amtsgericht Stuttgart, HRB 243294

13 years, 6 months

1
0
0 0

Updates sysroots for binary toolchain

by Marcin Juszkiewicz

Hi Updated sysroots for binary toolchain are available at [1]. This time I split -dev and -dbg sysroots so as long as dbgsym are not needed less disk space is used. Please take a look at them and report any issues. 1. http://people.linaro.org/~hrw/generic-linux/sysroots/20120301/

13 years, 6 months

3
8
0 0

Linaro toolchain and ARMv6

by ezjd

Hello, My name is Jiandong Zheng and am working on a few ARM specific projects. I have been using Linaro toolchain coming with Ubuntu to do Cortext-A9 building. I also need to maintain code for old ARM11 SoC so that Linaro toolchain is my preference and it did the job well back in Maverick days if I remember correctly. However, in Precise, I have troubles running this ARM11 u-boot and kernel built with Linaro toolchain, eventually I found that my old gcc 4.3.2 toolchain can still build workable u-boot and kernel so that Linaro toolchain (gcc 4.6.2) seems the problem. I understand that Linaro's focus has been ARMv7 or above but I am wondering if its toolchain can still be used for older ARM architectures. Thanks, JD

13 years, 6 months

4
4
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain