public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ramrad01 at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/54398] Incorrect ARM assembly when building with -fno-omit-frame-pointer -O2
Date: Tue, 11 Sep 2012 10:44:00 -0000	[thread overview]
Message-ID: <bug-54398-4-13lyVrLB0s@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54398-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from ramrad01 at arm dot com 2012-09-11 10:44:30 UTC ---
On 09/11/12 07:09, jakub at gcc dot gnu.org wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54398
>
> Jakub Jelinek <jakub at gcc dot gnu.org> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |jakub at gcc dot gnu.org
>
> --- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-09-11 06:09:13 UTC ---
> cselib.c has for this the various spots that special case
> HARD_FRAME_POINTER_REGNUM (or STACK_POINTER_REGNUM or FRAME_POINTER_REGNUM).
> Please see why that doesn't work in this case.
>

This rings a bell.

Maybe the patch mentioned below needs backporting given Carrot is 
reporting this against the 4.6 branch. What's not clear if this is 
reproducible on anything later though.

http://old.nabble.com/-PATCH--Prevent-cselib-substitution-of-FP,-SP,-SFP-td33080657.html

Full disclaimer that I've not investigated whether the same problem 
occurs on trunk.

HTH,
Ramana


  parent reply	other threads:[~2012-09-11 10:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29  0:21 [Bug other/54398] New: " asharif at gcc dot gnu.org
2012-08-30 23:32 ` [Bug other/54398] " ramana.radhakrishnan at gmail dot com
2012-08-30 23:32 ` [Bug other/54398] New: " Ramana Radhakrishnan
2012-09-04 19:43 ` [Bug other/54398] " ramana at gcc dot gnu.org
2012-09-04 22:47 ` asharif at gcc dot gnu.org
2012-09-04 22:49 ` asharif at gcc dot gnu.org
2012-09-07  1:19 ` carrot at google dot com
2012-09-11  0:11 ` carrot at google dot com
2012-09-11  6:09 ` jakub at gcc dot gnu.org
2012-09-11 10:44 ` ramrad01 at arm dot com [this message]
2012-09-12 20:57 ` carrot at google dot com

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-54398-4-13lyVrLB0s@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).