public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/115140] New: [15 regression] libgomp.oacc-c++/../libgomp.oacc-c-c++-common/acc_prof-kernels-1.c excess errors after r15-579-ga9251ab3c91c8c Date: Fri, 17 May 2024 15:26:00 +0000 [thread overview] Message-ID: <bug-115140-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115140 Bug ID: 115140 Summary: [15 regression] libgomp.oacc-c++/../libgomp.oacc-c-c++-common/acc_prof -kernels-1.c excess errors after r15-579-ga9251ab3c91c8c Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- g:a9251ab3c91c8c559d0306838575a666ae62dff4, r15-579-ga9251ab3c91c8c: 1130 failures FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/acc_prof-kernels-1.c -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 -foffload=disable -O2 at line 190 (test for warnings, line 185) FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/acc_prof-kernels-1.c -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 -foffload=disable -O2 at line 221 (test for warnings, line 214) FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/acc_prof-kernels-1.c -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 -foffload=disable -O2 at line 252 (test for warnings, line 245) FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/acc_prof-kernels-1.c -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 -foffload=disable -O2 (test for excess errors) FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/acc_prof-kernels-1.c -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 -foffload=disable -O2 at line 190 (test for warnings, line 185) FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/acc_prof-kernels-1.c -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 -foffload=disable -O2 at line 221 (test for warnings, line 214) FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/acc_prof-kernels-1.c -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 -foffload=disable -O2 at line 252 (test for warnings, line 245) FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/acc_prof-kernels-1.c -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 -foffload=disable -O2 (test for excess errors) commit a9251ab3c91c8c559d0306838575a666ae62dff4 (HEAD) Author: Richard Biener <rguenther@suse.de> Date: Thu May 16 12:35:28 2024 +0200 wrong code with points-to and volatile Excess errors: /home/seurer/gcc/git/gcc-test2/libgomp/testsuite/libgomp.oacc-c/../libgomp.oacc-c-c++-common/acc_prof-kernels-1.c:185:9: optimized: assigned OpenACC seq loop parallelism /home/seurer/gcc/git/gcc-test2/libgomp/testsuite/libgomp.oacc-c/../libgomp.oacc-c-c++-common/acc_prof-kernels-1.c:214:9: optimized: assigned OpenACC seq loop parallelism /home/seurer/gcc/git/gcc-test2/libgomp/testsuite/libgomp.oacc-c/../libgomp.oacc-c-c++-common/acc_prof-kernels-1.c:245:9: optimized: assigned OpenACC seq loop parallelism
next reply other threads:[~2024-05-17 15:26 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-17 15:26 seurer at gcc dot gnu.org [this message] 2024-05-18 19:36 ` [Bug other/115140] " pinskia at gcc dot gnu.org 2024-05-21 6:30 ` [Bug testsuite/115140] " rguenth at gcc dot gnu.org 2024-05-22 11:50 ` ro at gcc dot gnu.org 2024-05-24 6:39 ` 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-115140-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).