public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/54406] random_number() sometimes returns duplicate values when called from parallel threads Date: Wed, 29 Aug 2012 13:16:00 -0000 [thread overview] Message-ID: <bug-54406-4-ZWzsa3JOQn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54406-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54406 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-08-29 13:16:36 UTC --- How about replacing !$OMP parallel do schedule(dynamic) by !$OMP parallel do schedule(dynamic) private(r)
next prev parent reply other threads:[~2012-08-29 13:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-29 12:36 [Bug fortran/54406] New: " bugzilla.tmschr at wronghead dot com 2012-08-29 12:40 ` [Bug fortran/54406] " bugzilla.tmschr at wronghead dot com 2012-08-29 13:16 ` burnus at gcc dot gnu.org [this message] 2012-08-29 13:56 ` bugzilla.tmschr at wronghead dot com 2012-08-29 14:20 ` burnus 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-54406-4-ZWzsa3JOQn@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).