From: Patrick O'Neill <patrick@rivosinc.com>
To: gcc-patches@gcc.gnu.org
Cc: gnu-toolchain@rivosinc.com, jeffreyalaw@gmail.com,
palmer@rivosinc.com, rep.dot.nop@gmail.com,
Patrick O'Neill <patrick@rivosinc.com>
Subject: [PATCH] RISC-V: Name newly added flags in changelog
Date: Mon, 1 May 2023 09:10:37 -0700 [thread overview]
Message-ID: <20230501161037.614414-1-patrick@rivosinc.com> (raw)
This patch fixes the changelog to explicitly name the added command line
flags introduced in this patch:
https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616807.html
2023-05-01 Patrick O'Neill <patrick@rivosinc.com>
gcc/ChangeLog:
* ChangeLog: Name the flags added by the patch in the changelog.
Signed-off-by: Patrick O'Neill <patrick@rivosinc.com>
---
gcc/ChangeLog | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index fe8f624343c..7eb2b43c98c 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -109,10 +109,12 @@
PR target/104338
* config/riscv/riscv-protos.h: Add helper function stubs.
* config/riscv/riscv.cc: Add helper functions for subword masking.
- * config/riscv/riscv.opt: Add command-line flag.
+ * config/riscv/riscv.opt: Add command-line flags -minline-atomics and
+ -mno-inline-atomics.
* config/riscv/sync.md: Add masking logic and inline asm for fetch_and_op,
fetch_and_nand, CAS, and exchange ops.
- * doc/invoke.texi: Add blurb regarding command-line flag.
+ * doc/invoke.texi: Add blurb regarding new command-line flags
+ -minline-atomics and -mno-inline-atomics.
2023-04-26 Kyrylo Tkachov <kyrylo.tkachov@arm.com>
--
2.34.1
next reply other threads:[~2023-05-01 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 16:10 Patrick O'Neill [this message]
2023-05-02 15:50 ` Jeff Law
2023-05-02 16:24 ` Patrick O'Neill
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=20230501161037.614414-1-patrick@rivosinc.com \
--to=patrick@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu-toolchain@rivosinc.com \
--cc=jeffreyalaw@gmail.com \
--cc=palmer@rivosinc.com \
--cc=rep.dot.nop@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).