public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: gcc-patches@gcc.gnu.org
Cc: Richard Sandiford <richard.sandiford@arm.com>,
	Yunqiang Su <yunqiang.su@cipunited.com>,
	Dimitrije Milosevic <Dimitrije.Milosevic@Syrmia.com>
Subject: PING: [PATCH] libsanitizer: don't enable for MIPS Linux without GNU libc [PR 106136]
Date: Mon, 25 Jul 2022 15:06:58 +0800	[thread overview]
Message-ID: <5058f9defb73232a983845d22c52c32d4151d69d.camel@xry111.site> (raw)
In-Reply-To: <d15c9f5d076972d994a5c508181e9a2c0bd171f9.camel@xry111.site>

Gentle ping :).

On Thu, 2022-06-30 at 12:22 +0800, Xi Ruoyao wrote:
> In libsanitizer code, the size of some GNU libc data structure
> (notably,
> struct stat) is hard coded.  These sizes may trigger a static assert
> buidling against another libc.
> 
> Just make non-GNU libc targets UNSUPPORTED now.  If someone really
> cares
> about those alternative libc implementations, please submit patch to
> LLVM project adding the support.
> 
> libsanitizer/ChangeLog
> 
>         PR sanitizer/106136
>         * configure.tgt: Change mips*-*-linux* to mips*-*-linux-gnu*
>         because it fails to build with non-GNU libc.
> ---
>  libsanitizer/configure.tgt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/libsanitizer/configure.tgt b/libsanitizer/configure.tgt
> index fb89df4935c..54b74b60e2f 100644
> --- a/libsanitizer/configure.tgt
> +++ b/libsanitizer/configure.tgt
> @@ -54,7 +54,7 @@ case "${target}" in
>         ;;
>    arm*-*-linux*)
>         ;;
> -  mips*-*-linux*)
> +  mips*-*-linux-gnu*)
>         ;;
>    aarch64*-*-linux*)
>         if test x$ac_cv_sizeof_void_p = x8; then

-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

      reply	other threads:[~2022-07-25  7:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30  4:22 Xi Ruoyao
2022-07-25  7:06 ` Xi Ruoyao [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=5058f9defb73232a983845d22c52c32d4151d69d.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=Dimitrije.Milosevic@Syrmia.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.sandiford@arm.com \
    --cc=yunqiang.su@cipunited.com \
    /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).