public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jsantiago@chrysalisdev.com To: gcc-gnats@gcc.gnu.org Subject: c++/8089: c++ code with syntax error causes internal compiler error segfault Date: Sun, 29 Sep 2002 11:26:00 -0000 [thread overview] Message-ID: <20020929182237.12085.qmail@sources.redhat.com> (raw) >Number: 8089 >Category: c++ >Synopsis: c++ code with syntax error causes internal compiler error segfault >Confidential: no >Severity: serious >Priority: low >Responsible: unassigned >State: open >Class: ice-on-illegal-code >Submitter-Id: net >Arrival-Date: Sun Sep 29 11:26:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Jose Santiago >Release: 3.2 and 2.95.3 and probably others >Organization: >Environment: System: Linux hpc003 2.4.19pre1 #4 SMP Fri Mar 1 09:30:24 CST 2002 i686 unknown Architecture: i686 host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: i686-pc-linux-gnu configured with: ../configure --prefix=/appl/gcc-3.2 --disable-shared --enable-threads --enable-version-specific-runtime-libs --with-included-gettext Thread model: posix gcc version 3.2 >Description: g++ generates an Internal Compiler Error and segfaults with the following program containing a syntax error: class S { public: class SS { public: enum STATE_TYPE { INITIAL, INTERMEDIATE, FINAL }; }; /* class S:SS */ }; /* class S */ int main(void) { enum S::SS::STATE_TYPE state1; //The following line is a syntax error that generates an //internal compiler error on gcc-2.95.3 and gcc-3.2 enum S::SS state2; return 0; } >How-To-Repeat: compile the attatched program using gcc-3.2, gcc-2.95.3 and probably others. >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="main.cpp" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="main.cpp" CmNsYXNzIFMgewoKICBwdWJsaWM6CiAgICBjbGFzcyBTUyB7CiAgICAgIHB1YmxpYzoKICAgICAg ICBlbnVtIFNUQVRFX1RZUEUgeyBJTklUSUFMLCBJTlRFUk1FRElBVEUsIEZJTkFMIH07CiAgICB9 OyAvKiBjbGFzcyBTOlNTICovCgp9OyAvKiBjbGFzcyBTICovCgppbnQgbWFpbih2b2lkKQp7Cgog IGVudW0gUzo6U1M6OlNUQVRFX1RZUEUgc3RhdGUxOwoKLy9UaGUgZm9sbG93aW5nIGxpbmUgaXMg YSBzeW50YXggZXJyb3IgdGhhdCBnZW5lcmF0ZXMgYW4gaW50ZXJuYWwgY29tcGlsZXIgZXJyb3IK Ly9vbiBnY2MtMi45NS4zCiAgZW51bSBTOjpTUyBzdGF0ZTI7CgogIHJldHVybiAwOwp9CiAgICAg IAo=
next reply other threads:[~2002-09-29 18:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-29 11:26 jsantiago [this message] 2002-10-04 8:14 lerdsuwa 2003-01-01 13:47 neroden
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=20020929182237.12085.qmail@sources.redhat.com \ --to=jsantiago@chrysalisdev.com \ --cc=gcc-gnats@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).