public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kito Cheng <kito.cheng@gmail.com>
To: Philipp Tomsich <philipp.tomsich@vrull.eu>
Cc: Jeff Law <jeffreyalaw@gmail.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
	 Raphael Moreira Zinsly <rzinsly@ventanamicro.com>
Subject: Re: [PATCH] RISC-V: Add Veyron V1 pipeline description
Date: Thu, 8 Jun 2023 23:18:16 +0800	[thread overview]
Message-ID: <CA+yXCZAkvwdgoMk3fp3yBX0Dm6kga=5F60itgrbRyFuS75cx3w@mail.gmail.com> (raw)
In-Reply-To: <CAAeLtUDOT55-hWm1i_2RNKu5L7+gzq42JU6XzKpK1rJp-BKPwA@mail.gmail.com>

> > I'd very much like to see the condops go into GCC as well, but I've been
> > hesitant to move it forward myself.  We're still waiting on hardware and
> > it wasn't clear to me that we really had consensus agreement to move the
> > bits forward based on an announcement vs waiting on actual hardware
> > availability (based on the comments from Palmer when I upstreamed the
> > binutils bits).

My bad, apparently I grep wrong binutils so I thought it isn't in the tree yet,
I don't have strong opinion on that, so I would defer this to Palmer.

      reply	other threads:[~2023-06-08 15:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07 13:17 Raphael Moreira Zinsly
2023-06-07 14:13 ` Kito Cheng
2023-06-07 14:43   ` Jeff Law
2023-06-07 21:06     ` Jeff Law
2023-06-08  7:33 ` Kito Cheng
2023-06-08  9:58   ` Philipp Tomsich
2023-06-08 10:22     ` Kito Cheng
2023-06-08 14:17       ` Jeff Law
2023-06-08 14:41         ` Philipp Tomsich
2023-06-08 15:18           ` Kito Cheng [this message]

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='CA+yXCZAkvwdgoMk3fp3yBX0Dm6kga=5F60itgrbRyFuS75cx3w@mail.gmail.com' \
    --to=kito.cheng@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=rzinsly@ventanamicro.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).