From: Jan Beulich <jbeulich@suse.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] gas: retain whitespace between strings
Date: Mon, 21 Mar 2022 10:39:32 +0100 [thread overview]
Message-ID: <5f7de3cd-dc74-757e-5a8a-f39dc2b87ecb@suse.com> (raw)
In-Reply-To: <9c24aad3-04f1-00e3-a2fd-36e5e23737ca@suse.com>
On 21.03.2022 08:16, Jan Beulich via Binutils wrote:
> On 18.03.2022 16:44, Nick Clifton wrote:
>>>> One thing though - I think that it
>>>> would be a good idea to extend the documentation to cover this behaviour.
>>
>>> Or did you mean me to merely describe the specific behavior for .macro,
>>> leaving aside potential effects elsewhere?
>>
>> I think that this should be sufficient. :-)
>
> Okay, I'll try to invent some wording. But before that I guess I'll
> actually need to deal a strange regression with the change in tic4x
> and tic54x - the output of the .byte directives in all/macro.s has
> extra zeros appended in the listing (didn't check yet whether that's
> also the case in the generated object files). Of the changes I have
> under test, I can only guess it's the one here, but of course I'll
> need to isolate that as the first step to figuring what's going on
> there. I'm mentioning it here merely in case it rings a bell ...
Ah, yes - I've spotted respective comments and alike for other test
cases.
Jan
prev parent reply other threads:[~2022-03-21 9:39 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
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 [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=5f7de3cd-dc74-757e-5a8a-f39dc2b87ecb@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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).