public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Edwin Lu <ewlu@rivosinc.com>
To: gcc-patches@gcc.gnu.org
Cc: gnu-toolchain@rivosinc.com
Subject: Re: [Committed] RISC-V: Add Types to Un-Typed Sync Instructions:
Date: Fri, 25 Aug 2023 16:44:57 -0700	[thread overview]
Message-ID: <dd11c4ec-f634-44b9-8d1a-2e6282e98d0d@rivosinc.com> (raw)
Message-ID: <20230825234457.ypDjebsiB1X3AzUhHHpxXZak_rxm1Bm1z05ZAaLGMqQ@z> (raw)
In-Reply-To: <5a02fd13-95af-768a-f61d-7daf890076fa@gmail.com>

On 8/25/2023 11:53 AM, Jeff Law via Gcc-patches wrote:
> 
> 
> On 8/24/23 15:19, Edwin Lu wrote:
>> Related Discussion:
>> https://inbox.sourceware.org/gcc-patches/12fb5088-3f28-0a69-de1e-f387371a5eb2@gmail.com/
>>
>> This patch updates the sync instructions to ensure that no insn is left
>> without a type attribute. Updates a total of 6 insns to have type 
>> "atomic"
>>
>> Tested for regressions using rv32/64 multilib with newlib/linux.
>>
>> gcc/Changelog:
>>
>>     * config/riscv/sync-rvwmo.md: updated types to "multi" or
>>      "atomic" based on number of assembly lines generated
>>     * config/riscv/sync-ztso.md: likewise
>>     * config/riscv/sync.md: likewise
> OK.
> 
> You should have your write access set up already.  So go ahead and 
> follow the directions in the email you received to get yourself into the 
> MAINTAINERS file.  Then you can go ahead and push this change.
> 
> THanks,
> Jeff
> 
Committed!

Edwin



  reply	other threads:[~2023-08-25 23:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24 21:19 [PATCH V2] " Edwin Lu
2023-08-25 18:53 ` Jeff Law
2023-08-25 23:44   ` Edwin Lu [this message]
2023-08-25 23:44     ` [Committed] " Edwin Lu

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=dd11c4ec-f634-44b9-8d1a-2e6282e98d0d@rivosinc.com \
    --to=ewlu@rivosinc.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gnu-toolchain@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).