public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu.se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/47192] m68k target - gcc uses stack frame after it has been unlinked when compiling with -Os
Date: Thu, 06 Jan 2011 19:38:00 -0000 [thread overview]
Message-ID: <bug-47192-4-VIpoTPLGAP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47192-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47192
Mikael Pettersson <mikpe at it dot uu.se> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mikpe at it dot uu.se
--- Comment #1 from Mikael Pettersson <mikpe at it dot uu.se> 2011-01-06 19:19:21 UTC ---
I can reproduce this with both 4.5.2 and 4.4.6 based crosses to
m68k-{elf,linux}.
The -mcpu=51qe option seems to cause mis-scheduling of the epilogue.
With -Os -S -mcpu=51qe:
.L3:
lea (-2,%fp),%a0
move.l -8(%fp),%d2
unlk %fp
move.w (%a0),stc.1197
rts
Without the -mcpu= option:
.L3:
move.w -2(%fp),stc.1199
move.l -8(%fp),%d2
unlk %fp
rts
prev parent reply other threads:[~2011-01-06 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 15:56 [Bug target/47192] New: " tda at ls83 dot eclipse.co.uk
2011-01-06 19:38 ` mikpe at it dot uu.se [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-47192-4-VIpoTPLGAP@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).