From: Xi Ruoyao <xry111@mengyan1223.wang>
To: chenglulu <chenglulu@loongson.cn>, gcc-patches@gcc.gnu.org
Cc: yangyujie@loongson.cn, xuchenghua@loongson.cn
Subject: Re: LoongArch Port
Date: Sat, 27 Nov 2021 17:57:14 +0800 [thread overview]
Message-ID: <4b83339bdb06ba7a08a525a49646471bcb1307d1.camel@mengyan1223.wang> (raw)
In-Reply-To: <20211127082735.4139682-1-chenglulu@loongson.cn>
On Sat, 2021-11-27 at 16:27 +0800, chenglulu wrote:
> The LoongArch architecture (LoongArch) is an Instruction Set
> Architecture (ISA) that has a Reduced Instruction Set Computer (RISC)
> style.
> The documents are on
> https://loongson.github.io/LoongArch-Documentation/README-EN.html
>
> The ELF ABI Documents are on:
> https://loongson.github.io/LoongArch-Documentation/LoongArch-ELF-ABI-EN.html
>
> The binutils has been merged into trunk:
> https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=560b3fe208255ae909b4b1c88ba9c28b09043307
>
> Note: this GCC port requires the following patch applied to binutils
> to build.
> https://github.com/loongson/binutils-gdb/commit/aacb0bf860f02aa5a7dcb76dd0e392bf871c7586
> (will be submitted to upstream soon)
>
> chenglulu (12):
>
> LoongArch Port: gcc build
> LoongArch Port: Regenerate gcc/configure.
> LoongArch Port: Machine Decsription files.
> LoongArch Port: Machine description C files and .h
> LoongArch Port: Builtin functions.
> LoongArch Port: Builtin macros.
> LoongArch Port: libgcc
> LoongArch Port: Regenerate libgcc/configure.
> LoongArch Port: libgomp
> LoongArch Port: gcc/testsuite
> LoongArch Port: Regenerate configure
> LoongArch Port: Add doc.
GCC 12 is at stage 3 now, I think in stage 3 a new port won't be merged.
It's needed to be rebased for GCC 13, after GCC 12.1.0 release.
--
Xi Ruoyao <xry111@mengyan1223.wang>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2021-11-27 9:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 8:27 chenglulu
2021-11-27 8:27 ` [PATCH 01/12] LoongArch Port: gcc build chenglulu
2021-11-27 23:39 ` Xi Ruoyao
2021-11-27 23:43 ` Xi Ruoyao
2021-11-28 0:51 ` Xi Ruoyao
2021-11-29 21:10 ` Joseph Myers
2021-11-27 8:27 ` [PATCH 02/12] LoongArch Port: Regenerate gcc/configure chenglulu
2021-11-27 8:27 ` [PATCH 03/12] LoongArch Port: Machine Decsription files chenglulu
2021-11-27 8:27 ` [PATCH 04/12] LoongArch Port: Machine description C files and .h files chenglulu
2021-11-27 8:27 ` [PATCH 05/12] LoongArch Port: Builtin functions chenglulu
2021-11-27 8:27 ` [PATCH 06/12] LoongArch Port: Builtin macros chenglulu
2021-11-27 8:27 ` [PATCH 07/12] LoongArch Port: libgcc chenglulu
2021-11-27 8:27 ` [PATCH 08/12] LoongArch Port: Regenerate libgcc/configure chenglulu
2021-11-27 8:27 ` [PATCH 09/12] LoongArch Port: libgomp chenglulu
2021-11-27 8:27 ` [PATCH 10/12] LoongArch Port: gcc/testsuite chenglulu
2021-11-27 8:27 ` [PATCH 11/12] LoongArch Port: Regenerate configure chenglulu
2021-11-27 8:27 ` [PATCH 12/12] LoongArch Port: Add doc chenglulu
2021-11-27 9:57 ` Xi Ruoyao [this message]
2021-11-28 0:06 ` LoongArch Port Xi Ruoyao
2021-11-28 8:37 ` Xi Ruoyao
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=4b83339bdb06ba7a08a525a49646471bcb1307d1.camel@mengyan1223.wang \
--to=xry111@mengyan1223.wang \
--cc=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=xuchenghua@loongson.cn \
--cc=yangyujie@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).