From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 781D33858D35; Mon, 11 Oct 2021 17:12:34 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 781D33858D35 From: "davidhaufegcc at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/102649] GCC 9.3.1 LTO bug -- incorrect function call, bad stack arguments pushed Date: Mon, 11 Oct 2021 17:12:34 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: lto X-Bugzilla-Version: 9.3.1 X-Bugzilla-Keywords: lto, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: davidhaufegcc at gmail dot com X-Bugzilla-Status: WAITING 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: 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: Mon, 11 Oct 2021 17:12:34 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D102649 --- Comment #2 from David Haufe --- I had assumed this would be the response. Unfortunately the source code involved is both large (1000+ object files in this build) and proprietary. = The behavior we see where if we roll forward GIT and rebuild, and unrelated cha= nges "fix" the problem, makes it seem futile to develop an isolated test case.=20 I can provide the assembly for the functions that highlight the error if th= at would be beneficial? Not sure how helpful that would be though. Are there a= ny other best practices in a case like this one?=