public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu dot se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/39429] compiler create bad asm codes.
Date: Sat, 11 Jul 2009 20:20:00 -0000 [thread overview]
Message-ID: <20090711202041.1821.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39429-17427@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from mikpe at it dot uu dot se 2009-07-11 20:20 -------
It seems that cpu type and tuning options make a difference here. If I compile
with -mcpu and -mtune referring to a cpu that does not imply FL_LDSCHED, such
as arm740t, then I get the broken code that clobbers r0 before loading r3.
Changing cpu and tune types to a cpu that does imply FL_LDSCHED, such as arm8
or xscale, then r3 is loaded before r0 is clobbered and the sub becomes an rsb.
--
mikpe at it dot uu dot se changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mikpe at it dot uu dot se
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39429
next prev parent reply other threads:[~2009-07-11 20:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 7:25 [Bug c++/39429] New: " ryos at sinby dot com
2009-03-12 1:19 ` [Bug c++/39429] " ryos at sinby dot com
2009-03-16 22:53 ` rearnsha at gcc dot gnu dot org
2009-03-16 23:02 ` [Bug target/39429] " rearnsha at gcc dot gnu dot org
2009-07-11 20:20 ` mikpe at it dot uu dot se [this message]
2009-07-12 11:30 ` mikpe at it dot uu dot se
2009-07-12 20:51 ` ramana at gcc dot gnu dot org
2009-07-12 21:21 ` mikpe at it dot uu dot se
2009-07-12 23:58 ` mikpe at it dot uu dot se
2009-07-13 13:06 ` mikpe at it dot uu dot se
2009-07-13 13:07 ` mikpe at it dot uu dot se
[not found] <bug-39429-4@http.gcc.gnu.org/bugzilla/>
2015-03-12 11:29 ` ramana at gcc dot gnu.org
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=20090711202041.1821.qmail@sourceware.org \
--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).