public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/95062] New: [10/11 Regression] libgomp.oacc-c-c++-common/pr92843-1.c:26: verify_array: Assertion `array[i] == value' failed Date: Mon, 11 May 2020 16:32:21 +0000 [thread overview] Message-ID: <bug-95062-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95062 Bug ID: 95062 Summary: [10/11 Regression] libgomp.oacc-c-c++-common/pr92843-1.c:26: verify_array: Assertion `array[i] == value' failed Product: gcc Version: 10.0 Status: UNCONFIRMED Keywords: openacc Severity: normal Priority: P3 Component: libgomp Assignee: unassigned at gcc dot gnu.org Reporter: tschwinge at gcc dot gnu.org CC: jakub at gcc dot gnu.org, jules at gcc dot gnu.org Target Milestone: --- As made apparent by the 'dg-xfail-run-if' added, r279621 "OpenACC reference count overhaul" regressed the 'libgomp.oacc-c-c++-common/pr92843-1.c' test case: pr92843-1.exe: [...]/libgomp.oacc-c-c++-common/pr92843-1.c:26: verify_array: Assertion `array[i] == value' failed. There are patches to cure this: <http://mid.mail-archive.com/666bd70af1514e8a3d80fa9ad1ef114bbc2b3a80.1579292772.git.julian@codesourcery.com> "Introduce dynamic data mapping sentinel for OpenACC", <http://mid.mail-archive.com/4bbb4970cd48424873573a50e627786cc9cf3378.1579292772.git.julian@codesourcery.com" "Don't copy back vars mapped with acc_map_data", but these have issues on their own (cause other regressions).
next reply other threads:[~2020-05-11 16:32 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-11 16:32 tschwinge at gcc dot gnu.org [this message] 2020-05-12 6:56 ` [Bug libgomp/95062] " rguenth at gcc dot gnu.org 2020-07-15 12:57 ` tschwinge 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-95062-4@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).