public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64052] compilation error "local frame unavailable" appears for some optimization levels
Date: Mon, 16 Feb 2015 18:09:00 -0000	[thread overview]
Message-ID: <bug-64052-4-kdW7MWD9jE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64052-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Georg-Johann Lay <gjl at gcc dot gnu.org> ---
(In reply to Eugene from comment #4)
> I am not arguing for the sample code to be compilable and functional.
> My expectation is a consistent compilation result regardless of the
> optimisation settings. If it fails with 'O0' should fail with 'Os' too.

IMO this "consistency" is not feasible as the result depends on the
optimization level and probably optimization switches.  For such a
"consistency" the compiler would have to know the results of all other possible
option sets.

Not all diagnostics are emit during lexing or parsing, many diagnostics depend
on further analysis of code and data and might run after early inlining or dead
code / data elimination.


      parent reply	other threads:[~2015-02-16 18:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 14:40 [Bug c++/64052] New: " eugene at hutorny dot in.ua
2014-11-24 16:14 ` [Bug target/64052] " rguenth at gcc dot gnu.org
2014-11-25 18:24 ` eugene at hutorny dot in.ua
2014-11-29 20:27 ` gjl at gcc dot gnu.org
2014-11-29 20:41 ` eugene at hutorny dot in.ua
2015-02-16 18:09 ` gjl at gcc dot gnu.org [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-64052-4-kdW7MWD9jE@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).