On Thu, 24 Dec 2020, 12:06 Kewen.Lin, <linkw@xxxxxxxxxxxxx> wrote: > > on 2020/12/24 下午6:10, Jonathan Wakely wrote: > > On Thu, 24 Dec 2020, 08:50 Kewen.Lin via Gcc-help, <gcc-help@xxxxxxxxxxx > <mailto:gcc-help@xxxxxxxxxxx>> wrote: > > > > 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 < > 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. :) > > > > > > Yes, the documentation should be fixed. As currently written it's > incorrect. > > > > Could you please file a bug? > > > > Hi Jonathan, > > Thanks for confirming this. PR98437 was opened as you suggested. > Great, thanks. > > >
