public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Reichelt <reichelt@igpm.rwth-aachen.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/5661: Gcc 3.0.3 Seg faults compiling bad code
Date: Tue, 12 Feb 2002 05:46:00 -0000	[thread overview]
Message-ID: <20020212134601.11638.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/5661; it has been noted by GNATS.

From: Reichelt <reichelt@igpm.rwth-aachen.de>
To: adrian.cornish@bluedreamer.com, gcc-gnats@gcc.gnu.org,
        gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: c++/5661: Gcc 3.0.3 Seg faults compiling bad code
Date: Tue, 12 Feb 2002 15:04:20 +0100

 Hi,
 
 the problem can be reduced to the following code, which causes an ICE
 with gcc 3.1 20020204 (experimental) on i686-pc-linux-gnu and
 mips-sgi-irix6.5:
 
 -------------------snip here--------------------
 template <class T> struct A
 {
     A() throw() {}
 };
 
 struct B
 {
     static const int s;
     A<int[s]> a;  // illegal, constant value not known
 };
 
 const int B::s=16;
 
 B b;
 -------------------snip here--------------------
 
 The error message is:
 
 PR5661.cpp: In constructor `B::B()':
 PR5661.cpp:14: internal error: Segmentation fault
 Please submit a full bug report, [etc.]
 
 Greetings,
 Volker Reichelt
 
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5661
 
 


             reply	other threads:[~2002-02-12 13:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-12  5:46 Reichelt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-11 12:59 mmitchel
2002-10-03 22:38 mmitchel
2002-05-20  6:58 lerdsuwa
2002-02-11 14:16 adrian.cornish

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=20020212134601.11638.qmail@sources.redhat.com \
    --to=reichelt@igpm.rwth-aachen.de \
    --cc=gcc-prs@gcc.gnu.org \
    --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).