public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alexander.grund at mailbox dot tu-dresden.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/62010] OpenMP simd produces wrong results
Date: Mon, 04 Aug 2014 13:34:00 -0000	[thread overview]
Message-ID: <bug-62010-4-LMFLOOYvDn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62010-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62010

--- Comment #2 from Alexander Grund <alexander.grund at mailbox dot tu-dresden.de> ---
Related to this: In some cases OpenMP simd crashes while that crash is fixed by
removing an unrelated piece of code. See Testcase 2.

Run with:
 gfortran-4.9 gfortranBug.f -cpp && ./a.out && gfortran-4.9 gfortranBug.f -cpp
-fopenmp && ./a.out

Output:
 size          12 x          10 x           5
  -29032800293.326649     
 size          12 x          10 x           5
   3554.0040000000376 

Expected: Same output

And to crash run with:
gfortran-4.9 gfortranBug.f -cpp -D CRASH && ./a.out && gfortran-4.9
gfortranBug.f -cpp -D CRASH -fopenmp && ./a.out

Output:
 size          12 x          10 x           5
   3840.3482323232652     
 size          12 x          10 x           5

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.


  reply	other threads:[~2014-08-04 13:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04 13:29 [Bug fortran/62010] New: " alexander.grund at mailbox dot tu-dresden.de
2014-08-04 13:34 ` alexander.grund at mailbox dot tu-dresden.de [this message]
2014-08-04 16:38 ` [Bug fortran/62010] " jakub at gcc dot gnu.org
2014-08-04 16:48 ` alexander.grund at mailbox dot tu-dresden.de

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-62010-4-LMFLOOYvDn@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: link
Be 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).