From: Xi Ruoyao <xry111@xry111.site>
To: Lulu Cheng <chenglulu@loongson.cn>, gcc-patches@gcc.gnu.org
Cc: xuchenghua@loongson.cn
Subject: Re: [PATCH v2] LoongArch: Fix pr106828 by define hook TARGET_ASAN_SHADOW_OFFSET in loongarch backend.
Date: Wed, 07 Sep 2022 16:02:51 +0800 [thread overview]
Message-ID: <886a2abd8dfdaaf82ca6c2445f5ecb584121987f.camel@xry111.site> (raw)
In-Reply-To: <20220907073946.1102002-1-chenglulu@loongson.cn>
On Wed, 2022-09-07 at 15:39 +0800, Lulu Cheng wrote:
> Sorry, asan shadow offset is wrong in v1.
>
> In the file asan_mapping.h line 207:
> # define ASAN_SHADOW_OFFSET_CONST 0x0000400000000000
>
> So it's should be 1<<46.
LGTM. I forgot to include this change in r13-2296 :(.
>
> ------------------------------------
> gcc/ChangeLog:
>
> PR target/106828
> * config/loongarch/loongarch.cc
> (loongarch_asan_shadow_offset): New.
> (TARGET_ASAN_SHADOW_OFFSET): New.
>
> gcc/testsuite/ChangeLog:
>
> PR target/106828
> * g++.target/loongarch/pr106828.C: New test.
> ---
> gcc/config/loongarch/loongarch.cc | 13 +++++++++++++
> gcc/testsuite/g++.target/loongarch/pr106828.C | 4 ++++
> 2 files changed, 17 insertions(+)
> create mode 100644 gcc/testsuite/g++.target/loongarch/pr106828.C
>
> diff --git a/gcc/config/loongarch/loongarch.cc
> b/gcc/config/loongarch/loongarch.cc
> index 10acf06ef79..424fa4487f8 100644
> --- a/gcc/config/loongarch/loongarch.cc
> +++ b/gcc/config/loongarch/loongarch.cc
> @@ -6471,6 +6471,16 @@ loongarch_use_anchors_for_symbol_p (const_rtx
> symbol)
> return default_use_anchors_for_symbol_p (symbol);
> }
>
> +/* Implement the TARGET_ASAN_SHADOW_OFFSET hook. */
> +
> +static unsigned HOST_WIDE_INT
> +loongarch_asan_shadow_offset (void)
> +{
> + /* We only have libsanitizer support for LOONGARCH64 at present.
> + This value is taken from the file
> libsanitizer/asan/asan_mappint.h. */
> + return TARGET_64BIT ? (HOST_WIDE_INT_1 << 46) : 0;
> +}
> +
> /* Initialize the GCC target structure. */
> #undef TARGET_ASM_ALIGNED_HI_OP
> #define TARGET_ASM_ALIGNED_HI_OP "\t.half\t"
> @@ -6665,6 +6675,9 @@ loongarch_use_anchors_for_symbol_p (const_rtx
> symbol)
> #undef TARGET_USE_ANCHORS_FOR_SYMBOL_P
> #define TARGET_USE_ANCHORS_FOR_SYMBOL_P
> loongarch_use_anchors_for_symbol_p
>
> +#undef TARGET_ASAN_SHADOW_OFFSET
> +#define TARGET_ASAN_SHADOW_OFFSET loongarch_asan_shadow_offset
> +
> struct gcc_target targetm = TARGET_INITIALIZER;
>
> #include "gt-loongarch.h"
> diff --git a/gcc/testsuite/g++.target/loongarch/pr106828.C
> b/gcc/testsuite/g++.target/loongarch/pr106828.C
> new file mode 100644
> index 00000000000..190c1db715f
> --- /dev/null
> +++ b/gcc/testsuite/g++.target/loongarch/pr106828.C
> @@ -0,0 +1,4 @@
> +/* { dg-do-preprocess } */
> +/* { dg-options "-mabi=lp64d -fsanitize=address" } */
> +
> +/* Tests whether the compiler supports compile option '-
> fsanitize=address'. */
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-09-07 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 7:39 Lulu Cheng
2022-09-07 8:02 ` Xi Ruoyao [this message]
2022-09-07 9:12 ` [commited PATCH " Lulu Cheng
2022-09-07 9:58 ` [PATCH " Martin Liška
2022-09-07 10:01 ` Lulu Cheng
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=886a2abd8dfdaaf82ca6c2445f5ecb584121987f.camel@xry111.site \
--to=xry111@xry111.site \
--cc=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--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).