linaro-toolchain April 2011

linaro-toolchain@lists.linaro.org

29 participants
73 discussions

by Ramana Radhakrishnan

== GCC == Progress: * Spent some time digging into binutils issue for Neon but still not sure why I see the problem when this is fixed in 2.21 branch and no one else see this. * Fixed PR 48090 upstream. * Some patch review. * T2 performance meeting. Plans when I'm back: * Continue looking at divmodsi4 improvements. * Continue looking at excessive VFP moves. * Backport the fix for the initialization of cgraph into FSF 4.5 branch. Meetings: * 1-1s * Linaro toolchain meeting * T2 performance. * Linaro@UDS meeting. Absences: * April 15 – 26 -> Booked. * May 9-14 - LDS Budapest

13 years, 6 months

Issue with noreturn static function with unused arg

by Loïc Minier

hey This problem with busybox: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621137 seems to be a toolchain issue. It occurs with FSF GCC 4.5.2 but not 4.6, and it doesn't occur with Linaro GCC 4.5 but it does with Debian gcc-4.5. I'm trying to identify the fix which Linaro applied to solve this! :-) Michael Hope told me he remembers we fixed something similar for Qt, but he couldn't find the patch and suggested I post here to get feedback. I've pushed ash.i and .s at: http://people.linaro.org/~lool/ash.i which you can build with: gcc -save-temps -std=gnu99 -Wall -Wshadow -Wwrite-strings -Wundef -Wstrict-prototypes -Wunused -Wunused-parameter -Wunused-function -Wunused-value -Wmissing-prototypes -Wmissing-declarations -Wdeclaration-after-statement -Wold-style-definition -fno-builtin-strlen -finline-limit=0 -fomit-frame-pointer -ffunction-sections -fdata-sections -fno-guess-branch-probability -funsigned-char -static-libgcc -falign-functions=1 -falign-jumps=1 -falign-labels=1 -falign-loops=1 -g -Os -c -o ash2.o ash.i the interesting part is that ash.s has tryexec as not returning, when it does return: grep ^tryexec ash.s -A5 | grep return this seems to be due to the combination of tryexec being static, its parent being noreturn, and one argument of tryexec being unused. Any idea of which Linaro patch solved this? :-) Does it make sense to raise this to FSF GCC 4.5? Thanks! -- Loïc Minier

13 years, 6 months

First toolchain estimate for the next cycle

by Michael Hope

Hi there. Mounir and I have been looking at the work for next cycle. A summary spreadsheet with notes is available here: https://spreadsheets0.google.com/ccc?key=ty1c-H56f0GxnL1Hk9LCmRg I'm very interested in feedback, especially on the time estimates and extra topics we should suggest to the TSC. See the notes at the top and feel free to add items or estimates straight into the sheet - anyone can view and anyone at Linaro should be able to edit. -- Michael

13 years, 6 months

Differences in build hosts

by Michael Hope

Hi there. I ran a build of gcc-linaro-4.5+bzr99491 on ursa1 through 4 to see if there was any difference in build machines. The following tests had different results: * gcc.c-torture/compile/limits-structnest.c * gcc.dg/graphite/block-4.c * largefile.c * obj-c++.dg/template-5.mm * obj-c++.dg/template-5.mm * obj-c++.dg/template-6.mm * obj-c++.dg/template-6.mm * objc/execute/class-4.m I suspect that they're all caused by running the testsuite in parallel and the host running out of memory. limits-structnest takes around 850 MB of RAM and passes on the machine with swap (ursa1) and fails on the others. block-4.c takes 2:35 to run and timed out on ursa1 and passed on the others which may be due to ursa1 swapping heavily while running a limit test in parallel. The obj-c tests show various forms of killed, and suggest that they were killed due to another process taking all the memory. I'll change the machines to use the full 1 G of memory, run the test suite in sequential mode, and see how things go. I haven't investigated largefile.c - it's a PCH test and these fail randomly. Regarding block-4.c, it takes 155 s to run which is too close to the default 300 s for my taste. Should we add a dg-timeout-factor 4.0 to it similar to block-3.c? -- Michael

13 years, 6 months

[Activity] April 4th - 8th

by Ramana Radhakrishnan

