public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bowie dot owens at csiro dot au" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/26611] New: openmp gomp ICE at gimplify.c:4257 Date: Wed, 08 Mar 2006 22:30:00 -0000 [thread overview] Message-ID: <bug-26611-12330@http.gcc.gnu.org/bugzilla/> (raw) I consistently get the following ICE on this C++ code. omp_harness.cpp:39: internal compiler error: in omp_add_variable, at gimplify.c:4257 The code is not legit and there are several errors but this is because I have cut down a larger program. I am using the gomp-branch and gcc -v reports: Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../gomp-20050608-branch/configure --prefix=/local_scratch/owe043/gcc_gomp Thread model: posix gcc version 4.2.0-gomp-20050608-branch 20060216 (experimental) (merged 20060216) The command line I used to compile was: g++ -save-temps -fopenmp omp_harness.cpp -- Summary: openmp gomp ICE at gimplify.c:4257 Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgomp AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: bowie dot owens at csiro dot au GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26611
next reply other threads:[~2006-03-08 22:30 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-03-08 22:30 bowie dot owens at csiro dot au [this message] 2006-03-08 22:34 ` [Bug libgomp/26611] " bowie dot owens at csiro dot au 2006-03-08 22:39 ` bowie dot owens at csiro dot au 2006-03-09 18:33 ` [Bug middle-end/26611] [GOMP] " pinskia at gcc dot gnu dot org 2006-03-09 18:43 ` pinskia at gcc dot gnu dot org 2006-03-23 19:54 ` [Bug middle-end/26611] " jakub at gcc dot gnu dot org 2006-03-24 16:14 ` jakub at gcc dot gnu dot org 2006-03-27 16:13 ` 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-26611-12330@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).