public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/102317] signed integer overflow sanitizer cannot work well with -fno-strict-overflow
Date: Tue, 14 Sep 2021 18:53:34 +0000	[thread overview]
Message-ID: <bug-102317-4-JsqHiip8bq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102317-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The optimize attribute is how different options are represented in LTO
compilation, so it grew over years from perhaps initial debugging use to
something that is used everywhere.  And we definitely aren't going to add
further and further attributes that match just a small subset of the optimize
and/or target attributes, especially when they'd need to use the same
infrastructure under the hood anyway.
If you don't want to use optimize attribute, there is always the option to just
do the arithmetics in unsigned types in the few selected functions where you
don't want the sanitization, and if you really want use -fwrapv-pointer
together with -fsanitize=integer-signed-overflow and throw away
-fno-strict-overflow.

  parent reply	other threads:[~2021-09-14 18:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13 21:31 [Bug sanitizer/102317] New: " qinzhao at gcc dot gnu.org
2021-09-13 21:35 ` [Bug sanitizer/102317] " pinskia at gcc dot gnu.org
2021-09-13 21:41 ` qinzhao at gcc dot gnu.org
2021-09-13 21:45 ` pinskia at gcc dot gnu.org
2021-09-13 21:57 ` jakub at gcc dot gnu.org
2021-09-13 22:01 ` qing.zhao at oracle dot com
2021-09-14  5:55 ` jakub at gcc dot gnu.org
2021-09-14 15:57 ` kees at outflux dot net
2021-09-14 16:04 ` jakub at gcc dot gnu.org
2021-09-14 18:36 ` kees at outflux dot net
2021-09-14 18:53 ` jakub at gcc dot gnu.org [this message]
2021-09-23 22:58 ` kees at outflux dot net
2023-09-07 20:53 ` qinzhao at gcc dot gnu.org
2024-02-15  1:22 ` i at maskray dot me

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-102317-4-JsqHiip8bq@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).