From: Andreas Schwab <schwab@linux-m68k.org>
To: Patrick O'Neill <patrick@rivosinc.com>
Cc: gcc-patches@gcc.gnu.org, palmer@rivosinc.com,
kito.cheng@gmail.com, david.abd@gmail.com,
jeffreyalaw@gmail.com
Subject: Re: [PATCH v5] RISCV: Inline subword atomic ops
Date: Tue, 18 Apr 2023 17:06:05 +0200 [thread overview]
Message-ID: <87y1mpb57m.fsf@igel.home> (raw)
In-Reply-To: <20230418142858.2424851-1-patrick@rivosinc.com> (Patrick O'Neill's message of "Tue, 18 Apr 2023 07:28:58 -0700")
On Apr 18 2023, Patrick O'Neill wrote:
> diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
> index a38547f53e5..9c3e91d2fee 100644
> --- a/gcc/doc/invoke.texi
> +++ b/gcc/doc/invoke.texi
> @@ -1227,6 +1227,7 @@ See RS/6000 and PowerPC Options.
> -mstack-protector-guard=@var{guard} -mstack-protector-guard-reg=@var{reg}
> -mstack-protector-guard-offset=@var{offset}
> -mcsr-check -mno-csr-check}
> +-minline-atomics -mno-inline-atomics
The options need to be inside @gccoptlist.
> @@ -29006,6 +29007,13 @@ Do or don't use smaller but slower prologue and epilogue code that uses
> library function calls. The default is to use fast inline prologues and
> epilogues.
>
> +@item -minline-atomics
> +@itemx -mno-inline-atomics
> +@opindex minline-atomics
@opindex should precede @item.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2023-04-18 15:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 21:58 [PATCH v4] RISC-V: Add support for inlining subword atomic operations Palmer Dabbelt
2022-09-02 10:08 ` Kito Cheng
2022-10-28 16:55 ` David Abdurachmanov
2022-11-16 3:53 ` Jeff Law
2023-04-18 14:28 ` [PATCH v5] RISCV: Inline subword atomic ops Patrick O'Neill
2023-04-18 15:06 ` Andreas Schwab [this message]
2023-04-18 16:39 ` [PATCH v6] " Patrick O'Neill
2023-04-18 20:17 ` Palmer Dabbelt
2023-04-18 21:41 ` [PATCH v7] " Patrick O'Neill
2023-04-24 17:20 ` Patrick O'Neill
2023-04-25 5:52 ` Jeff Law
2023-04-25 15:20 ` Patrick O'Neill
2023-04-26 2:27 ` Jeff Law
2023-04-26 17:01 ` [committed] " Patrick O'Neill
2023-05-02 20:34 ` Patrick O'Neill
2023-05-03 6:32 ` Jeff Law
2023-05-03 9:49 ` Richard Biener
2023-05-03 14:14 ` Palmer Dabbelt
2023-05-03 15:13 ` Jeff Law
2023-05-03 15:33 ` Palmer Dabbelt
2023-05-03 16:13 ` Patrick O'Neill
2023-04-18 16:59 ` [PATCH v5] " Jeff Law
2023-04-18 20:48 ` Patrick O'Neill
2023-04-18 21:04 ` Jeff Law
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=87y1mpb57m.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=david.abd@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=palmer@rivosinc.com \
--cc=patrick@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).