https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63347
Jeffrey A. Law changed:
What|Removed |Added
CC||law at redhat dot com
--- Comment #10 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63347
--- Comment #9 from Mikael Pettersson ---
This wrong-code started with Bernd's r171845, possibly by exposing a latent
issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63347
--- Comment #8 from Andreas Schwab ---
*** Bug 64233 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63347
--- Comment #7 from Jonathan Larmour ---
I have also now submitted bug 64233 which is about a different testcase which
also gets misoptimised. This may or may not be related, but could well be since
-fschedule-insns is what makes a difference, an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63347
Andreas Schwab changed:
What|Removed |Added
Status|WAITING |NEW
--- Comment #6 from Andreas Schwab
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63347
Mikael Pettersson changed:
What|Removed |Added
CC||mikpelinux at gmail dot com
--- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63347
--- Comment #4 from Jonathan Larmour ---
I have just double-checked, and my gcc 4.8.3 definitely doesn't generate the
'tstl', but it looks like you're bang on right about how gcc was configured: I
configured it with --with-arch=cf. Sorry I should
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63347
--- Comment #3 from Mikael Pettersson ---
I can't reproduce with a vanilla gcc-4.8.3 configured for m68k-elf. For the
"if (0x0 == haddr) ..." it generates:
lea (20,%sp),%sp
tst.l %d2
seq %d2
extb.l %d2
ne
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63347
Jonathan Larmour changed:
What|Removed |Added
Known to fail||4.8.3
--- Comment #2 from Jonathan La
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63347
Andreas Schwab changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
10 matches
Mail list logo