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/48044] [4.6 Regression] ICE in function_and_variable_visibility, at ipa.c:875
Date: Thu, 10 Mar 2011 09:36:00 -0000	[thread overview]
Message-ID: <bug-48044-4-mTmNtM1kPI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48044-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-03-10 09:36:12 UTC ---
c's vnode is first varpool_mark_needed_node, then it is again marked as not
needed by cgraph_remove_unreachable_nodes (so far both for -O0 and -O1+)
and as nothing like finish_aliases_1 is run afterwards again, the vnode is
!vnode->needed && vnode->force_output.  In -O1 case the varpool node is removed
altogether as not needed (which is strange, the vnode's decl is going to be
emitted anyway), but for -O0:
  /* We must release unused extern inlines or sanity checking will fail.  Rest
of transformations
     are undesirable at -O0 since we do not want to remove anything.  */
  if (!optimize)
    return changed;

  if (file)
    fprintf (file, "Reclaiming variables:");

the reclaiming isn't done, so the vnode remains !vnode->needed and we ICE on it
later on.

I wonder if cgraph_remove_unreachable_nodes shouldn't be somehow alias pairs
aware (can it e.g. call find_aliases_1 again?), or at least for !optimize
shouldn't it avoid clearing vnode->needed for vnode->force_output?


  parent reply	other threads:[~2011-03-10  9:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 12:13 [Bug middle-end/48044] New: " rguenth at gcc dot gnu.org
2011-03-09 12:28 ` [Bug middle-end/48044] " rguenth at gcc dot gnu.org
2011-03-10  9:03 ` jakub at gcc dot gnu.org
2011-03-10  9:36 ` jakub at gcc dot gnu.org [this message]
2011-03-10 12:51 ` hubicka at ucw dot cz
2011-03-11 13:45 ` jakub at gcc dot gnu.org
2011-03-11 14:46 ` jakub at gcc dot gnu.org
2011-03-11 14:47 ` jakub at gcc dot gnu.org
2011-03-11 14:52 ` jakub 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-48044-4-mTmNtM1kPI@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).