public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/35078] New: ICE with reference in parallel for loop Date: Mon, 04 Feb 2008 13:54:00 -0000 [thread overview] Message-ID: <bug-35078-1771@http.gcc.gnu.org/bugzilla/> (raw) The following invalid code snippet triggers an ICE since GCC 4.2.0 when compiled with -fopenmp: =========================================================== template<int> void foo() { #pragma omp parallel for for (int& i = 0; i < 10; ++i) ; } =========================================================== bug.cc: In function 'void foo()': bug.cc:5: internal compiler error: in build_modify_expr, at cp/typeck.c:5809 Please submit a full bug report, [etc.] Without templates the situation is not much better: =========================================================== void foo() { int j = 0; #pragma omp parallel for for (int& i = j; i < 10; ++i) ; } =========================================================== bug.cc: In function 'void foo()': bug.cc:6: error: 'i' declared as reference but not initialized bug.cc:7: internal compiler error: in build_modify_expr, at cp/typeck.c:5809 Please submit a full bug report, [etc.] The compiler issues a bogus error message (the variable is initialized), and crashes afterwards. -- Summary: ICE with reference in parallel for loop Product: gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: ice-on-invalid-code, diagnostic, monitored, openmp Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: reichelt at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35078
next reply other threads:[~2008-02-04 13:54 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-04 13:54 reichelt at gcc dot gnu dot org [this message] 2008-02-04 14:28 ` [Bug c++/35078] " rguenth at gcc dot gnu dot org 2008-02-15 17:57 ` jakub at gcc dot gnu dot org 2008-02-18 10:20 ` jakub at gcc dot gnu dot org 2008-02-19 10:16 ` jakub at gcc dot gnu dot org 2008-03-06 22:10 ` jakub at gcc dot gnu dot org 2008-03-10 10:26 ` jakub 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=bug-35078-1771@http.gcc.gnu.org/bugzilla/ \ --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).