public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fw at deneb dot enyo dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/13268] New: ICE on illegal code: bool foo(const operator&); Date: Tue, 02 Dec 2003 06:29:00 -0000 [thread overview] Message-ID: <20031202062909.13268.fw@deneb.enyo.de> (raw) This apparently illegal code snippet triggers an ICE: bool foo(const operator&); /tmp/t.cc:1: error: declaration of `operator&' as non-function /tmp/t.cc:1: internal compiler error: Segmentation fault -- Summary: ICE on illegal code: bool foo(const operator&); Product: gcc Version: 3.4 Status: UNCONFIRMED Severity: minor Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: fw at deneb dot enyo dot de CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13268
next reply other threads:[~2003-12-02 6:29 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-12-02 6:29 fw at deneb dot enyo dot de [this message] 2003-12-02 14:31 ` [Bug c++/13268] " bangerth at dealii dot org 2003-12-02 15:51 ` pinskia at gcc dot gnu dot org 2003-12-24 6:31 ` pinskia at gcc dot gnu dot org 2003-12-24 18:03 ` pinskia at gcc dot gnu dot org 2003-12-24 18:16 ` pinskia at gcc dot gnu dot org 2003-12-25 16:46 ` cvs-commit at gcc dot gnu dot org 2003-12-25 17:24 ` pinskia at gcc dot gnu dot org 2003-12-30 21:13 ` reichelt at gcc dot gnu dot org 2003-12-30 21:15 ` pinskia at gcc dot gnu dot org 2004-01-13 4:12 ` pinskia at gcc dot gnu dot org 2004-01-14 5:41 ` pinskia at gcc dot gnu dot org 2004-04-23 19:57 ` pinskia at gcc dot gnu dot org 2004-05-24 14:34 ` pinskia at gcc dot gnu dot org 2004-09-27 4:01 ` pinskia at gcc dot gnu dot org 2004-12-22 3:35 ` cvs-commit at gcc dot gnu dot org 2004-12-23 16:21 ` reichelt at gcc dot gnu dot org 2005-08-05 21:04 ` mmitchel at gcc dot gnu dot org 2005-08-05 21:04 ` mmitchel 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=20031202062909.13268.fw@deneb.enyo.de \ --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).