public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-2296] libsanitizer: enable libubsan and libasan for loongarch64-*-linux* Date: Wed, 31 Aug 2022 06:34:30 +0000 (GMT) [thread overview] Message-ID: <20220831063430.D1A513857B86@sourceware.org> (raw) https://gcc.gnu.org/g:a542e4d67306f207845ce2a3036d5360654a6a8c commit r13-2296-ga542e4d67306f207845ce2a3036d5360654a6a8c Author: Xi Ruoyao <xry111@xry111.site> Date: Wed Aug 31 13:46:22 2022 +0800 libsanitizer: enable libubsan and libasan for loongarch64-*-linux* The LoongArch support for libubsan and libasan has been added in: - https://reviews.llvm.org/D129371 - https://reviews.llvm.org/D129418 and we've merged them in r13-2269. It's time to enable them. No unexpected failures in GCC asan.exp and ubsan.exp tests. libsanitizer/ChangeLog: * configure.tgt: Allow loongarch64-*-linux*. Diff: --- libsanitizer/configure.tgt | 2 ++ 1 file changed, 2 insertions(+) diff --git a/libsanitizer/configure.tgt b/libsanitizer/configure.tgt index fb89df4935c..87d8a2c3820 100644 --- a/libsanitizer/configure.tgt +++ b/libsanitizer/configure.tgt @@ -72,6 +72,8 @@ case "${target}" in ;; riscv64-*-linux*) ;; + loongarch64-*-linux*) + ;; *) UNSUPPORTED=1 ;;
reply other threads:[~2022-08-31 6:34 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220831063430.D1A513857B86@sourceware.org \ --to=xry111@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /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: linkBe 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).