From: Vineet Gupta <vineetg@rivosinc.com>
To: gcc-patches@gcc.gnu.org
Cc: kito.cheng@gmail.com, jim.wilson.gcc@gmail.com,
"Palmer Dabbelt" <palmer@rivosinc.com>,
"Philipp Tomsich" <philipp.tomsich@vrull.eu>,
"Christoph Müllner" <christoph.muellner@vrull.eu>,
collison@rivosinc.com, gnu-toolchain@rivosinc.com,
"Vineet Gupta" <vineetg@rivosinc.com>
Subject: [PATCH 0/2] PIC cleanup
Date: Tue, 30 Aug 2022 10:48:28 -0700 [thread overview]
Message-ID: <20220830174830.224541-1-vineetg@rivosinc.com> (raw)
Hi,
A couple of cleanup patches when trying to understand -mexplicit-relocs
and code model.
- 1/2 should be strightfwd
- 2/2 might be slightly controversial.
Tested with a bunch of rv32/rv64 configs: same results before after,
granted pic might not really be getting tested here.
========= Summary of gcc testsuite =========
| # of unexpected case / # of unique unexpected case
| gcc | g++ | gfortran |
rv64imafdc/ lp64d/ medlow | 12 / 10 |11016 / 2776 | 0 / 0 |
rv32imafdc/ ilp32d/ medlow | 9 / 7 |10959 / 2764 | 0 / 0 |
rv32imac/ ilp32/ medlow | 9 / 7 |10959 / 2764 | 0 / 0 |
rv64imac/ lp64/ medlow | 13 / 11 |11016 / 2776 | 0 / 0 |
Thx,
-Vineet
Vineet Gupta (2):
RISC-V: remove deprecate pic code model macro
RISC-V: remove CM_PIC as it doesn't do much
gcc/config/riscv/riscv-c.cc | 7 -------
gcc/config/riscv/riscv-opts.h | 3 +--
gcc/config/riscv/riscv.cc | 2 +-
3 files changed, 2 insertions(+), 10 deletions(-)
--
2.32.0
next reply other threads:[~2022-08-30 17:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 17:48 Vineet Gupta [this message]
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 ` [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=20220830174830.224541-1-vineetg@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).