Missed sending this out earlier this week. == GCC == Progress: * Sync'd with Andrew about T2 performance stuff. * Spent some time investigating what could be done for divmodsi4 improvements . Working through the various phases. Not done tree level stuff for a while so my knowledge of the API is a a bit rusty. * Some upstream bugzilla duty. Plans: * Continue looking at divmodsi4 improvements. * Continue looking at excessive VFP moves. * Look at binutils + neon issue. * Performance kick-off meeting Meetings: * 1-1s * Linaro toolchain meeting * Andrew Stubbs meeting for 1 hour about T2 performance. Absences: * April 13th - Internal ARM conference. Not at desk all day. * April 15 – 26 -> Booked. * May 9-14 - LDS Budapest

13 years, 6 months

[ACTIVITY] weekly status

by Ken Werner

Hi, libunwind: * started to look on how to resume from a given stack frame: * other platforms use setcontext * setcontext is not implemented on ARM (glibc) * the *context functions have been marked obsolescent in Posix * http://pubs.opengroup.org/onlinepubs/009695399/functions/makecontext.html pandaboard: * gdb doesn't find separate debug info of libraries that have been put into a multiarch directory (#758619) Note: I'll be out of office to attend a class till (including) Friday. Regards Ken

13 years, 6 months

Today's T2 perf call.

by Ramana Radhakrishnan

A rough agenda for today's call. I'll put this on the wiki after the call. 1. Go over what we are all doing today - roughly Areas of investigation that we are looking at for near term. a. divmodsi4 work. b. Unnecessary VFP to integer register moves because of addressing modes availability. c. Thumb2 constants work d. Additional areas for headroom in DENBENCH. e. Coremark regressions fix up f. Revisions causing major regressions in coremark 2. Find a way of replicating the benchmarking results and make sure we get similar results to Michael and we are doing roughly the same thing. 3. Regular bi-weekly call following the Toolchain WG meeting ? Or do we organize another call ?

13 years, 6 months

[Bug 758082] [NEW] [armel] segfaults in make check pass when built with optimization

by Jani Monoses

