From: Lulu Cheng <chenglulu@loongson.cn>
To: gcc-patches@gcc.gnu.org
Cc: xry111@xry111.site, i@xen0n.name, xuchenghua@loongson.cn,
chenglulu@loongson.cn
Subject: [PATCH v2 0/2] Delete ISA_BASE_LA64V110 related definitions.
Date: Tue, 5 Dec 2023 10:30:17 +0800 [thread overview]
Message-ID: <20231205023019.32452-1-chenglulu@loongson.cn> (raw)
1. Rebase Xi Ruoyao's patch a to the latest commit.
https://gcc.gnu.org/pipermail/gcc-patches/2023-November/636798.html
2. remove the #if
!defined(IN_LIBGCC2) && !defined(IN_TARGET_LIBS) && !defined(IN_RTS)
guards in loongarch-def.h and loongarch-opts.h as they'll be unneeded.
3. Described in LoongArch Reference Manual v1.1:
The new functional subsets in each new version have independent identification
bits in the return value of the CPUCFG instruction. It is recommended that the
software determines the running process based on this information rather than
the version number of the Loongson architecture.
So delete the ISA_BASE_LA64V110 related definitions here.
*** BLURB HERE ***
Lulu Cheng (1):
LoongArch: Remove the definition of ISA_BASE_LA64V110 from the code.
Xi Ruoyao (1):
LoongArch: Switch loongarch-def from C to C++ to make it possible.
.../loongarch/genopts/loongarch-strings | 1 -
gcc/config/loongarch/genopts/loongarch.opt.in | 3 -
gcc/config/loongarch/loongarch-cpu.cc | 23 +-
gcc/config/loongarch/loongarch-def-array.h | 40 +++
gcc/config/loongarch/loongarch-def.c | 227 ------------------
gcc/config/loongarch/loongarch-def.cc | 193 +++++++++++++++
gcc/config/loongarch/loongarch-def.h | 67 +++---
gcc/config/loongarch/loongarch-opts.cc | 10 +-
gcc/config/loongarch/loongarch-opts.h | 9 +-
gcc/config/loongarch/loongarch-str.h | 1 -
gcc/config/loongarch/loongarch-tune.h | 123 +++++++++-
gcc/config/loongarch/loongarch.opt | 3 -
gcc/config/loongarch/t-loongarch | 4 +-
13 files changed, 405 insertions(+), 299 deletions(-)
create mode 100644 gcc/config/loongarch/loongarch-def-array.h
delete mode 100644 gcc/config/loongarch/loongarch-def.c
create mode 100644 gcc/config/loongarch/loongarch-def.cc
--
2.31.1
next reply other threads:[~2023-12-05 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 2:30 Lulu Cheng [this message]
2023-12-05 2:30 ` [PATCH v2 1/2] LoongArch: Switch loongarch-def from C to C++ to make it possible Lulu Cheng
2023-12-05 2:30 ` [PATCH v2 2/2] LoongArch: Remove the definition of ISA_BASE_LA64V110 from the code Lulu Cheng
2023-12-08 7:39 ` [pushed][PATCH v2 0/2] Delete ISA_BASE_LA64V110 related definitions chenglulu
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=20231205023019.32452-1-chenglulu@loongson.cn \
--to=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--cc=xry111@xry111.site \
--cc=xuchenghua@loongson.cn \
/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).