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 lto/60721] xcoral fails to build with LTO: internal compiler error: verify_flow_info failed
Date: Mon, 31 Mar 2014 13:50:00 -0000	[thread overview]
Message-ID: <bug-60721-4-P7jcSxVrqv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60721-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hubicka at gcc dot gnu.org

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
(gdb) p debug_bb (bb)
<bb 2>:
result_5 = getenv ("SMAC_STACK_SIZE");
if (result_5 != 0B)
  goto <bb 3>;
else
  goto <bb 5>;
(gdb) p debug_generic_expr (cfun->decl)
init_smac

in one unit getenv is pulled in via a header leading to

extern char *getenv (const char *__name) __attribute__ ((__nothrow__ ,
__leaf__)) __attribute__ ((__nonnull__ (1))) __attribute__
((__warn_unused_result__));

(note the leaf attribute), and in the other we have

int
main ( argc, argv )
    int argc;
    char **argv;
{
...
  extern char *getenv ();

this means that if cfun->calls_setjmp as in this case, this can make a
difference.  This is verifying after IPA transforms took place.

It seems that 'leaf' is a decl attribute and thus is not preserved
via gimple_call_fntype streaming (and also cannot be set for indirect calls).

Sth for stmt fixup similar as we handle noreturn?


  reply	other threads:[~2014-03-31 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31 13:41 [Bug lto/60721] New: " rguenth at gcc dot gnu.org
2014-03-31 13:50 ` rguenth at gcc dot gnu.org [this message]
2014-04-01 11:21 ` [Bug lto/60721] " rguenth at gcc dot gnu.org
2014-04-01 11:53 ` rguenth at gcc dot gnu.org
2014-04-01 12:24 ` jamborm at gcc dot gnu.org
2014-04-01 12:29 ` rguenth 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-60721-4-P7jcSxVrqv@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).