From: Jeff Law <jeffreyalaw@gmail.com>
To: Andrew Waterman <andrew@sifive.com>,
Palmer Dabbelt <palmer@rivosinc.com>
Cc: Vineet Gupta <vineetg@rivosinc.com>,
gcc-patches@gcc.gnu.org, Kito Cheng <kito.cheng@gmail.com>,
gnu-toolchain@rivosinc.com
Subject: Re: [PATCH] RISC-V: improve codegen for repeating large constants [3]
Date: Sat, 1 Jul 2023 08:04:16 -0600 [thread overview]
Message-ID: <f3c04812-5dfe-c3b5-336c-97d020599a57@gmail.com> (raw)
In-Reply-To: <CA++6G0ALM-9aVUiqE=YDB7-jEhYNg6RScBk4urnFpC-BmwjKoA@mail.gmail.com>
On 7/1/23 02:00, Andrew Waterman wrote:
>
> Yeah, that might end up being a false economy for superscalars.
>
> In general, I wouldn't recommend spending too many cleverness beans on
> non-Zba+Zbb implementations. Going forward, we should expect that
> even very simple cores provide those extensions.
I suspect you under-estimate how difficult it is to get the distros to
move forward on baseline ISAs.
jeff
next prev parent reply other threads:[~2023-07-01 14:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 23:33 Vineet Gupta
2023-06-30 23:41 ` Vineet Gupta
2023-06-30 23:50 ` Andrew Waterman
2023-07-01 0:13 ` Vineet Gupta
2023-07-01 0:25 ` Andrew Waterman
2023-07-01 0:36 ` Palmer Dabbelt
2023-07-01 8:00 ` Andrew Waterman
2023-07-01 14:04 ` Jeff Law [this message]
2023-07-01 14:34 ` Palmer Dabbelt
2023-07-01 15:08 ` Andrew Waterman
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=f3c04812-5dfe-c3b5-336c-97d020599a57@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=andrew@sifive.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu-toolchain@rivosinc.com \
--cc=kito.cheng@gmail.com \
--cc=palmer@rivosinc.com \
--cc=vineetg@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).