public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.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 [thread overview] Message-ID: <bug-30928-4717-LyUih4vDHl@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30928-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30928 --- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> --- Bisects to: ... $ git bisect bad 5cc007751cdb8ea713c98294e37cd447c12c9bab is the first bad commit commit 5cc007751cdb8ea713c98294e37cd447c12c9bab Author: Jan Beulich <jbeulich@suse.com> 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). ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-10-01 11:00 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-01 10:14 [Bug testsuite/30928] New: " vries at gcc dot gnu.org 2023-10-01 11:00 ` vries at gcc dot gnu.org [this message] 2023-10-01 11:15 ` [Bug testsuite/30928] " vries at gcc dot gnu.org 2023-10-03 20:50 ` vries at gcc dot gnu.org 2023-10-07 8:33 ` cvs-commit at gcc dot gnu.org 2023-10-07 8:38 ` vries at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-30928-4717-LyUih4vDHl@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).