http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48565
--- Comment #5 from Jonathan Wakely 2011-04-13
15:12:31 UTC ---
(In reply to comment #4)
> How did you configure the library to hit this
> problem?
I know you said with -pipe in your CFLAGS, is that all?
You could probably edit scripts/testsu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48565
--- Comment #4 from Jonathan Wakely 2011-04-13
15:09:36 UTC ---
It shouldn't happen unless the person running the testsuite specifies it, so
they can not specify it. How did you configure the library to hit this
problem?
Jakub's suggestion is t
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48565
--- Comment #3 from Allan McRae 2011-04-13
10:35:24 UTC ---
So, just to clarify... Is this being seen as something that the person
building the gcc test-suite should deal with or something that should be dealt
with in the test-suite?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48565
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #2 f
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48565
--- Comment #1 from Jonathan Wakely 2011-04-12
07:48:36 UTC ---
Those tests have to use -save-temps to inspect the assembler output, I think
the answer is to not use -pipe
