public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/25952] New: -fopenmp causes ICE on valid code Date: Wed, 25 Jan 2006 00:44:00 -0000 [thread overview] Message-ID: <bug-25952-6528@http.gcc.gnu.org/bugzilla/> (raw) Example: int toto() { int a=0; #pragma omp single { for (int i=0; i<10; ++i) a += i; } return a; } int main() { return toto(); } ---- Even though we don't support openmp currently, this should not ICE. -- Summary: -fopenmp causes ICE on valid code Product: gcc Version: unknown Status: UNCONFIRMED Keywords: openmp Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pinskia at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25952
next reply other threads:[~2006-01-25 0:44 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-01-25 0:44 pinskia at gcc dot gnu dot org [this message] 2006-02-24 18:30 ` [Bug c++/25952] " pinskia at gcc dot gnu dot org 2006-03-09 18:31 ` pinskia at gcc dot gnu dot org 2006-03-14 1:25 ` 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=bug-25952-6528@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).