public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/57649] New: [4.7 Regression] ICE in set_is_used
Date: Wed, 19 Jun 2013 09:33:00 -0000	[thread overview]
Message-ID: <bug-57649-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 57649
           Summary: [4.7 Regression] ICE in set_is_used
           Product: gcc
           Version: 4.7.3
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jakub at gcc dot gnu.org
                CC: matz at gcc dot gnu.org

void bar (const char *);
void
foo ()
{
  static const char *s = __PRETTY_FUNCTION__;
  struct T { T () { bar (s); } } t;
}

ICEs at -O2 starting with r179618 on 4.7 branch, went away with r187719 for
4.8+.

Similarly C -O2:
void bar (const char *);
void
foo (void)
{
  static const char *s = __PRETTY_FUNCTION__;
  auto void baz (void) { bar (s); }
  baz ();
}

The problem is that the s variable isn't referenced in foo during
*referenced_vars pass, is referenced in another function (nested or local class
method), but at that point the DECL_INITIAL of the var isn't marked, and later
on when the nested/local class method is inlined nothing marks the
DECL_INITIAL.
Perhaps the inliner should somewhere go through all gimple_referenced_vars of
the callee and for each TREE_STATIC var with DECL_CONTEXT of the caller just
call add_referenced_var?


             reply	other threads:[~2013-06-19  9:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19  9:33 jakub at gcc dot gnu.org [this message]
2013-06-19  9:33 ` [Bug middle-end/57649] " jakub at gcc dot gnu.org
2013-06-19  9:39 ` ebotcazou at gcc dot gnu.org
2013-06-19  9:40 ` jakub at gcc dot gnu.org
2013-06-19  9:47 ` jakub at gcc dot gnu.org
2013-06-19 10:42 ` rguenth at gcc dot gnu.org
2013-06-19 10:46 ` jakub at gcc dot gnu.org
2013-06-19 10:52 ` rguenth at gcc dot gnu.org
2014-06-12 13:28 ` 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-57649-4@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).