From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 57A153858020; Tue, 18 Jan 2022 10:24:43 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 57A153858020 From: "tschwinge at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: diagnostic, openacc X-Bugzilla-Severity: normal X-Bugzilla-Who: tschwinge at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone cf_gcctarget Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2022 10:24:43 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D104088 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=3D]' 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, msebo= r 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=3D1 -DACC_MEM_SHARED=3D0 -foffload=3Damdgcn-amdhsa= -O0=20 (test for excess errors) PASS: libgomp.oacc-c/../libgomp.oacc-c-c++-common/vprop.c -DACC_DEVICE_TYPE_radeon=3D1 -DACC_MEM_SHARED=3D0 -foffload=3Damdgcn-amdhsa= -O0=20 execution test [-PASS:-]{+FAIL:+} libgomp.oacc-c/../libgomp.oacc-c-c++-common/vprop.c -DACC_DEVICE_TYPE_radeon=3D1 -DACC_MEM_SHARED=3D0 -foffload=3Damdgcn-amdhsa= -O2=20 (test for excess errors) PASS: libgomp.oacc-c/../libgomp.oacc-c-c++-common/vprop.c -DACC_DEVICE_TYPE_radeon=3D1 -DACC_MEM_SHARED=3D0 -foffload=3Damdgcn-amdhsa= -O2=20 execution test In function 'test_char._omp_fn.0': lto1: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=3D] lto1: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=3D] PASS: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/vprop.c -DACC_DEVICE_TYPE_radeon=3D1 -DACC_MEM_SHARED=3D0 -foffload=3Damdgcn-amdhsa= -O0=20 (test for excess errors) PASS: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/vprop.c -DACC_DEVICE_TYPE_radeon=3D1 -DACC_MEM_SHARED=3D0 -foffload=3Damdgcn-amdhsa= -O0=20 execution test [-PASS:-]{+FAIL:+} libgomp.oacc-c++/../libgomp.oacc-c-c++-common/vprop.c -DACC_DEVICE_TYPE_radeon=3D1 -DACC_MEM_SHARED=3D0 -foffload=3Damdgcn-amdhsa= -O2=20 (test for excess errors) PASS: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/vprop.c -DACC_DEVICE_TYPE_radeon=3D1 -DACC_MEM_SHARED=3D0 -foffload=3Damdgcn-amdhsa= -O2=20 execution test In function '_Z9test_charv._omp_fn.0': lto1: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=3D] lto1: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=3D] There is no (!) meaningful difference if good vs. bad '-foffload=3Damdgcn-amdhsa=3D-fdump-tree-all\ -fdump-ipa-all\ -fdump-rtl-al= l' dump files. I'm happy to supply any dump files etc. to help resolve this.=