public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chinoune.mehdi at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/95150] Some offloaded programs crash with openmp Date: Fri, 15 May 2020 15:49:01 +0000 [thread overview] Message-ID: <bug-95150-4-L3xLJJxoHG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95150-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95150 --- Comment #3 from Chinoune <chinoune.mehdi at hotmail dot com> --- (In reply to Tobias Burnus from comment #1) > * You compilation uses "-O0" – I do not know whether that's intended. I didn't set any optimization flag, maybe the compiler default to "-O0". > > * I did not see any timeout message although it did take a while to run > with offloading. (See timing results below.) > I wonder what causes the problem you are seeing. > > You could try whether setting the environment variable > GOMP_DEBUG=1 > shows some useful details for the launch. > I have attached the output with GOMP_DEBUG=1 > * The OpenACC test case is wrong as "c" has to be "copy" not "copyout" > as the initial value is used (→ NaN) Thanks, I did observe after I reported the bug. I am using a Kepler (sm_35) Graphics card, if this helps.
next prev parent reply other threads:[~2020-05-15 15:49 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-15 11:36 [Bug libgomp/95150] New: " chinoune.mehdi at hotmail dot com 2020-05-15 14:10 ` [Bug libgomp/95150] " burnus at gcc dot gnu.org 2020-05-15 15:42 ` chinoune.mehdi at hotmail dot com 2020-05-15 15:49 ` chinoune.mehdi at hotmail dot com [this message] 2020-05-21 7:12 ` chinoune.mehdi at hotmail dot com 2020-10-30 9:32 ` mehdi.chinoune at hotmail dot com 2020-12-12 20:03 ` mehdi.chinoune at hotmail dot com 2020-12-13 3:33 ` mehdi.chinoune at hotmail dot com 2020-12-13 4:21 ` mehdi.chinoune at hotmail dot com 2020-12-19 12:18 ` mehdi.chinoune at hotmail dot com 2021-07-28 8:26 ` mehdi.chinoune at hotmail dot com
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-95150-4-L3xLJJxoHG@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).