public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppluzhnikov at charter dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/22008] New: ICE on valid code Date: Fri, 10 Jun 2005 18:18:00 -0000 [thread overview] Message-ID: <20050610181800.22008.ppluzhnikov@charter.net> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1116 bytes --] The test was reduced from PlumHall test X_132p92: $ cat x_132p92.cc struct X_132p92 { static int k; // [1] X_132p92(const X_132p92 &x); // [2] }; void f_132p92(volatile X_132p92 x) // [3] { bool b = x.k >= 1; } $ g++4 -c x_132p92.cc x_132p92.cc: In function â: x_132p92.cc:8: internal compiler error: in create_tmp_var, at gimplify.c:368 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. Commenting out "static" at [1], copy-ctor at [2], or volatile at [3] "cures" the bug. -- Summary: ICE on valid code Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: ppluzhnikov at charter dot net CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: same GCC host triplet: i386-redhat-linux, x86_64-unknown-linux-gnu GCC target triplet: same http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22008
next reply other threads:[~2005-06-10 18:18 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-06-10 18:18 ppluzhnikov at charter dot net [this message] 2005-06-10 18:56 ` [Bug c++/22008] [4.0/4.1 Regression] " pinskia at gcc dot gnu dot org 2005-07-01 19:59 ` pinskia at gcc dot gnu dot org 2005-07-06 17:04 ` mmitchel at gcc dot gnu dot org 2005-09-02 15:41 ` [Bug c++/22008] [4.0/4.1 Regression] ICE on valid code, create_tmp_var 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=20050610181800.22008.ppluzhnikov@charter.net \ --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).