From: Jan Beulich <jbeulich@suse.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Andrew Waterman <andrew@sifive.com>,
Jim Wilson <jim.wilson.gcc@gmail.com>,
nelson@rivosinc.com, Nick Clifton <nickc@redhat.com>,
binutils@sourceware.org, Palmer Dabbelt <palmer@dabbelt.com>
Subject: Re: [PATCH] gas/RISC-V: adjust assembler for opcode table re-ordering
Date: Tue, 10 Jan 2023 10:25:04 +0100 [thread overview]
Message-ID: <4a67f41c-3473-3833-c0fc-ed4f69a062e9@suse.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2301092144270.65308@angie.orcam.me.uk>
On 09.01.2023 22:59, Maciej W. Rozycki wrote:
> On Mon, 9 Jan 2023, Palmer Dabbelt wrote:
>
>>>>> The similar workaround in my_getSmallExpression() actually looks
>>>>> suspicious to me: I expect that it would get in the way of using equates
>>>>> "shadowing" names of GPRs.
>>>>>
>>>>> --- a/gas/config/tc-riscv.c
>>>>> +++ b/gas/config/tc-riscv.c
>>>>> @@ -3266,6 +3266,17 @@ riscv_ip (char *str, struct riscv_cl_ins
>>>>> continue;
>>>>>
>>>>> case 'a': /* 20-bit PC-relative offset. */
>>>>> + /* Like in my_getSmallExpression() we need to avoid emitting
>>>>> + a stray undefined symbol if the 1st JAL entry doesn't match,
>>>>> + but the 2nd (with 2 operands) might. */
>>>>> + if (oparg == insn->args)
>>>>> + {
>>>>> + asargStart = asarg;
>>>>> + if (reg_lookup (&asarg, RCLASS_GPR, NULL)
>>>>> + && (*asarg == ',' || (ISSPACE (*asarg) && asarg[1] ==
>>>>> ',')))
>>>>> + break;
>>>>> + asarg = asargStart;
>>>>> + }
>>>>> jump:
>>>>> my_getExpression (imm_expr, asarg);
>>>>> asarg = expr_end;
>>>>
>>>> Thanks for the patch. I have tested it and confirmed it fix the problem
>>>> I reported.
>>>
>>> With 2.40 scheduled to be cut in less than a week, may I ask for an arch
>>> maintainer's view here?
>>
>> Thanks for fixing this. I don't have any issues with what's there, but looks
>> like I'm also getting some failures (glibc/multilib errno related stuff). I'm
>> trying to bisect those so I can't really get a proper test up now, I'll try to
>> do so ASAP as it's really late to have stuff broken.
>
> I wonder why the RISC-V port needs such a hack while the MIPS one
> doesn't.
Perhaps I misunderstood your earlier reply then. There you said you deal with
this by carefully ordering the opcode table. Here restoring the original order
would only be a temporary workaround, as it would re-introduce the
disassembler issue that was fixed by altering the order: Alias entries need to
come ahead of "real" ones, or else respective alias mnemonics would never be
emitted by the disassembler. Hence a solution is needed here which retains the
order, and which also respects that insn operands may be parsed
- more than once,
- with identical names having different meaning depending on context.
I realize what I'm doing is a hack, but I cannot think of anything better.
Jan
next prev parent reply other threads:[~2023-01-10 9:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 12:34 Jan Beulich
2023-01-07 23:29 ` Aurelien Jarno
2023-01-09 17:07 ` Jan Beulich
2023-01-09 19:07 ` Palmer Dabbelt
2023-01-09 21:59 ` Maciej W. Rozycki
2023-01-10 9:25 ` Jan Beulich [this message]
2023-01-10 22:58 ` Maciej W. Rozycki
2023-01-11 9:28 ` Jan Beulich
2023-01-12 1:28 ` Maciej W. Rozycki
2023-01-12 8:26 ` Jan Beulich
2023-01-12 8:40 ` Andrew Waterman
2023-01-10 12:31 ` Nick Clifton
2023-01-10 20:14 ` Palmer Dabbelt
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=4a67f41c-3473-3833-c0fc-ed4f69a062e9@suse.com \
--to=jbeulich@suse.com \
--cc=andrew@sifive.com \
--cc=binutils@sourceware.org \
--cc=jim.wilson.gcc@gmail.com \
--cc=macro@orcam.me.uk \
--cc=nelson@rivosinc.com \
--cc=nickc@redhat.com \
--cc=palmer@dabbelt.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).