public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Vineet Gupta <vineetg@rivosinc.com>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: gcc-patches@gcc.gnu.org, Kito Cheng <kito.cheng@gmail.com>,
	Jim Wilson <jim.wilson.gcc@gmail.com>,
	philipp.tomsich@vrull.eu, christoph.muellner@vrull.eu,
	collison@rivosinc.com, gnu-toolchain@rivosinc.com
Subject: Re: [PATCH 1/2] RISC-V: remove deprecate pic code model macro
Date: Wed, 31 Aug 2022 13:36:46 -0700	[thread overview]
Message-ID: <51722bee-6d84-f92b-0025-e216be931a6a@rivosinc.com> (raw)
In-Reply-To: <mhng-dfd1e731-e5d1-4f0b-a345-a4b155e38b33@palmer-mbp2014>

On 8/31/22 07:57, Palmer Dabbelt wrote:
> On Tue, 30 Aug 2022 10:48:29 PDT (-0700), Vineet Gupta wrote:
>> Came across this deprecated symbol when looking around for
>> -mexplicit-relocs handling in code
>>
>> Signed-off-by: Vineet Gupta <vineetg@rivosinc.com>
>> ---
>>  gcc/config/riscv/riscv-c.cc | 3 ---
>>  1 file changed, 3 deletions(-)
>>
>> 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:
>
> It looks like some of the tests
> (gcc/testsuite/gcc.target/riscv/predef-3.c, for example) are checking
> for __riscv_cmodel_pic.  From looking at them I'd expect them to fail,
> but even if they're not we should clean them up.

Aah, I did miss removing them and looks like there was a snafu in my 
test setup as well.
I'm rerunning the tests with the fix and will post a v2 after tests come 
out clean.

Thx,
-Vineet

  parent reply	other threads:[~2022-08-31 20:36 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
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     ` Vineet Gupta [this message]
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=51722bee-6d84-f92b-0025-e216be931a6a@rivosinc.com \
    --to=vineetg@rivosinc.com \
    --cc=christoph.muellner@vrull.eu \
    --cc=collison@rivosinc.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gnu-toolchain@rivosinc.com \
    --cc=jim.wilson.gcc@gmail.com \
    --cc=kito.cheng@gmail.com \
    --cc=palmer@rivosinc.com \
    --cc=philipp.tomsich@vrull.eu \
    /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).