public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/58084] FAIL: gcc.dg/torture/pr8081.c  -O2 -flto -fno-use-linker-plugin -flto-partition=none  (internal compiler error)
Date: Mon, 12 Aug 2013 12:50:00 -0000	[thread overview]
Message-ID: <bug-58084-4-NufBlb5ikK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58084-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
OK, the problem is that the return type of nested function is variable sized
type of the outer functions.  These types go to function sections and are not
merged.
We used to not ICE just by luck - RESTLT_DECL went to global section that
created yet another unmerged version of the type that got into RESULT_DECL.

This is not only problem of this kind and I am not quite sure what to do here:
either we need to invent way how to refer items in the other function section,
or we need to put all abstract origins into global stream completely.
The second would be very expensive...

In this partiuclar case we probably can just teach tree-inline to
VOID_CONVERT_EXPR when needed?


  parent reply	other threads:[~2013-08-12 12:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-58084-4@http.gcc.gnu.org/bugzilla/>
2013-08-05 10:17 ` ktkachov at gcc dot gnu.org
2013-08-05 10:18 ` ktkachov at gcc dot gnu.org
2013-08-06 20:00 ` pthaugen at gcc dot gnu.org
2013-08-08  9:38 ` ramana at gcc dot gnu.org
2013-08-09 12:40 ` ro at gcc dot gnu.org
2013-08-12 12:28 ` hubicka at gcc dot gnu.org
2013-08-12 12:50 ` hubicka at gcc dot gnu.org [this message]
2013-08-19 22:28 ` [Bug lto/58084] [4.9 Regression] " hp at gcc dot gnu.org
2013-08-19 23:38 ` hp at gcc dot gnu.org
2013-08-29 13:17 ` rguenth at gcc dot gnu.org
2013-09-04 16:59 ` hubicka at gcc dot gnu.org
2013-09-17 15:22 ` hubicka 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-58084-4-NufBlb5ikK@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).