From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D2450389FC20; Wed, 22 Jul 2020 07:53:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D2450389FC20 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1595404397; bh=g3dCIr1tnolirbuKjADrmmV41FIuRv/6+g7bVvo2ufo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=OBTwsSe2gVx8Xr0RaUoFGZBzSpNRMBw5LXIoG20MUKYKo7y7cC/6ofnUE1zBc/G2i 2oTN4xqDPfZ2krCdj+Zhhimvfbb3bZrzaHA6qGU3Mbu1dO2sf10wYuMVPsm6zM3SB/ ltmAznjatF0Uvy1rhCViaJluBkus/I/I3HdmRFBI= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/96270] [8/9/10/11 Regression] stdarg malfunction with -m32 and -Os Date: Wed, 22 Jul 2020 07:53:17 +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: 9.3.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.5 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to priority bug_status 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 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: Wed, 22 Jul 2020 07:53:17 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96270 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot = gnu.org Priority|P3 |P2 Status|NEW |ASSIGNED --- Comment #3 from Richard Biener --- I think we have some duplicates about this PRE issue but I also thought this specific one is already mitigated by 1dc00a8ec9aeba86b74b16bff6f171824bb7b4= a1 Now here code hoisting comes into play and with the other outstanding PRE issues the issue is it operates based on values thus we do not actually know the expression we operate on and VN value-numbers u.r the same as u.i.=