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/108845] Unnecessary signed integer overflow checks
Date: Sat, 18 Feb 2023 19:48:28 +0000	[thread overview]
Message-ID: <bug-108845-4-UlCVBszS9u@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108845-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I'm not convinced it is a good idea.
Sure, in the above case it is obvious it will never trigger, but if we say use
ranger to decide if the operation can or can't overflow, then VRP is in many
cases based on assumptions which only hold for valid code, but sanitizers
actually want to diagnose invalid code.

  parent reply	other threads:[~2023-02-18 19:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-18 19:24 [Bug sanitizer/108845] New: " qrzhang at gatech dot edu
2023-02-18 19:34 ` [Bug sanitizer/108845] " pinskia at gcc dot gnu.org
2023-02-18 19:48 ` jakub at gcc dot gnu.org [this message]
2023-02-18 20:27 ` qrzhang at gatech dot edu
2023-02-19  3:55 ` qrzhang at gatech dot edu

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-108845-4-UlCVBszS9u@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).