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/110556] Floating point exception with specific optimizations
Date: Thu, 06 Jul 2023 01:38:55 +0000	[thread overview]
Message-ID: <bug-110556-4-MBHBPHtE6m@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110556-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to CTC from comment #6)
> (In reply to Andrew Pinski from comment #4)
> > Reducing this but it is taking a little longer as I get to the case where we
> > get undefined code on accident so I need to test it using
> > -fsanitize=undefined,address also.
> 
> For the unreduced program and optimizations, I test it with
> -fno-strict-aliasing -fwrapv -fno-aggressive-loop-optimizations and
> -fsanitize=undefined. Both of them got floating point exception too.
> 
> I reduced the program with -fsanitize=undefined. The result doesn't get
> floating point exception. But its return value is not 0.

That is still undefined code ... as the return value of the app is not
specified in the source.

  parent reply	other threads:[~2023-07-06  1:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05  9:19 [Bug c/110556] New: " 19373742 at buaa dot edu.cn
2023-07-05  9:20 ` [Bug c/110556] " 19373742 at buaa dot edu.cn
2023-07-05 10:30 ` 19373742 at buaa dot edu.cn
2023-07-05 17:54 ` pinskia at gcc dot gnu.org
2023-07-05 21:28 ` [Bug middle-end/110556] " pinskia at gcc dot gnu.org
2023-07-05 22:32 ` pinskia at gcc dot gnu.org
2023-07-06  1:36 ` 19373742 at buaa dot edu.cn
2023-07-06  1:38 ` pinskia at gcc dot gnu.org [this message]
2023-07-06  5:30 ` pinskia at gcc dot gnu.org
2023-07-06  5:42 ` [Bug middle-end/110556] [12/13/14 Regression] " pinskia at gcc dot gnu.org
2023-07-06  8:15 ` [Bug tree-optimization/110556] [12/13/14 Regression] division of INT_MIN and -1 happening incorrectly with -fno-delete-dead-exceptions -fnon-call-exceptions rguenth at gcc dot gnu.org
2023-07-06 11:45 ` rguenth at gcc dot gnu.org
2023-07-06 13:24 ` cvs-commit at gcc dot gnu.org
2023-07-07 12:07 ` [Bug tree-optimization/110556] [12 " cvs-commit at gcc dot gnu.org
2023-11-27 11:35 ` cvs-commit at gcc dot gnu.org
2023-11-27 11:36 ` 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-110556-4-MBHBPHtE6m@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).