public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>
Cc: binutils@sourceware.org, Cary Coutant <ccoutant@gmail.com>
Subject: Re: [PATCH] gas: Fix a testcase broken by new ZSTD support
Date: Fri, 5 Aug 2022 09:29:55 +0200	[thread overview]
Message-ID: <27d2627d-363b-8b7c-cd7b-3c3ea6818714@suse.com> (raw)
In-Reply-To: <88262e9dfc11097d08b552171f1af2e8e026f554.1659683506.git.research_trasio@irq.a4lg.com>

On 05.08.2022 09:12, Tsukasa OI wrote:
> The commit 1369522f36eece1b37139a81f7f2139ba3915172 ("Recognize the new ELF
> compression type for ZSTD.") added the new ELF compression type but it
> accidentally broke a GAS testcase.  Since 2 is now a valid compression type
> ELFCOMPRESS_ZSTD, the ".word 2" line in section10.s which expects an
> **unknown** compression type needs to be changed to another unknown value.
> 
> gas/ChangeLog:
> 
> 	* testsuite/gas/elf/section10.s: Use unknown ELF compression type.
> ---
>  gas/testsuite/gas/elf/section10.s | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/gas/testsuite/gas/elf/section10.s b/gas/testsuite/gas/elf/section10.s
> index d52b3458fb1..6a252fb6334 100644
> --- a/gas/testsuite/gas/elf/section10.s
> +++ b/gas/testsuite/gas/elf/section10.s
> @@ -4,7 +4,7 @@
>  
>  	# Make sure that a numeric value can be mixed with alpha values.
>  	.section sec2, "a2048x"
> -	.word 2
> +	.word 9

Hmm, in N years time this will become an issue again. Since it's not
really connected to the purpose of the test, would it make sense to
instead simply drop that one line from section10.d?

Jan

  reply	other threads:[~2022-08-05  7:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05  7:12 Tsukasa OI
2022-08-05  7:29 ` Jan Beulich [this message]
2022-08-05  7:45   ` Tsukasa OI
2022-08-05  7:45 ` [PATCH v2] " Tsukasa OI
2022-08-05  8:24   ` Jan Beulich
2022-08-05  8:54     ` Tsukasa OI
2022-08-05  8:52   ` [PATCH v3] " Tsukasa OI
2022-08-05  8:59     ` Jan Beulich
2022-08-05 20:27 ` [PATCH] " Cary Coutant

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=27d2627d-363b-8b7c-cd7b-3c3ea6818714@suse.com \
    --to=jbeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=ccoutant@gmail.com \
    --cc=research_trasio@irq.a4lg.com \
    /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).