From: Jan Beulich <jbeulich@suse.com>
To: Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: PR28977 tc-i386.c internal error in parse_register
Date: Mon, 21 Mar 2022 17:59:28 +0100 [thread overview]
Message-ID: <c0d8c4d8-6db5-a1a7-ce05-820eba17968b@suse.com> (raw)
In-Reply-To: <YjR0+l4WyG+IWF3D@squeak.grove.modra.org>
On 18.03.2022 13:03, Alan Modra wrote:
> Heh, if you really want to get your teeth into this, try this one:
>
> b=a
> a=%rax
> xor b,%rax
Now this one isn't very difficult to resolve (and actually make
work). What looks harder is how to make cleanly fail e.g.
b=a
xor b,%rax
a=%rax
Jan
prev parent reply other threads:[~2022-03-21 16:59 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
2022-03-21 16:59 ` 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=c0d8c4d8-6db5-a1a7-ce05-820eba17968b@suse.com \
--to=jbeulich@suse.com \
--cc=amodra@gmail.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).