From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 5F7183858D37; Sat,  7 Oct 2023 08:33:46 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5F7183858D37
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1696667626;
	bh=kOf4jD3CpP5RkmLBeah/4KEJ/DjWuiLBdWTzMeeKBVQ=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=QlXHbbIP8koE0os3awg5mhKVh6Z50ljLe8txud8dWEDY1rr4e3IfUYZlIBLVUgvZG
	 +XOVEXF+vcyBrBwtjHy7UNdoICQbrKHKXohDM2zFjgwYVcSQTa7wqbSQEyyVQn1qBO
	 d9Rx+qAnEJfa+VjwBs9wEIEZ+DPmRrAqsZgT8s2c=
From: "cvs-commit 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: Sat, 07 Oct 2023 08:33:38 +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: cvs-commit 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: <bug-30928-4717-nEcJpjICa4@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-30928-4717@http.sourceware.org/bugzilla/>
References: <bug-30928-4717@http.sourceware.org/bugzilla/>
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: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D30928

--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gn=
u.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D6542e3df2065=
2b96851c9f801ce199e3072792cf

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=3Dnever -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 =3D=3D 1), and
    - unix/-m32 (is_amd64_regs_target =3D=3D 0),

    PR testsuite/30928
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30928

--=20
You are receiving this mail because:
You are on the CC list for the bug.=