public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/60162] [4.9 lra regression] mlra appears to be using the FP registers for integer values and then moving on to GPR registers.
Date: Wed, 12 Feb 2014 22:46:00 -0000 [thread overview]
Message-ID: <bug-60162-4-C6V4p0eHFZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60162-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60162
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|middle-end |rtl-optimization
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This sounds like the cost model of moving between register classes is not
correct for the arm backend.
next prev parent reply other threads:[~2014-02-12 22:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 22:08 [Bug middle-end/60162] New: [4.9 lra regression] mlra appears to be using the FP registers as a set of spill registers for ARM ramana at gcc dot gnu.org
2014-02-12 22:46 ` pinskia at gcc dot gnu.org [this message]
2014-02-13 9:22 ` [Bug rtl-optimization/60162] [4.9 Regression][lra] mlra appears to be using the FP registers for integer values and then moving on to GPR registers rguenth at gcc dot gnu.org
2014-02-13 10:26 ` ramana at gcc dot gnu.org
2014-02-13 12:10 ` ktkachov at gcc dot gnu.org
2014-03-06 21:30 ` vmakarov at gcc dot gnu.org
2014-03-31 9:24 ` rguenth at gcc dot gnu.org
2014-04-22 11:35 ` [Bug rtl-optimization/60162] [4.9/4.10 " jakub at gcc dot gnu.org
2014-07-16 13:27 ` jakub at gcc dot gnu.org
2014-10-30 10:38 ` [Bug rtl-optimization/60162] [4.9/5 " jakub at gcc dot gnu.org
2015-01-16 15:46 ` 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=bug-60162-4-C6V4p0eHFZ@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).