public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/51262] [4.7 Regression] ICE: SIGSEGV in primary_template_instantiation_p (pt.c:2874) with -flto -g
Date: Fri, 09 Dec 2011 03:49:00 -0000	[thread overview]
Message-ID: <bug-51262-4-zTCxcHXC0U@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51262-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Jason Merrill <jason at redhat dot com> 2011-12-09 03:25:17 UTC ---
On 12/08/2011 11:46 AM, rguenth at gcc dot gnu.org wrote:
> Dodji, Jason, can such anonymous name types ever have TYPE_DECL_ALIAS_P
> set?

They can't, but

> -  else if (CLASS_TYPE_P (t) &&  !TYPE_DECL_ALIAS_P (TYPE_NAME (t)))
> +  else if (CLASS_TYPE_P (t)
> +           && TYPE_NAME (t) && !TYPE_DECL_ALIAS_P (TYPE_NAME (t)))
>       return CLASSTYPE_TEMPLATE_INSTANTIATION (t)
>             && PRIMARY_TEMPLATE_P (CLASSTYPE_TI_TEMPLATE (t));

I would reverse the sense here so that the condition is satisfied by a 
null TYPE_NAME, since an anonymous union is a non-alias class.

Jason


  parent reply	other threads:[~2011-12-09  3:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22  0:02 [Bug debug/51262] New: " zsojka at seznam dot cz
2011-12-05 14:25 ` [Bug debug/51262] " rguenth at gcc dot gnu.org
2011-12-06 14:08 ` rguenth at gcc dot gnu.org
2011-12-06 14:24 ` rguenth at gcc dot gnu.org
2011-12-07  7:22 ` reichelt at gcc dot gnu.org
2011-12-08 17:06 ` rguenth at gcc dot gnu.org
2011-12-09  3:49 ` jason at redhat dot com [this message]
2011-12-09  9:22 ` rguenth at gcc dot gnu.org
2011-12-12  8:39 ` rguenth at gcc dot gnu.org
2011-12-12  8:40 ` 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-51262-4-zTCxcHXC0U@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).