Public bug reported: FTBFS on armel https://launchpadlibrarian.net/68239668/buildlog_ubuntu-natty-armel.augeas_… not apparent from the log but the failing of test-interpreter.sh is due to a core dump. Starting program: /home/jani/work/ftbfs/aug/augeas-0.8.0/src/.libs/lt- augparse --nostdinc -I . fail_let_no_exp.aug Program received signal SIGSEGV, Segmentation fault. strlen () at ../ports/sysdeps/arm/strlen.S:29 29 ../ports/sysdeps/arm/strlen.S: No such file or directory. in ../ports/sysdeps/arm/strlen.S (gdb) bt #0 strlen () at ../ports/sysdeps/arm/strlen.S:29 #1 0x4016c050 in _IO_vfprintf_internal (s=<value optimized out>, format=<value optimized out>, ap=<value optimized out>) at vfprintf.c:1620 #2 0x401d7b66 in __vasprintf_chk (result_ptr=0xbee5097c, flags=1, format=0x400d961c "%s", args=...) at vasprintf_chk.c:68 #3 0x400bfad6 in vasprintf (info=<value optimized out>, code=<value optimized out>, format=0x400d961c "%s", ap=...) at /usr/include/bits/stdio2.h:199 #4 format_error (info=<value optimized out>, code=<value optimized out>, format=0x400d961c "%s", ap=...) at syntax.c:96 #5 0x400bfd98 in syntax_error (info=0x1, format=0x400d961c "%s") at syntax.c:124 #6 0x400c3e96 in augl_error (locp=<value optimized out>, term=<value optimized out>, scanner=<value optimized out>, s=0x400d7abc "syntax error") at parser.y:628 #7 0x400c54f8 in augl_parse_file (aug=0x1ef1878, name=<value optimized out>, term=0xbee50a64) at parser.y:362 #8 0x400c153a in load_module_file (aug=0x1ef1878, filename=0xbee50ddb "fail_let_no_exp.aug") at syntax.c:1951 #9 0x400bbf0a in __aug_load_module_file (aug=0x1ef1878, filename=0xbee50ddb "fail_let_no_exp.aug") at augeas.c:1447 #10 0x00008b04 in main (argc=<value optimized out>, argv=0xbee50c84) at augparse.c:131 ** Affects: gcc-linaro Importance: Undecided Status: New ** Affects: augeas (Ubuntu) Importance: Undecided Status: New ** Tags: arm-porting-queue ** Also affects: gcc-linaro Importance: Undecided Status: New ** Summary changed: - segfaults in make check pass when built with optimization + [armel] segfaults in make check pass when built with optimization ** Tags added: arm-porting-queue -- You received this bug notification because you are a member of Linaro Toolchain Developers, which is subscribed to Linaro GCC. https://bugs.launchpad.net/bugs/758082 Title: [armel] segfaults in make check pass when built with optimization Status in Linaro GCC: New Status in “augeas” package in Ubuntu: New Bug description: FTBFS on armel https://launchpadlibrarian.net/68239668/buildlog_ubuntu-natty-armel.augeas_… not apparent from the log but the failing of test-interpreter.sh is due to a core dump. Starting program: /home/jani/work/ftbfs/aug/augeas-0.8.0/src/.libs/lt- augparse --nostdinc -I . fail_let_no_exp.aug Program received signal SIGSEGV, Segmentation fault. strlen () at ../ports/sysdeps/arm/strlen.S:29 29 ../ports/sysdeps/arm/strlen.S: No such file or directory. in ../ports/sysdeps/arm/strlen.S (gdb) bt #0 strlen () at ../ports/sysdeps/arm/strlen.S:29 #1 0x4016c050 in _IO_vfprintf_internal (s=<value optimized out>, format=<value optimized out>, ap=<value optimized out>) at vfprintf.c:1620 #2 0x401d7b66 in __vasprintf_chk (result_ptr=0xbee5097c, flags=1, format=0x400d961c "%s", args=...) at vasprintf_chk.c:68 #3 0x400bfad6 in vasprintf (info=<value optimized out>, code=<value optimized out>, format=0x400d961c "%s", ap=...) at /usr/include/bits/stdio2.h:199 #4 format_error (info=<value optimized out>, code=<value optimized out>, format=0x400d961c "%s", ap=...) at syntax.c:96 #5 0x400bfd98 in syntax_error (info=0x1, format=0x400d961c "%s") at syntax.c:124 #6 0x400c3e96 in augl_error (locp=<value optimized out>, term=<value optimized out>, scanner=<value optimized out>, s=0x400d7abc "syntax error") at parser.y:628 #7 0x400c54f8 in augl_parse_file (aug=0x1ef1878, name=<value optimized out>, term=0xbee50a64) at parser.y:362 #8 0x400c153a in load_module_file (aug=0x1ef1878, filename=0xbee50ddb "fail_let_no_exp.aug") at syntax.c:1951 #9 0x400bbf0a in __aug_load_module_file (aug=0x1ef1878, filename=0xbee50ddb "fail_let_no_exp.aug") at augeas.c:1447 #10 0x00008b04 in main (argc=<value optimized out>, argv=0xbee50c84) at augparse.c:131

13 years, 6 months

Conference code for today's Thumb-2 kick off call

by Michael Hope

Hi everyone. The conference code for today's call is 5238686884. The dial in numbers are the same as the weekly meeting. See: http://wiki.linaro.org/WorkingGroups/ToolChain/Meetings -- Michael

13 years, 6 months

[Bug 757427] [NEW] gconftool-2 segfaults on arm

by Jani Monoses

Public bug reported: The 2.32.2 upload of gconf is likely miscompiled and segfaults. This leads to other armel FTBFSs in the archive when calling gconftool-2 as part of the install phase. ** Affects: gcc-linaro Importance: Undecided Status: New ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: arm-porting-queue ** Package changed: ubuntu => gconf (Ubuntu) ** Also affects: gcc-linaro Importance: Undecided Status: New -- You received this bug notification because you are a member of Linaro Toolchain Developers, which is subscribed to Linaro GCC. https://bugs.launchpad.net/bugs/757427 Title: gconftool-2 segfaults on arm Status in Linaro GCC: New Status in “gconf” package in Ubuntu: New Bug description: The 2.32.2 upload of gconf is likely miscompiled and segfaults. This leads to other armel FTBFSs in the archive when calling gconftool-2 as part of the install phase.

13 years, 6 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain April 2011