public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "evstupac at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/59984] New: OpenMP and Cilk Plus SIMD pragma makes loop incorrect Date: Wed, 29 Jan 2014 14:41:00 -0000 [thread overview] Message-ID: <bug-59984-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59984 Bug ID: 59984 Summary: OpenMP and Cilk Plus SIMD pragma makes loop incorrect Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: evstupac at gmail dot com GCC generates incorrect code for the SIMD loop (#pragma [omp] simd) with function call that have pointer parameters. (test case attached) gcc test.c foo.c -fcilkplus -O3 ./a.out ; echo $? 1 gcc test.c foo.c -fcilkplus -O0 ./a.out ; echo $? 0 the same for -fopenmp -DENABLE_OMP instead of -fcilkplus Moreover g++ crashes on the test: g++ test.c -fcilkplus -O3 -c test.c: In function 'int main()': test.c:10:5: error: dead STMT in EH table int main() ^ # .MEM_11 = VDEF <.MEM_39> foo (_10, &v1, &v2); test.c:10:5: internal compiler error: verify_gimple failed 0xb774b3 verify_gimple_in_cfg(function*) /export/users/mstester/stability/svn/trunk/gcc/tree-cfg.c:4853 0xa9fc52 execute_function_todo /export/users/mstester/stability/svn/trunk/gcc/passes.c:1853 0xaa05a3 execute_todo /export/users/mstester/stability/svn/trunk/gcc/passes.c:1887 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <http://gcc.gnu.org/bugs.html> for instructions.
next reply other threads:[~2014-01-29 14:41 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-29 14:41 evstupac at gmail dot com [this message] 2014-01-29 14:42 ` [Bug c/59984] " evstupac at gmail dot com 2014-02-05 18:42 ` mpolacek at gcc dot gnu.org 2014-02-06 12:59 ` izamyatin at gmail dot com 2014-02-06 16:11 ` jakub at gcc dot gnu.org 2014-02-07 14:34 ` jakub at gcc dot gnu.org 2014-02-07 15:20 ` jakub at gcc dot gnu.org 2014-02-08 9:10 ` jakub at gcc dot gnu.org 2014-02-08 9:29 ` jakub at gcc dot gnu.org 2014-02-08 9:30 ` jakub at gcc dot gnu.org 2014-04-22 11:38 ` jakub at gcc dot gnu.org 2014-07-16 13:31 ` jakub at gcc dot gnu.org 2014-10-30 10:43 ` jakub at gcc dot gnu.org 2014-11-13 23:51 ` evstupac at gmail dot com 2014-11-14 15:04 ` jakub at gcc dot gnu.org 2014-11-17 9:03 ` rguenther at suse dot de 2014-11-17 14:58 ` rguenth at gcc dot gnu.org 2015-06-26 20:13 ` jakub at gcc dot gnu.org 2015-06-26 20:36 ` jakub at gcc dot gnu.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-59984-4@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).