From: Jakub Jelinek <jakub@redhat.com>
To: Lulu Cheng <chenglulu@loongson.cn>
Cc: gcc-patches@gcc.gnu.org, xry111@xry111.site, i@xen0n.name,
xuchenghua@loongson.cn, chenguoqi <chenguoqi@loongson.cn>
Subject: Re: [PATCH] LoongArch: libsanitizer: Enable build lsan and tsan for loongarch64.
Date: Fri, 2 Feb 2024 11:01:41 +0100 [thread overview]
Message-ID: <Zby9hSC6A0OvlR6E@tucnak> (raw)
In-Reply-To: <20240130020951.18469-1-chenglulu@loongson.cn>
On Tue, Jan 30, 2024 at 10:09:51AM +0800, Lulu Cheng wrote:
> From: chenguoqi <chenguoqi@loongson.cn>
>
> libsanitizer/ChangeLog:
>
> * configure.tgt: Enable tsan and lsan for loongarch64.
> * tsan/Makefile.am: Add tsan_rtl_loongarch64.S to EXTRA_libtsan_la_SOURCES.
This line is too long and should read
* tsan/Makefile.am (EXTRA_libtsan_la_SOURCES): Add
tsan_rtl_loongarch64.S.
> * tsan/Makefile.in: Regenerate.
Otherwise LGTM.
Jakub
next prev parent reply other threads:[~2024-02-02 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 2:09 Lulu Cheng
2024-02-02 1:37 ` chenglulu
2024-02-02 10:01 ` Jakub Jelinek [this message]
2024-02-04 1:24 ` chenglulu
2024-02-06 1:40 ` 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=Zby9hSC6A0OvlR6E@tucnak \
--to=jakub@redhat.com \
--cc=chenglulu@loongson.cn \
--cc=chenguoqi@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).