On Feb 16, 2008 8:01 PM, Kaveh R. Ghazi <[EMAIL PROTECTED]> wrote: > From: "Richard Guenther" <[EMAIL PROTECTED]> > > >> You can trigger the bug in a regular pass by applying the following > >> noinline patch to the testcase. Thoughts? > > > > How does it break? It works for me with noinline and with -fPIC. > > Richard. > > I'm running with mainline revision 132367 on x86_64-unknown-linux-gnu (i.e. > lp64, not ilp32). When I run the failing testcase under gdb I get: > > (gdb) run > Starting program: /tmp/kg/build/gcc/testsuite/gcc/pr32268.exe > > Program received signal SIGABRT, Aborted. > 0x00002b2ae231d07b in raise () from /lib/libc.so.6 > (gdb) up > #1 0x00002b2ae231e84e in abort () from /lib/libc.so.6 > (gdb) up > #2 0x0000000000400575 in main () at > /tmp/kg/egcc-SVN20080216/gcc/testsuite/gcc.target/i386/pr32268.c:32 > 32 abort(); > (gdb) list > 27 if (r != ((double) a < (double) b)) > 28 abort(); > 29 > 30 r = test_gt (a, b); > 31 if (r != ((double) a > (double) b)) > 32 abort(); > 33 > 34 return 0; > 35 } > (gdb) p a > $1 = 0 > (gdb) p b > $2 = 0 > > > "b" should be 1.0.
Ok. So this works for me with r132367, with the original testcase and flags, with the original testcase and -fPIC and with the modified testcase and both cases. Richard.
