public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug testsuite/30928] New: [gdb/testsuite] Compilation failure for gdb.arch/i386-signal.exp
@ 2023-10-01 10:14 vries at gcc dot gnu.org
2023-10-01 11:00 ` [Bug testsuite/30928] " vries at gcc dot gnu.org
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: vries at gcc dot gnu.org @ 2023-10-01 10:14 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30928
Bug ID: 30928
Summary: [gdb/testsuite] Compilation failure for
gdb.arch/i386-signal.exp
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
With test-case gdb.arch/i386-signal.exp I run into:
...
builtin_spawn -ignore SIGHUP gcc -fno-stack-protector
/data/vries/gdb/src/gdb/testsuite/gdb.arch/i386-signal.c
-fdiagnostics-color=never -fno-pie -g -no-pie -lm -o
/data/vries/gdb/leap-15-4/build/gdb/testsuite/outputs/gdb.arch/i386-signal/i386-signal^M
/tmp/cc2xydTG.s: Assembler messages:^M
/tmp/cc2xydTG.s:50: Error: operand size mismatch for `push'^M
compiler exited with status 1
output is:
/tmp/cc2xydTG.s: Assembler messages:^M
/tmp/cc2xydTG.s:50: Error: operand size mismatch for `push'^M
gdb compile failed, /tmp/cc2xydTG.s: Assembler messages:
/tmp/cc2xydTG.s:50: Error: operand size mismatch for `push'
UNTESTED: gdb.arch/i386-signal.exp: failed to compile
...
This with gas 2.41. With gas 2.40 it compiles.
The test-case also compiles with target board unix/-m32.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug testsuite/30928] [gdb/testsuite] Compilation failure for gdb.arch/i386-signal.exp
2023-10-01 10:14 [Bug testsuite/30928] New: [gdb/testsuite] Compilation failure for gdb.arch/i386-signal.exp vries at gcc dot gnu.org
@ 2023-10-01 11:00 ` vries at gcc dot gnu.org
2023-10-01 11:15 ` vries at gcc dot gnu.org
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: vries at gcc dot gnu.org @ 2023-10-01 11:00 UTC (permalink / raw)
To: gdb-prs
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug testsuite/30928] [gdb/testsuite] Compilation failure for gdb.arch/i386-signal.exp
2023-10-01 10:14 [Bug testsuite/30928] New: [gdb/testsuite] Compilation failure for gdb.arch/i386-signal.exp vries at gcc dot gnu.org
2023-10-01 11:00 ` [Bug testsuite/30928] " vries at gcc dot gnu.org
@ 2023-10-01 11:15 ` vries at gcc dot gnu.org
2023-10-03 20:50 ` vries at gcc dot gnu.org
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: vries at gcc dot gnu.org @ 2023-10-01 11:15 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30928
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
https://sourceware.org/pipermail/gdb-patches/2023-October/202875.html
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug testsuite/30928] [gdb/testsuite] Compilation failure for gdb.arch/i386-signal.exp
2023-10-01 10:14 [Bug testsuite/30928] New: [gdb/testsuite] Compilation failure for gdb.arch/i386-signal.exp vries at gcc dot gnu.org
2023-10-01 11:00 ` [Bug testsuite/30928] " vries at gcc dot gnu.org
2023-10-01 11:15 ` 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
4 siblings, 0 replies; 6+ messages in thread
From: vries at gcc dot gnu.org @ 2023-10-03 20:50 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30928
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
Might also be a gas regression:
https://sourceware.org/pipermail/binutils/2023-October/129818.html
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug testsuite/30928] [gdb/testsuite] Compilation failure for gdb.arch/i386-signal.exp
2023-10-01 10:14 [Bug testsuite/30928] New: [gdb/testsuite] Compilation failure for gdb.arch/i386-signal.exp vries at gcc dot gnu.org
` (2 preceding siblings ...)
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
4 siblings, 0 replies; 6+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2023-10-07 8:33 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30928
--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6542e3df20652b96851c9f801ce199e3072792cf
commit 6542e3df20652b96851c9f801ce199e3072792cf
Author: Tom de Vries <tdevries@suse.de>
Date: Sat Oct 7 10:33:29 2023 +0200
[gdb/testsuite] Fix gdb.arch/i386-signal.exp on x86_64
On x86_64-linux, with test-case gdb.arch/i386-signal.exp I run into:
...
builtin_spawn -ignore SIGHUP gcc -fno-stack-protector i386-signal.c \
-fdiagnostics-color=never -fno-pie -g -no-pie -lm -o i386-signal^M
/tmp/cc2xydTG.s: Assembler messages:^M
/tmp/cc2xydTG.s:50: Error: operand size mismatch for `push'^M
compiler exited with status 1
output is:
/tmp/cc2xydTG.s: Assembler messages:^M
/tmp/cc2xydTG.s:50: Error: operand size mismatch for `push'^M
gdb compile failed, /tmp/cc2xydTG.s: Assembler messages:
/tmp/cc2xydTG.s:50: Error: operand size mismatch for `push'
UNTESTED: gdb.arch/i386-signal.exp: failed to compile
...
This is with gas 2.41, it compiles without problems with gas 2.40. Some
more
strict checking was added in commit 5cc007751cd ("x86: further adjust
extend-to-32bit-address conditions"). This may or may not be a gas
regression
( https://sourceware.org/pipermail/binutils/2023-October/129818.html ).
The offending bit is:
...
" push $sigframe\n"
...
which refers to a function:
...
" .globl sigframe\n"
"sigframe:\n"
...
The test-case passes with target board unix/-m32.
Make the test-case work by using pushq instead of push for the
is_amd64_regs_target case.
Tested on x86_64-linux, with target boards:
- unix/-m64 (is_amd64_regs_target == 1), and
- unix/-m32 (is_amd64_regs_target == 0),
PR testsuite/30928
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30928
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug testsuite/30928] [gdb/testsuite] Compilation failure for gdb.arch/i386-signal.exp
2023-10-01 10:14 [Bug testsuite/30928] New: [gdb/testsuite] Compilation failure for gdb.arch/i386-signal.exp vries at gcc dot gnu.org
` (3 preceding siblings ...)
2023-10-07 8:33 ` cvs-commit at gcc dot gnu.org
@ 2023-10-07 8:38 ` vries at gcc dot gnu.org
4 siblings, 0 replies; 6+ messages in thread
From: vries at gcc dot gnu.org @ 2023-10-07 8:38 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30928
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Target Milestone|--- |14.1
Status|NEW |RESOLVED
--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
Fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2023-10-07 8:38 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-10-01 10:14 [Bug testsuite/30928] New: [gdb/testsuite] Compilation failure for gdb.arch/i386-signal.exp vries at gcc dot gnu.org
2023-10-01 11:00 ` [Bug testsuite/30928] " vries at gcc dot gnu.org
2023-10-01 11:15 ` 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
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).