public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/94307] Provide a way to declare the *SAN exception handler -fsanitize-undefined-trap-on-error
Date: Wed, 25 Mar 2020 09:28:59 +0000 [thread overview]
Message-ID: <bug-94307-4-PS5EUcSQmF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94307-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94307
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #1)
> But isn't the default without -fsanitize-undefined-trap-on-error already
> calling
> a library routine that the kernel could override?
They don't want to implement all the:
call __ubsan_handle_add_overflow
call __ubsan_handle_divrem_overflow
call __ubsan_handle_dynamic_type_cache_miss
call __ubsan_handle_invalid_builtin
call __ubsan_handle_load_invalid_value
call __ubsan_handle_mul_overflow
call __ubsan_handle_negate_overflow
call __ubsan_handle_nonnull_arg
call __ubsan_handle_out_of_bounds
call __ubsan_handle_pointer_overflow
call __ubsan_handle_shift_out_of_bounds
call __ubsan_handle_sub_overflow
call __ubsan_handle_type_mismatch_v1
...
run-time entry points.
next prev parent reply other threads:[~2020-03-25 9:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 18:17 [Bug sanitizer/94307] New: " kees at outflux dot net
2020-03-25 7:35 ` [Bug sanitizer/94307] " rguenth at gcc dot gnu.org
2020-03-25 9:28 ` marxin at gcc dot gnu.org
2020-03-25 9:28 ` marxin at gcc dot gnu.org [this message]
2020-03-25 9:37 ` jakub at gcc dot gnu.org
2020-03-31 5:02 ` kees at outflux dot net
2020-03-31 7:45 ` marxin at gcc dot gnu.org
2020-04-06 11:23 ` marxin at gcc dot gnu.org
2020-04-20 9:31 ` marxin at gcc dot gnu.org
2020-05-15 11:32 ` marxin at gcc dot gnu.org
2020-07-28 10:24 ` marxin at gcc dot gnu.org
2021-04-27 11:38 ` jakub at gcc dot gnu.org
2021-07-28 7:04 ` rguenth 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-94307-4-PS5EUcSQmF@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).