From: Nick Clifton <nickc@redhat.com>
To: Jan Beulich <jbeulich@suse.com>, Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] gas: retain whitespace between strings
Date: Wed, 16 Mar 2022 16:55:17 +0000 [thread overview]
Message-ID: <941f3fdc-bc52-afc9-9f70-69d25a236bc1@redhat.com> (raw)
In-Reply-To: <edad36de-f420-410d-5363-6be9d97896c0@suse.com>
Hi Jan,
> Change the scrubber to retain such whitespace, by making the processing
> of strings more similar to that of symbols. And indeed this appears to
> make sense when taking into account that for quite a while gas has been
> supporting quoted symbol names.
OK, that makes sense.
> Taking a more general view, however, the change doesn't go quite far
> enough. There are further cases where significant whitespace is removed
> by the scrubber. The new testcase enumerates a few in its ".if 0"
> section. I'm afraid the only way that I see to deal with this would be
> to significantly simplify the scrubber, such that it wouldn't do much
> more than collapse sequences of unquoted whitespace into a single blank.
> To be honest problems in this area aren't really surprising when seeing
> that there's hardly any checking of .macro use throughout the testsuite
> (and in particular in the [relatively] generic tests under all/).
Plus assembler macro syntax has never been that well specified.
> Partly RFC: While I did test this for x86, I didn't get around yet to
> run a much wider set of tests.
I ran my regression tester with the patch applied and nothing turned up,
so I am happy to approve the patch. One thing though - I think that it
would be a good idea to extend the documentation to cover this behaviour.
I do not mind if you do that as a separate patch, or just an extension
to this one, but I think that it should be done.
Cheers
Nick
next prev parent reply other threads:[~2022-03-16 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 8:14 Jan Beulich
2022-03-16 16:55 ` Nick Clifton [this message]
2022-03-17 8:20 ` Jan Beulich
2022-03-18 15:44 ` Nick Clifton
2022-03-21 7:16 ` Jan Beulich
2022-03-21 9:39 ` Jan Beulich
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=941f3fdc-bc52-afc9-9f70-69d25a236bc1@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.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).