User account creation filtered due to spam.
[ Forwarded from http://bugs.debian.org/487406 ]
Enrico Zini reported the following bug (with testcase) to Debian: the attached
code compiled with -fPIC results in a segfault on ARM (old ABI; not on EABI).
It works fine on other architectures or on ARM with gcc 4.2.
I verified that the bug is present in gcc 4.3 from SVN and in trunk.
Created attachment 16991 [details]
only arm-eabi is in the list of primary/secondary targets.
GCC 4.3.3 is being released, adjusting target milestone.
Does this still occur on trunk ?
The bug occurs on OABI with gcc-4.3-20090705 but not with gcc-4.4-20090707.
This was fixed for 4.4 by revision 133117, which did a fair amount of stack frame management changes. Applying that change to 4.3-20090712 fixes this test case also for 4.3.
I'm not in a position to do a full regression test of an OABI toolchain, but I may have time to test that it doesn't cause regressions for EABI.
GCC 4.3.4 is being released, adjusting target milestone.
GCC 4.3.5 is being released, adjusting target milestone.
4.3 branch is being closed, moving to 4.4.7 target.
4.4 branch is being closed, moving to 4.5.4 target.
Old ABI is no longer supported