public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mattyt-bugzilla at tpg dot com dot au" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/13975] New: ICE on misplaced visibility specifier. Date: Mon, 02 Feb 2004 10:27:00 -0000 [thread overview] Message-ID: <20040202102736.13975.mattyt-bugzilla@tpg.com.au> (raw) Here's a "reduced test case" in the true sense of the term. The code: public: causes this error: test.cc:1: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. The code: private: gives a slightly different error: test.cc:1: error: expected unqualified-id before " Internal compiler error: Error reporting routines re-entered. ... and protected works OK! -- Summary: ICE on misplaced visibility specifier. Product: gcc Version: 3.4.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mattyt-bugzilla at tpg dot com dot au CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13975
next reply other threads:[~2004-02-02 10:27 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-02-02 10:27 mattyt-bugzilla at tpg dot com dot au [this message] 2004-02-02 14:30 ` [Bug c++/13975] [3.4/3.5 Regression] " pinskia at gcc dot gnu dot org 2004-02-03 4:34 ` mmitchel at gcc dot gnu dot org 2004-02-03 4:49 ` pinskia at gcc dot gnu dot org 2004-02-03 8:26 ` pinskia at gcc dot gnu dot org 2004-02-03 16:12 ` cvs-commit at gcc dot gnu dot org 2004-02-03 16:53 ` cvs-commit at gcc dot gnu dot org 2004-02-03 16:54 ` cvs-commit at gcc dot gnu dot org 2004-02-03 16:57 ` mmitchel at gcc dot gnu dot org 2004-02-19 19:35 ` pinskia at gcc dot gnu dot 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=20040202102736.13975.mattyt-bugzilla@tpg.com.au \ --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: 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).