public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kito Cheng <kito.cheng@gmail.com>
To: Andreas Schwab <schwab@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] riscv: add work around for PR sanitizer/82501
Date: Tue, 30 May 2023 17:03:27 +0800	[thread overview]
Message-ID: <CA+yXCZA_KyEtAg=ZxA1d5OkX+6ATw-Sx5oYBLzqHVRQKAs6e4Q@mail.gmail.com> (raw)
In-Reply-To: <mvmfs7eciqg.fsf@suse.de>

LGTM, thanks :)

On Tue, May 30, 2023 at 4:43 PM Andreas Schwab via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
>         PR sanitizer/82501
>         * c-c++-common/asan/pointer-compare-1.c: Disable use of small data
>         on RISC-V.
> ---
>  gcc/testsuite/c-c++-common/asan/pointer-compare-1.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/gcc/testsuite/c-c++-common/asan/pointer-compare-1.c b/gcc/testsuite/c-c++-common/asan/pointer-compare-1.c
> index 4b558bf8179..fb9126d6df1 100644
> --- a/gcc/testsuite/c-c++-common/asan/pointer-compare-1.c
> +++ b/gcc/testsuite/c-c++-common/asan/pointer-compare-1.c
> @@ -5,6 +5,7 @@
>  /* FIXME: remove me after PR sanitizer/82501 is resolved.  */
>  /* { dg-additional-options "-fno-section-anchors" } */
>  /* { dg-additional-options "-msdata=none" { target { powerpc*-*-* } } } */
> +/* { dg-additional-options "-msmall-data-limit=0" { target { riscv*-*-* } } } */
>
>  volatile int v;
>
> --
> 2.40.1
>
>
> --
> Andreas Schwab, SUSE Labs, schwab@suse.de
> GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
> "And now for something completely different."

      reply	other threads:[~2023-05-30  9:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30  8:43 Andreas Schwab
2023-05-30  9:03 ` Kito Cheng [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='CA+yXCZA_KyEtAg=ZxA1d5OkX+6ATw-Sx5oYBLzqHVRQKAs6e4Q@mail.gmail.com' \
    --to=kito.cheng@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=schwab@suse.de \
    /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).