public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/37938] libgomp testsuite failures on ia64-linux Date: Tue, 28 Oct 2008 15:04:00 -0000 [thread overview] Message-ID: <20081028150236.5051.qmail@sourceware.org> (raw) In-Reply-To: <bug-37938-87@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from jakub at gcc dot gnu dot org 2008-10-28 15:02 ------- BTW, using + reduction in the same loop (and with asm optimization barrier for that variable) I see the reduction computed value always correct, so the loop body is executed the correct number of times. That means in some cases the memory reads/writes between GOMP_atomic_{start,end} must overlap between threads. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37938
next prev parent reply other threads:[~2008-10-28 15:04 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-28 14:41 [Bug libgomp/37938] New: " jakub at gcc dot gnu dot org 2008-10-28 15:04 ` jakub at gcc dot gnu dot org [this message] 2008-10-31 20:05 ` [Bug libgomp/37938] " sje at cup dot hp dot com 2008-10-31 20:16 ` jakub at gcc dot gnu dot org 2008-10-31 23:31 ` hjl dot tools at gmail dot com 2008-11-04 16:55 ` sje at cup dot hp dot com 2008-11-13 21:09 ` sje at gcc dot gnu dot org 2008-11-13 21:14 ` 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=20081028150236.5051.qmail@sourceware.org \ --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).