From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5F0B538AA275; Mon, 5 Dec 2022 16:36:30 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5F0B538AA275 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1670258190; bh=slq0h3KjjHct8/AEhoEDfJ9JpjEpkkSl7sNz/bMVH9c=; h=From:To:Subject:Date:In-Reply-To:References:From; b=T/tQ6opc7kmDMtmdOtl1hI78f/9ySF1682ojgzja6hH2k6QYvaaDLlR7AVKueT3Mp Q3Dd3F9jUKrD71M5gt8MY3IjITfWlpdT3SBWLtufhiygNoUPch4MIbvGEta+7sXxSS aCEW+XP3+I3WhDSnotRAQoaW6kHTg2SmUBA7z7GQ= From: "thiago at kde dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/104475] [12/13 Regression] Wstringop-overflow + atomics incorrect warning on dynamic object Date: Mon, 05 Dec 2022 16:36:29 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: diagnostic, missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: thiago at kde dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 12.3 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D104475 --- Comment #14 from Thiago Macieira --- Created attachment 54015 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D54015&action=3Dedit qfutureinterface.cpp preprocessed [gcc trunk-20221205] (In reply to Richard Biener from comment #13) > There's been some changes on trunk but the preprocessed source doesn't wo= rk > there. Uploaded the updated preprocessed source with current trunk, from roughly t= he same Qt commit (I chose a date just before this bug report was opened). I can still reproduce this issue with the minimal original sources and these preprocessed, but somehow not with the actual qfutureinterface.cpp, either = then or now.=