From: chenglulu <chenglulu@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>, gcc-patches@gcc.gnu.org
Cc: i@xen0n.name, xuchenghua@loongson.cn
Subject: Re: [pushed ][PATCH v1 0/3] Add LoongarchV1.1 instructions support.
Date: Sat, 18 Nov 2023 16:15:58 +0800 [thread overview]
Message-ID: <9d35f652-8180-e380-6627-aa1c5216da5a@loongson.cn> (raw)
In-Reply-To: <dcd2b813c7db0c051e093f00df1f9e70136c7c0e.camel@xry111.site>
Pushed to r14-5568.
在 2023/11/17 下午7:09, Xi Ruoyao 写道:
> On Fri, 2023-11-17 at 16:33 +0800, Lulu Cheng wrote:
>> Lulu Cheng (3):
>> LoongArch: Add LA664 support.
>> LoongArch: Implement atomic operations using LoongArch1.1
>> instructions.
>> LoongArch: atomic_load and atomic_store are implemented using dbar
>> grading.
>>
>> gcc/config.gcc | 10 +-
>> .../loongarch/genopts/loongarch-strings | 1 +
>> gcc/config/loongarch/genopts/loongarch.opt.in | 3 +
>> gcc/config/loongarch/loongarch-cpu.cc | 4 +
>> gcc/config/loongarch/loongarch-def.c | 21 ++
>> gcc/config/loongarch/loongarch-def.h | 10 +-
>> gcc/config/loongarch/loongarch-opts.cc | 8 +-
>> gcc/config/loongarch/loongarch-opts.h | 6 +-
>> gcc/config/loongarch/loongarch-str.h | 1 +
>> gcc/config/loongarch/loongarch.cc | 7 +-
>> gcc/config/loongarch/loongarch.opt | 3 +
>> gcc/config/loongarch/sync.md | 256 ++++++++++++++---
>> -
>> 12 files changed, 263 insertions(+), 67 deletions(-)
> I'll rebase my patches for div32 and ld-seq-sa on top of this.
>
prev parent reply other threads:[~2023-11-18 8:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 8:33 [PATCH " Lulu Cheng
2023-11-17 8:33 ` [PATCH v1 1/3] LoongArch: Add LA664 support Lulu Cheng
2023-11-17 12:31 ` Xi Ruoyao
2023-11-17 12:58 ` chenglulu
2023-11-17 8:33 ` [PATCH v1 2/3] LoongArch: Implement atomic operations using LoongArch1.1 instructions Lulu Cheng
2023-11-17 8:33 ` [PATCH v1 3/3] LoongArch: atomic_load and atomic_store are implemented using dbar grading Lulu Cheng
2023-11-17 11:09 ` [PATCH v1 0/3] Add LoongarchV1.1 instructions support Xi Ruoyao
2023-11-18 8:15 ` chenglulu [this message]
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=9d35f652-8180-e380-6627-aa1c5216da5a@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).