public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug rtl-optimization/38452]  New: delared branch scheduling doesn't fully take return into account
@ 2008-12-09 14:10 amylaar at gcc dot gnu dot org
  0 siblings, 0 replies; only message in thread
From: amylaar at gcc dot gnu dot org @ 2008-12-09 14:10 UTC (permalink / raw)
  To: gcc-bugs

Due to a backend bug, dbr had picked a delay slot insn for annul-true which was
not actually elegible for annul-true.  When I fixed the bug, I found that
instead an insn from the target path was chosen, the restore of the return
address, as the target is an epilogue.
The original instruction, mov r4,-1 , would have been suitable as a non-anulled
delay slot insn, since r4 is a call-used register, and the function does not
return a value that would require r4 to represent, and the epilogue did not
make use of the value in r4.

I've seen this for ARC compiling
cjpeg/jcmarker.c
using the options:
-mnorm -mswap -mmul64 -mARC600 -O3 -fomit-frame-pointer

in the function write_file_header.

For obvious reasons I can't provide preprocessed source for some eighty years.


-- 
           Summary: delared branch scheduling doesn't fully take return into
                    account
           Product: gcc
           Version: 4.2.1
            Status: UNCONFIRMED
          Keywords: missed-optimization
          Severity: minor
          Priority: P3
         Component: rtl-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: amylaar at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38452


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2008-12-09 14:10 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-12-09 14:10 [Bug rtl-optimization/38452] New: delared branch scheduling doesn't fully take return into account amylaar at gcc dot gnu dot org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).