From: Alan Modra <amodra@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: binutils@sourceware.org
Subject: Re: PR28977 tc-i386.c internal error in parse_register
Date: Fri, 18 Mar 2022 22:33:06 +1030 [thread overview]
Message-ID: <YjR0+l4WyG+IWF3D@squeak.grove.modra.org> (raw)
In-Reply-To: <2614e201-d2a0-6e68-23f7-ea4c14700df0@suse.com>
On Fri, Mar 18, 2022 at 10:39:42AM +0100, Jan Beulich wrote:
> On 18.03.2022 08:32, Alan Modra wrote:
> > My testcase was a little tidier but still gives:
> >
> > mad.s: Error: invalid operands (*GAS `reg' section* and *GAS `reg' section* sections) for `%' when setting `s'
>
> That's only with your change in place, I assume?
Yes.
> > The aim of the patch is to stop an abort *before* we decide the
> > expression is invalid. i386 parse_register was being called via
> > md_parse_name in gas/expr.c:operand.
>
> It still feels like your change is merely hiding a problem elsewhere.
If you think the patch is wrong, please feel free to revert it. Since
we are getting into this discussion, I guess I should have asked
permission.
I don't doubt there are problems elsewhere, but I have some experience
tweaking the expression evaluation code (as do you) and don't want to
go down that rabbit hole for the sake of correcting the ssegment in
erroneous expressions.
I most definitely do not want to spend a large amount of my time
fixing things that never occur in real assembly source, as opposed to
the ridiculuous stuff fed to gas by fuzzers.
> Going from your example (and observing where the abort actually is
> reported) I added a 3rd instance of x=s. Then the abort continues to
> be reported on the 2nd instance. If things were working consistently,
> I would expect it to happen either on the first instance or at the
> end of the file (in this latter case the location reported would
> simply be bogus).
Oh yes, I noticed the same. Just one instance of x=s doesn't hit the
problem either. There were rather a lot more duplicated assignments
in the original 17k of fuzzer garbage, and the symbol name wasn't a
nice "x"!
> I think the original know(e->X_op == O_register) was actually quite
> appropriate when seeing a reg_section symbol come in. No reg_section
> symbols violating this should ever be constructed, at least not for
> x86.
Might be difficult to enforce if forward references are allowed.
Heh, if you really want to get your teeth into this, try this one:
b=a
a=%rax
xor b,%rax
> There might be architectures where such makes sense, albeit
> code like this in expr.c:
>
> else if (mode != expr_defer && segment == reg_section)
> {
> expressionP->X_op = O_register;
> expressionP->X_add_number = S_GET_VALUE (symbolP);
> }
>
> makes me think such should never be put into existence. I seem to
> have a vague recollection of, very long ago, having discussed with
> you already the question of too little use of expr_section in the
> course of expression evaluation (without any actual outcome as far
> as changes to the code).
>
> Jan
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2022-03-18 12:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 6:56 Alan Modra
2022-03-18 7:12 ` Jan Beulich
2022-03-18 7:32 ` Alan Modra
2022-03-18 9:39 ` Jan Beulich
2022-03-18 12:03 ` Alan Modra [this message]
2022-03-21 16:59 ` 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=YjR0+l4WyG+IWF3D@squeak.grove.modra.org \
--to=amodra@gmail.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).