public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/98437] New: confusing wording in the description of option -fsanitize=address
Date: Thu, 24 Dec 2020 11:31:03 +0000	[thread overview]
Message-ID: <bug-98437-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98437

            Bug ID: 98437
           Summary: confusing wording in the description of option
                    -fsanitize=address
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
          Assignee: unassigned at gcc dot gnu.org
          Reporter: linkw at gcc dot gnu.org
  Target Milestone: ---

As Qingnan's question[1] in the mail list gcc-help, the last part in the
current description of option -fsanitize=address looks confusing. Manual users
are easy to misunderstand the below wording

   "Note that the only target this option is currently supported on is
AArch64." 

is specific for option -fsanitize=address.  But it's intended to note the
option -fsanitize=hwaddress which can not be combined with option
-fsanitize=address.

Both hook TARGET_MEMTAG_CAN_TAG_ADDRESSES and commit r11-5375 shows only option
-fsanitize=hwaddress is aarch64 specific.

[1] https://gcc.gnu.org/pipermail/gcc-help/2020-December/139745.html

             reply	other threads:[~2020-12-24 11:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-24 11:31 linkw at gcc dot gnu.org [this message]
2021-01-04  7:21 ` [Bug other/98437] " marxin at gcc dot gnu.org
2021-01-04 12:06 ` cvs-commit at gcc dot gnu.org
2021-01-04 12:38 ` marxin at gcc dot gnu.org

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=bug-98437-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).