public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@rivosinc.com>
To: philipp.tomsich@vrull.eu
Cc: gcc-patches@gcc.gnu.org, Vineet Gupta <vineetg@rivosinc.com>,
	jlaw@ventanamicro.com, Kito Cheng <kito.cheng@gmail.com>,
	christoph.muellner@vrull.eu, philipp.tomsich@vrull.eu
Subject: Re: [PATCH v2 0/2] Basic support for the Ventana VT1 w/ instruction fusion
Date: Mon, 14 Nov 2022 12:00:13 -0800 (PST)	[thread overview]
Message-ID: <mhng-9344dfda-bb95-4d7f-b5da-10bbabdf50bd@palmer-ri-x1c9a> (raw)
In-Reply-To: <20221113204824.4062042-1-philipp.tomsich@vrull.eu>

On Sun, 13 Nov 2022 12:48:22 PST (-0800), philipp.tomsich@vrull.eu wrote:
>
> This series provides support for the Ventana VT1 (a 4-way superscalar
> rv64gc_zba_zbb_zbc_zbs_zifenci_xventanacondops core) including support
> for the supported instruction fusion patterns.
>
> This includes the addition of the fusion-aware scheduling
> infrastructure for RISC-V and implements idiom recognition for the
> fusion patterns supported by VT1.
>
> Note that we don't signal support for XVentanaCondOps at this point,
> as the XVentanaCondOps support is in-flight separately.  Changing the
> defaults for VT1 can happen late in the cycle, so no need to link the
> two different changesets.
>
> Changes in v2:
> - Rebased and changed over to .rst-based documentation
> - Updated to catch more fusion cases
> - Signals support for Zifencei
>
> Philipp Tomsich (2):
>   RISC-V: Add basic support for the Ventana-VT1 core
>   RISC-V: Add instruction fusion (for ventana-vt1)
>
>  gcc/config/riscv/riscv-cores.def              |   3 +
>  gcc/config/riscv/riscv-opts.h                 |   2 +-
>  gcc/config/riscv/riscv.cc                     | 233 ++++++++++++++++++
>  .../risc-v-options.rst                        |   5 +-
>  4 files changed, 240 insertions(+), 3 deletions(-)

I guess we never really properly talked about this on the GCC mailing 
lists, but IMO it's fine to start taking code for designs that have been 
announced under the assumption that if the hardware doesn't actually 
show up according to those timelines that it will be assumed to have 
never existed and thus be removed more quickly than usual.

That said, I can't find anything describing that the VT-1 exists aside 
from these patches.  Is there anything that describes this design and 
when it's expected to be available?

  parent reply	other threads:[~2022-11-14 20:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-13 20:48 Philipp Tomsich
2022-11-13 20:48 ` [PATCH v2 1/2] RISC-V: Add basic support for the Ventana-VT1 core Philipp Tomsich
2022-11-14 15:52   ` Jeff Law
2022-11-14 15:57     ` Philipp Tomsich
2022-11-14 18:50     ` Philipp Tomsich
2022-11-13 20:48 ` [PATCH v2 2/2] RISC-V: Add instruction fusion (for ventana-vt1) Philipp Tomsich
2022-11-14 16:06   ` Jeff Law
2022-11-14 16:11     ` Jakub Jelinek
2022-11-14 18:55     ` Philipp Tomsich
2022-11-14 19:10       ` Jeff Law
2022-11-14 20:00 ` Palmer Dabbelt [this message]
2022-11-14 20:03   ` [PATCH v2 0/2] Basic support for the Ventana VT1 w/ instruction fusion Philipp Tomsich
2022-11-14 20:58     ` Palmer Dabbelt
2022-11-14 21:14       ` Philipp Tomsich
2022-11-14 22:47         ` Palmer Dabbelt
2022-11-14 23:00           ` Philipp Tomsich
2022-11-15  7:25             ` Richard Biener
2022-11-15 17:30               ` Palmer Dabbelt
2022-11-14 21:23   ` Jeff Law
2022-11-14 21:28     ` Philipp Tomsich

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-9344dfda-bb95-4d7f-b5da-10bbabdf50bd@palmer-ri-x1c9a \
    --to=palmer@rivosinc.com \
    --cc=christoph.muellner@vrull.eu \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jlaw@ventanamicro.com \
    --cc=kito.cheng@gmail.com \
    --cc=philipp.tomsich@vrull.eu \
    --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).