From: Andreas Schwab <schwab@linux-m68k.org>
To: Vineet Gupta <vineetg@rivosinc.com>
Cc: gcc-patches@gcc.gnu.org, collison@rivosinc.com,
gnu-toolchain@rivosinc.com, kito.cheng@gmail.com,
Philipp Tomsich <philipp.tomsich@vrull.eu>
Subject: Re: [PATCH v2] RISC-V: remove deprecate pic code model macro
Date: Fri, 02 Sep 2022 23:03:08 +0200 [thread overview]
Message-ID: <8735d9a3qr.fsf@igel.home> (raw)
In-Reply-To: <20220902203310.370711-1-vineetg@rivosinc.com> (Vineet Gupta's message of "Fri, 2 Sep 2022 13:33:10 -0700")
On Sep 02 2022, Vineet Gupta wrote:
> diff --git a/gcc/config/riscv/riscv-c.cc b/gcc/config/riscv/riscv-c.cc
> index eb7ef09297e9..bba72cf77a82 100644
> --- a/gcc/config/riscv/riscv-c.cc
> +++ b/gcc/config/riscv/riscv-c.cc
> @@ -93,9 +93,6 @@ riscv_cpu_cpp_builtins (cpp_reader *pfile)
> break;
>
> case CM_PIC:
> - /* __riscv_cmodel_pic is deprecated, and will removed in next GCC release.
> - see https://github.com/riscv/riscv-c-api-doc/pull/11 */
> - builtin_define ("__riscv_cmodel_pic");
> /* FALLTHROUGH. */
>
> case CM_MEDANY:
If there is nothing left between the case labels the fallthrough comment
is no longer needed.
--
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:[~2022-09-02 21:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 17:48 [PATCH 0/2] PIC cleanup Vineet Gupta
2022-08-30 17:48 ` [PATCH 1/2] RISC-V: remove deprecate pic code model macro Vineet Gupta
2022-08-31 14:57 ` Palmer Dabbelt
2022-08-31 15:35 ` Kito Cheng
2022-09-02 20:33 ` [PATCH v2] " Vineet Gupta
2022-09-02 21:03 ` Andreas Schwab [this message]
2022-09-02 21:05 ` [PATCH v3] " Vineet Gupta
2022-09-23 18:07 ` Vineet Gupta
2022-10-05 2:24 ` Kito Cheng
2022-10-05 3:33 ` Vineet Gupta
2022-08-31 20:36 ` [PATCH 1/2] " Vineet Gupta
2022-08-30 17:48 ` [PATCH 2/2] RISC-V: remove CM_PIC as it doesn't do much Vineet Gupta
2022-08-31 14:57 ` Palmer Dabbelt
2022-08-31 20:39 ` Vineet Gupta
2022-09-02 20:38 ` Vineet Gupta
2022-09-02 23:08 ` [PATCH] RISC-V: make USE_LOAD_ADDRESS_MACRO easier to understand Vineet Gupta
2022-09-23 16:01 ` Kito Cheng
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=8735d9a3qr.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=collison@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu-toolchain@rivosinc.com \
--cc=kito.cheng@gmail.com \
--cc=philipp.tomsich@vrull.eu \
--cc=vineetg@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).