From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 531CD3856DEA; Sun, 1 Oct 2023 11:00:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 531CD3856DEA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1696158004; bh=GkxSB7oJTvnuJHWvhatsiuiTq/i8d2DlR97XV6p8khc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Kn7vfxfwrXClL7PYQe1DL0ccPTU/9Fa0A81bnBsI+zVTIFglyOME4G1XmseWo92T+ kZJabn0XwlNjYLYNr547fjsXN4azP70TNuTHGiOBFLwQyQebMCdXD5Vl45Z9e2vopK lBkTdtUxntiQdSNw5K437i85D7qmZPf9CqWYpOWg= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/30928] [gdb/testsuite] Compilation failure for gdb.arch/i386-signal.exp Date: Sun, 01 Oct 2023 11:00:02 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot 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://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30928 --- Comment #1 from Tom de Vries --- Bisects to: ... $ git bisect bad 5cc007751cdb8ea713c98294e37cd447c12c9bab is the first bad commit commit 5cc007751cdb8ea713c98294e37cd447c12c9bab Author: Jan Beulich Date: Fri May 19 09:18:09 2023 +0200 x86: further adjust extend-to-32bit-address conditions While a442cac5084e ("ix86: wrap constants") helped address a number of inconsistencies between BFD64 and !BFD64 builds, it has also resulted in certain bogus uses of constants to no longer be warned about. Leverage the md_optimize_expr() hook to adjust when to actually truncate expressions to 32 bits - any involvement of binary expressions (which would be evaluated in 32 bits only when !BFD64) signals the need for doing so. Plain constants (or ones merely subject to unary operators) should remain un-truncated - they would be handled as bignums when !BFD64, and hence are okay to permit. To compensate - slightly extend optimize_imm() (to be honest I never understood why the code being added - or something similar - wasn't there in the first place), - adjust expectations of the disp-imm-32 testcase (there are now warnings, as there should be for any code which won't build [warning- free] when !BFD64, and Disp8/Imm8 are no longer used in the warned about cases). ... --=20 You are receiving this mail because: You are on the CC list for the bug.=