https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66754
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marxin at gcc dot gnu.org
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Hello.
Correct command line:
gcc builtin-apply2.c -m32 -mregparm=3
BT:
Program received signal SIGABRT, Aborted.
0xf7fd8d40 in __kernel_vsyscall ()
(gdb) bt
#0 0xf7fd8d40 in __kernel_vsyscall ()
#1 0xf7e10eb6 in raise () from /lib/libc.so.6
#2 0xf7e124b1 in abort () from /lib/libc.so.6
#3 0x08048476 in foo (name=0xf7f99de0 <environ> "\f\316\377\377",
d=-2.6030469739081194e-220, e=-1.1363900720223263e-307,
f=2.8014219794078323e+283, g=-12908) at
/home/marxin/Programming/gcc3/gcc/testsuite/gcc.dg/builtin-apply2.c:33
#4 0x08048535 in bar (name=0x8048630 "eeee") at
/home/marxin/Programming/gcc3/gcc/testsuite/gcc.dg/builtin-apply2.c:38
#5 0x0804859d in main () at
/home/marxin/Programming/gcc3/gcc/testsuite/gcc.dg/builtin-apply2.c:43
As I've been reading GCC documentation:
Warning: if you use this switch, and num is nonzero, then you must build all
modules with the same value, including any libraries. This includes the system
libraries and startup modules.
That means, libc hasn't been built with the option and it explain the abort.
Am I right?
Martin
