public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/100232] [OpenMP][nvptx] Reduction fails with optimization and 'loop'/'for simd' but not with 'for' Date: Thu, 29 Apr 2021 09:08:52 +0000 [thread overview] Message-ID: <bug-100232-4-OUQCEW0fyb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100232-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100232 Tom de Vries <vries at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Target Milestone|--- |11.2 Resolution|--- |FIXED --- Comment #8 from Tom de Vries <vries at gcc dot gnu.org> --- I tried backporting to releases/gcc-10, but ran into: ... FAIL: libgomp.c/target-43.c (test for excess errors) Excess errors: unresolved symbol __sync_val_compare_and_swap_1 mkoffload: fatal error: /home/vries/oacc/trunk/install/offload-nvptx-none/bin//x86_64-pc-linux-gnu-accel-nvptx-none-gcc returned 1 exit status compilation terminated. ... So I guess backporting stops at gcc-11.
prev parent reply other threads:[~2021-04-29 9:08 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-23 13:20 [Bug target/100232] New: " burnus at gcc dot gnu.org 2021-04-23 14:19 ` [Bug target/100232] " vries at gcc dot gnu.org 2021-04-23 15:27 ` burnus at gcc dot gnu.org 2021-04-28 12:51 ` vries at gcc dot gnu.org 2021-04-28 13:03 ` vries at gcc dot gnu.org 2021-04-28 14:31 ` vries at gcc dot gnu.org 2021-04-29 7:55 ` cvs-commit at gcc dot gnu.org 2021-04-29 8:40 ` cvs-commit at gcc dot gnu.org 2021-04-29 9:08 ` vries at gcc dot gnu.org [this message]
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-100232-4-OUQCEW0fyb@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).