public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/62144] "Frame pointer required, but reserved" error with -fomit-frame-pointer but only with -m32 -O2
Date: Fri, 15 Aug 2014 10:02:00 -0000	[thread overview]
Message-ID: <bug-62144-4-Ejw2pwg9MM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62144-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62144

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-08-15
                 CC|                            |vmakarov at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
frame_pointer_needed is set by setup_can_eliminate.  Which means that desipte
-fomit-frame-pointer IRA is not able to eliminate the frame pointer?

Vlad?


  reply	other threads:[~2014-08-15 10:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-14 18:44 [Bug inline-asm/62144] New: " brooks at gcc dot gnu.org
2014-08-15 10:02 ` rguenth at gcc dot gnu.org [this message]
2014-09-29 20:31 ` [Bug inline-asm/62144] " brooks at gcc dot gnu.org
2014-10-01  2:00 ` vmakarov at gcc dot gnu.org
2014-10-01  2:07 ` brooks at gcc dot gnu.org
2014-10-28 16:51 ` luk32 at o2 dot pl
2014-10-29  8:26 ` jakub at gcc dot gnu.org
2014-10-29  9:46 ` luk32 at o2 dot pl
2021-09-14  9:53 ` [Bug target/62144] " pinskia 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-62144-4-Ejw2pwg9MM@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).