public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "scovich at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/45959] [4.6 Regression] ICE: tree code 'template_type_parm' is not supported in gimple streams with -flto/-fwhopr
Date: Mon, 11 Oct 2010 13:54:00 -0000	[thread overview]
Message-ID: <20101011135400.64_DtyTE6Cf_uabygubZH0LBol9OJsN1nJNf79I6TAw@z> (raw)
In-Reply-To: <bug-45959-4@http.gcc.gnu.org/bugzilla/>

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

Ryan Johnson <scovich at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |scovich at gmail dot com

--- Comment #6 from Ryan Johnson <scovich at gmail dot com> 2010-10-11 13:53:42 UTC ---
Actually, this isn't a regression -- not on 4.6, at least. The following
minimal test case makes x86_64-unknown-linux-gnu-gcc-4.5.1 die with the same
error message:

$ cat > lto-bug.h <<EOF
#pragma interface
template<class T> struct foo;
template<class T>
struct foo<T*&> : foo<T&> {
    foo<T*&>(T* t) : foo<T&>(*t) { }
};
EOF

$ cat > lto-bug.C <<EOF
#pragma implementation "lto-bug.h"
#include "lto-bug.h"
EOF

$ gcc-4.5.1 -flto lto-bug.C
In file included from lto-bug.C:2:0:
lto-bug.h:6:2: internal compiler error: tree code ‘template_type_parm’ is not
supported in gimple streams
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

Removing anything at all makes the ICE disappear

I don't have a copy of the 4.6 sources to test whether the just checked-in fix
takes care of this... reopen?


  parent reply	other threads:[~2010-10-11 13:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-10  8:18 [Bug lto/45959] New: " zsojka at seznam dot cz
2010-10-10 11:29 ` [Bug lto/45959] " rguenth at gcc dot gnu.org
2010-10-10 11:30 ` rguenth at gcc dot gnu.org
2010-10-10 20:11 ` jason at gcc dot gnu.org
2010-10-11 13:26 ` jason at gcc dot gnu.org
2010-10-11 13:30 ` jason at gcc dot gnu.org
2010-10-11 13:54 ` scovich at gmail dot com [this message]
2010-10-11 16:50 ` jason at gcc dot gnu.org
2021-08-25 22:58 ` pinskia 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=20101011135400.64_DtyTE6Cf_uabygubZH0LBol9OJsN1nJNf79I6TAw@z \
    --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).