public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "i at maskray dot me" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/109489] [ubsan] Support -fsanitize-trap=
Date: Mon, 17 Apr 2023 04:22:58 +0000	[thread overview]
Message-ID: <bug-109489-4-Ghyr4bMvHQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109489-4@http.gcc.gnu.org/bugzilla/>

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

Fangrui Song <i at maskray dot me> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from Fangrui Song <i at maskray dot me> ---
This has been implemented in
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=2c7cfc7b418564a2f1f0e7a5b38dec7013ba5e18
(2022-06). Sorry that I did not check the trunk GCC.

https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html says "The
-fsanitize-undefined-trap-on-error option is deprecated equivalent of
-fsanitize-trap=all." (as expected).

  parent reply	other threads:[~2023-04-17  4:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 18:07 [Bug c/109489] New: " i at maskray dot me
2023-04-12 18:09 ` [Bug sanitizer/109489] " pinskia at gcc dot gnu.org
2023-04-17  4:22 ` i at maskray dot me [this message]
2023-04-17  4:59 ` pinskia 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-109489-4-Ghyr4bMvHQ@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).