public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, me@leflo.de,
	nobody@gcc.gnu.org
Subject: Re: c++/9600: [3.2 regression] ICE with typedefs in template class
Date: Thu, 06 Feb 2003 19:57:00 -0000	[thread overview]
Message-ID: <20030206195753.14610.qmail@sources.redhat.com> (raw)

Old Synopsis: typedefs in template class
New Synopsis: [3.2 regression] ICE with typedefs in template class

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Thu Feb  6 19:57:53 2003
State-Changed-Why:
    Confirmed: ICEs with 3.2.*, works with 2.95, 3.3 and 3.4.
    Here's a redux:
    ----------------------------
    template<typename T> struct X {
      typedef T* type();
      type t;
    };
    template struct X<int>;
    ------------------------
    tmp/g> /home/bangerth/bin/gcc-3.2.2-pre/bin/c++ -c x.cc
    x.cc: In instantiation of `X<int>':
    x.cc:5:   instantiated from here
    x.cc:3: internal error: Segmentation fault
    Please submit a full bug report,
    
    
    I am unsure about the validity of the code, in particular
      typedef T* type();
    I guess at the best this would qualify as a reference to
    a function. Making this a pointer-to-function like
      typedef T* (*type)();
    makes the compilation go through. So I guess this is an
    ICE-on-illegal.
    
    W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9600


             reply	other threads:[~2003-02-06 19:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-06 19:57 bangerth [this message]
2003-04-25 21:10 jbuck

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=20030206195753.14610.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=me@leflo.de \
    --cc=nobody@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).