From: Jan Beulich <jbeulich@suse.com>
To: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] x86: drop redundant x86-64-code16-2 test
Date: Fri, 4 Mar 2022 13:39:57 +0100 [thread overview]
Message-ID: <5b9bda44-f879-7edc-718d-cf87eb1c36cc@suse.com> (raw)
In-Reply-To: <3fb7d1a3-dc40-d538-55ba-7c477521c9b5@suse.com>
On 25.02.2022 14:26, Jan Beulich via Binutils wrote:
> The code16-2 test is already meaningless enough as a gas test, identical
> to this one, and is run uniformly for all ELF targets anyway.
In the absence of any feedback I've committed this as obvious (enough).
Jan
> --- a/gas/testsuite/gas/i386/i386.exp
> +++ b/gas/testsuite/gas/i386/i386.exp
> @@ -1331,7 +1331,6 @@ if [gas_64_check] then {
> run_dump_test "x86-64-property-8"
> run_dump_test "x86-64-property-9"
> run_dump_test "x86-64-property-14"
> - run_dump_test "x86-64-code16-2"
>
> if {[istarget "*-*-linux*"]} then {
> run_dump_test "x86-64-align-branch-3"
> --- a/gas/testsuite/gas/i386/x86-64-code16-2.d
> +++ /dev/null
> @@ -1,4 +0,0 @@
> -#source: code16-2.s
> -#name: x86-64 code16 2
> -#as: -mx86-used-note=no --generate-missing-build-notes=no
> -#readelf: -n
>
prev parent reply other threads:[~2022-03-04 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 13:26 Jan Beulich
2022-03-04 12:39 ` Jan Beulich [this message]
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=5b9bda44-f879-7edc-718d-cf87eb1c36cc@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@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: link
Be 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).