From: Palmer Dabbelt <palmer@dabbelt.com>
To: jbeulich@suse.com
Cc: nelson@rivosinc.com, binutils@sourceware.org,
Andrew Waterman <andrew@sifive.com>,
Jim Wilson <jim.wilson.gcc@gmail.com>
Subject: Re: [PATCH 2/2] RISC-V: adjust logic to avoid register name symbols
Date: Thu, 16 Feb 2023 08:54:01 -0800 (PST) [thread overview]
Message-ID: <mhng-b6e8ac4b-96e9-426d-8bb0-898769d2e620@palmer-ri-x1c9a> (raw)
In-Reply-To: <2bb25d60-0a22-ed4d-0056-f1f21a6dae62@suse.com>
On Thu, 16 Feb 2023 08:49:36 PST (-0800), jbeulich@suse.com wrote:
> On 16.02.2023 10:36, Nelson Chu wrote:
>> Yeah the logs are too big, so not sure where can be uploaded these
>> kind of huge files. However, we should get the same result if we just
>> run the gcc upstream testsuites. Seems many errors but a quick
>> review, most of them are,
>>
>> *Assembler messages:
>> *Error: register value used as expression
>> ...
>>
>> Here are some details,
>
> Thanks - knowing examples of failures and compiler options used is
> sufficient indeed. And yes, taking one of the examples I can repro and
> will hence be able to investigate. (As hinted at earlier, first thing
> I'll do is add yet another testcase to the gas testsuite, as imo the
> case should be covered there).
Thanks for that, we didn't really add target-specific tests when we did
the original binutils port and it bites us pretty frequently for stuff
like this. So the more we can get in there the better.
next prev parent reply other threads:[~2023-02-16 16:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 8:01 [PATCH 0/2] RISC-V/gas: re-work register named symbols avoidance logic Jan Beulich
2023-02-13 8:02 ` [PATCH 1/2] RISC-V: test for expected / no unexpected symbols Jan Beulich
2023-02-13 8:02 ` [PATCH 2/2] RISC-V: adjust logic to avoid register name symbols Jan Beulich
2023-02-15 3:09 ` Nelson Chu
2023-02-15 8:03 ` Jan Beulich
2023-02-15 8:48 ` Nelson Chu
2023-02-15 9:21 ` Jan Beulich
2023-02-16 9:36 ` Nelson Chu
2023-02-16 16:49 ` Jan Beulich
2023-02-16 16:54 ` Palmer Dabbelt [this message]
2023-03-03 13:52 ` Jan Beulich
2023-03-15 10:07 ` Nelson Chu
2023-03-15 11:49 ` Jan Beulich
2023-03-16 0:30 ` Nelson Chu
2023-04-19 9:37 ` 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=mhng-b6e8ac4b-96e9-426d-8bb0-898769d2e620@palmer-ri-x1c9a \
--to=palmer@dabbelt.com \
--cc=andrew@sifive.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=jim.wilson.gcc@gmail.com \
--cc=nelson@rivosinc.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).