public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/106136] gcc-12.1.1 - libsanitizer fails when compiled for MIPS
Date: Thu, 30 Jun 2022 03:59:40 +0000 [thread overview]
Message-ID: <bug-106136-4-BQs7mcMc0X@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106136-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106136
Xi Ruoyao <xry111 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
CC| |xry111 at gcc dot gnu.org
Resolution|DUPLICATE |---
--- Comment #3 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
Not a duplicate. PR105614 happens because the attemption to build libsanitizer
with GCC 11 and we don't support this at all. This PR, instead, happens
because the MIPS code of libsanitizer is not compatible with musl.
next prev parent reply other threads:[~2022-06-30 3:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 9:17 [Bug sanitizer/106136] New: " immoloism at googlemail dot com
2022-06-29 9:32 ` [Bug sanitizer/106136] " immoloism at googlemail dot com
2022-06-29 11:57 ` marxin at gcc dot gnu.org
2022-06-30 3:59 ` xry111 at gcc dot gnu.org [this message]
2022-06-30 4:18 ` xry111 at gcc dot gnu.org
2024-05-29 18:33 ` syq at gcc dot gnu.org
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=bug-106136-4-BQs7mcMc0X@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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: 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).