public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Kito Cheng <kito.cheng@gmail.com>,
	Maxim Blinov <maxim.a.blinov@gmail.com>,
	Jeff Law <jlaw@ventanamicro.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
	gcc-patches@gcc.gnu.org, juzhe.zhong@rivai.ai,
	maxim.blinov@imgtec.com
Subject: Re: [PATCH] RISC-V: VECT: Remember to assert any_known_not_updated_vssa
Date: Mon, 6 Nov 2023 20:55:25 -0700	[thread overview]
Message-ID: <ffa8a453-b2c4-4e1c-8190-52f429a6de12@gmail.com> (raw)
In-Reply-To: <CA+yXCZCJyvh-CY6TSr5LQ9xFA66rnzxazfUS41na=67ovAc9iw@mail.gmail.com>



On 11/6/23 06:18, Kito Cheng wrote:
>> Oh, you're right! I should have checked the master branch first... and
>> I was even wondering why it wasn't marked as such. Should perhaps
>> cherry pick this for gcc-13-with-riscv-opts?
> 
>   gcc-13-with-riscv-opts mostly maintained by Ventana folks, so maybe
> ask Jeff if you want to cherry pick into that branch?
I haven't done the risc-v bits this week (yet, probably a job for the 
short flight tomorrow).  But I did go ahead and cherry-pick the 
appropriate generic bits to make the relevant IFNs const/nothrow.

jeff

  parent reply	other threads:[~2023-11-07  3:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 13:01 Maxim Blinov
2023-11-06 13:04 ` Richard Biener
2023-11-06 13:12   ` Maxim Blinov
2023-11-06 13:18     ` Kito Cheng
2023-11-06 14:39       ` Jeff Law
2023-11-07  3:55       ` Jeff Law [this message]
2023-11-09 16:26 ` Jeff Law
2023-11-09 22:05   ` Maxim Blinov

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=ffa8a453-b2c4-4e1c-8190-52f429a6de12@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jlaw@ventanamicro.com \
    --cc=juzhe.zhong@rivai.ai \
    --cc=kito.cheng@gmail.com \
    --cc=maxim.a.blinov@gmail.com \
    --cc=maxim.blinov@imgtec.com \
    --cc=richard.guenther@gmail.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).