public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Kriang Lerdsuwanakij <lerdsuwa@users.sourceforge.net> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/9706: Internal error: segmentation fault Date: Tue, 18 Feb 2003 15:16:00 -0000 [thread overview] Message-ID: <20030218151600.17225.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/9706; it has been noted by GNATS. From: Kriang Lerdsuwanakij <lerdsuwa@users.sourceforge.net> To: Gabriel Huecas Fernandez-Toribio <gabriel@dit.upm.es> Cc: lerdsuwa@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c++/9706: Internal error: segmentation fault Date: Tue, 18 Feb 2003 22:14:31 +0700 Thanks for the report. I closed this bug report because it has been fixed in the main cvs (future GCC 3.4). Fixing this bug for GCC 3.3 is very unlikely since it's very close to the release date now. --Kriang Gabriel Huecas Fernandez-Toribio wrote: >It is not a bug, indeed. The code is not C++, >but I expected a "syntax error" or "semantic error", >but not a "internal error: segmentation fault". > >The compiler should not crash, in my opinion. > >Well, g++ asked to submit a report and I did. > >gabriel > >On 16 Feb 2003 lerdsuwa@gcc.gnu.org wrote: > > > >>Synopsis: Internal error: segmentation fault >> >>State-Changed-From-To: analyzed->closed >>State-Changed-By: lerdsuwa >>State-Changed-When: Sun Feb 16 18:04:26 2003 >>State-Changed-Why: >> Not a bug according to 3.3.7 p2. The declaration 'int XXX;' hides 'class XXX'. The class 'XXX' can be accessed using elaborated type specifier. >> >>http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9706 >> >> >> > > >
next reply other threads:[~2003-02-18 15:16 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-18 15:16 Kriang Lerdsuwanakij [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-18 16:16 Gabriel Huecas Fernandez-Toribio 2003-02-17 15:06 Gabriel Huecas Fernandez-Toribio 2003-02-16 18:04 lerdsuwa 2003-02-14 21:40 bangerth 2003-02-14 14:36 gabriel
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=20030218151600.17225.qmail@sources.redhat.com \ --to=lerdsuwa@users.sourceforge.net \ --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: linkBe 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).