public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/35412] Correctness with -ftrapv depended on libcall notes
Date: Sun, 05 Mar 2023 20:03:30 +0000	[thread overview]
Message-ID: <bug-35412-4-sGWoEK344L@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-35412-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to dingd from comment #10)
> I wonder what's the status of this bug. It has been 15 years.

It still is a bug.

> 
> As far as I know, Clang doesn't have this bug, so it should not be
> impossible to implement.

Yes clang/LLVM does not have this bug because the internals of them and GCC are
way different.

> 
> And, does -fsantize=undefined really provides the same functionality of this
> switch? I have always assumed that santizers are not to be used in
> production, right?

See PR 101521 for some ideas of how to implement this using the same
infrastructure as -fsantize=undefined .

  parent reply	other threads:[~2023-03-05 20:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-35412-4@http.gcc.gnu.org/bugzilla/>
2023-03-05 14:20 ` ntysdd at qq dot com
2023-03-05 20:03 ` pinskia at gcc dot gnu.org [this message]
2008-02-29 23:24 [Bug middle-end/35412] New: Correctness with -ftrapv depends " steven at gcc dot gnu dot org
2008-06-25 11:55 ` [Bug middle-end/35412] Correctness with -ftrapv depended " rguenth at gcc dot gnu dot org
2008-07-04 19:43 ` jsm28 at gcc dot gnu dot org
2009-04-14 20:00 ` pinskia at gcc dot gnu dot org
2009-04-14 20:08 ` jv244 at cam dot ac dot uk
2009-05-14 10:55 ` rguenth at gcc dot gnu dot 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-35412-4-sGWoEK344L@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).