public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kewen.Lin" <linkw@linux.ibm.com>
To: Qingnan Duan <Qingnan.Duan@microsoft.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: GCC address sanitizer - supported architecture
Date: Thu, 24 Dec 2020 16:48:53 +0800	[thread overview]
Message-ID: <2c875371-3d7f-4698-2024-597352665af8@linux.ibm.com> (raw)
In-Reply-To: <TYZP153MB0448789F2DB7DD10FAF71CE781DD9@TYZP153MB0448.APCP153.PROD.OUTLOOK.COM>

Hi Qingnan,

on 2020/12/24 上午11:23, Qingnan Duan via Gcc-help wrote:
> Hi everyone,
> I was looking at this page Instrumentation Options (Using the GNU Compiler Collection (GCC))<https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html> and it says "-fsanitize=address" is only supported on AArch64. However, I was able to compile my code on x86-64 CPU with -fsanitize=address flag.
> 

I think the part "Note that the only target this option is currently supported on is AArch64. "
is specific for option “-fsanitize=hwaddress” not for option "-fsanitize=address".

Only aarch64 port re-defines TARGET_MEMTAG_CAN_TAG_ADDRESSES which is used for -fsanitize=hwaddress,
that matches the wordings.

By the way, I also felt a bit confused without digging, not sure whether it's confusing from
native speaker's perspective.  If yes, maybe it's worth to revise it somehow.  :)

> Is the document out-of-date? Or, does it mean the result of ASan is not guaranteed on any platform other than AArch64?
> Thanks in advance for your help!
> 
> Best regards,
> Qingnan Duan
> 

BR,
Kewen

  reply	other threads:[~2020-12-24  8:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-24  3:23 Qingnan Duan
2020-12-24  8:48 ` Kewen.Lin [this message]
2020-12-24 10:10   ` Jonathan Wakely
2020-12-24 12:06     ` Kewen.Lin
2020-12-24 12:28       ` Jonathan Wakely
2020-12-25  7:37         ` [EXTERNAL] " Qingnan Duan

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=2c875371-3d7f-4698-2024-597352665af8@linux.ibm.com \
    --to=linkw@linux.ibm.com \
    --cc=Qingnan.Duan@microsoft.com \
    --cc=gcc-help@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).