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 middle-end/104088] New: [12 Regression] '-O2' (or higher) GCN offloading (only) 'libgomp.oacc-c-c++-common/vprop.c' excess errors: 'warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]'
Date: Tue, 18 Jan 2022 10:24:43 +0000 [thread overview]
Message-ID: <bug-104088-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104088
Bug ID: 104088
Summary: [12 Regression] '-O2' (or higher) GCN offloading
(only) 'libgomp.oacc-c-c++-common/vprop.c' excess
errors: 'warning: writing 1 byte into a region of size
0 [-Wstringop-overflow=]'
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: diagnostic, openacc
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: tschwinge at gcc dot gnu.org
CC: ams at gcc dot gnu.org, jules at gcc dot gnu.org, msebor at gcc dot gnu.org
Target Milestone: ---
Target: gcn
The recent commit r12-6592-g72332337e3d8acbb21398b8d123f1bfe77a8327e "Use
enclosing object size if it's smaller than member [PR 101475]" causes a
regression with '-O2' (or higher) GCN offloading (only):
PASS: libgomp.oacc-c/../libgomp.oacc-c-c++-common/vprop.c
-DACC_DEVICE_TYPE_radeon=1 -DACC_MEM_SHARED=0 -foffload=amdgcn-amdhsa -O0
(test for excess errors)
PASS: libgomp.oacc-c/../libgomp.oacc-c-c++-common/vprop.c
-DACC_DEVICE_TYPE_radeon=1 -DACC_MEM_SHARED=0 -foffload=amdgcn-amdhsa -O0
execution test
[-PASS:-]{+FAIL:+} libgomp.oacc-c/../libgomp.oacc-c-c++-common/vprop.c
-DACC_DEVICE_TYPE_radeon=1 -DACC_MEM_SHARED=0 -foffload=amdgcn-amdhsa -O2
(test for excess errors)
PASS: libgomp.oacc-c/../libgomp.oacc-c-c++-common/vprop.c
-DACC_DEVICE_TYPE_radeon=1 -DACC_MEM_SHARED=0 -foffload=amdgcn-amdhsa -O2
execution test
In function 'test_char._omp_fn.0':
lto1: warning: writing 1 byte into a region of size 0
[-Wstringop-overflow=]
lto1: warning: writing 1 byte into a region of size 0
[-Wstringop-overflow=]
PASS: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/vprop.c
-DACC_DEVICE_TYPE_radeon=1 -DACC_MEM_SHARED=0 -foffload=amdgcn-amdhsa -O0
(test for excess errors)
PASS: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/vprop.c
-DACC_DEVICE_TYPE_radeon=1 -DACC_MEM_SHARED=0 -foffload=amdgcn-amdhsa -O0
execution test
[-PASS:-]{+FAIL:+} libgomp.oacc-c++/../libgomp.oacc-c-c++-common/vprop.c
-DACC_DEVICE_TYPE_radeon=1 -DACC_MEM_SHARED=0 -foffload=amdgcn-amdhsa -O2
(test for excess errors)
PASS: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/vprop.c
-DACC_DEVICE_TYPE_radeon=1 -DACC_MEM_SHARED=0 -foffload=amdgcn-amdhsa -O2
execution test
In function '_Z9test_charv._omp_fn.0':
lto1: warning: writing 1 byte into a region of size 0
[-Wstringop-overflow=]
lto1: warning: writing 1 byte into a region of size 0
[-Wstringop-overflow=]
There is no (!) meaningful difference if good vs. bad
'-foffload=amdgcn-amdhsa=-fdump-tree-all\ -fdump-ipa-all\ -fdump-rtl-all' dump
files.
I'm happy to supply any dump files etc. to help resolve this.
next reply other threads:[~2022-01-18 10:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 10:24 tschwinge at gcc dot gnu.org [this message]
2022-01-18 11:12 ` [Bug middle-end/104088] " rguenth at gcc dot gnu.org
2022-03-21 15:54 ` tschwinge at gcc dot gnu.org
2022-05-06 8:32 ` [Bug middle-end/104088] [12/13 " jakub at gcc dot gnu.org
2022-10-19 9:48 ` rguenth at gcc dot gnu.org
2022-11-21 13:18 ` burnus at gcc dot gnu.org
2023-05-08 12:23 ` [Bug middle-end/104088] [12/13/14 " rguenth at gcc dot gnu.org
2024-03-22 14:06 ` law 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-104088-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: link
Be 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).