public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@rivosinc.com>
To: jeffreyalaw@gmail.com
Cc: Andrew Waterman <andrew@sifive.com>,
	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, 01 Jul 2023 07:34:56 -0700 (PDT)	[thread overview]
Message-ID: <mhng-7ca10bd8-b96d-419d-82da-40daab68faeb@palmer-ri-x1c9> (raw)
In-Reply-To: <f3c04812-5dfe-c3b5-336c-97d020599a57@gmail.com>

On Sat, 01 Jul 2023 07:04:16 PDT (-0700), jeffreyalaw@gmail.com wrote:
>
>
> 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.

Ya, we haven't even gotten to the point where most implementations are 
shipping with the B extensions, much less to the point where we can 
start ignoring all the pre-B hardware.

  reply	other threads:[~2023-07-01 14:34 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
2023-07-01 14:34               ` Palmer Dabbelt [this message]
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=mhng-7ca10bd8-b96d-419d-82da-40daab68faeb@palmer-ri-x1c9 \
    --to=palmer@rivosinc.com \
    --cc=andrew@sifive.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gnu-toolchain@rivosinc.com \
    --cc=jeffreyalaw@gmail.com \
    --cc=kito.cheng@gmail.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).