public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wuz73 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/98220] New: LTO causes floating point exception
Date: Thu, 10 Dec 2020 08:14:13 +0000	[thread overview]
Message-ID: <bug-98220-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 98220
           Summary: LTO causes floating point exception
           Product: gcc
           Version: 9.3.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: wuz73 at hotmail dot com
  Target Milestone: ---

Created attachment 49726
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49726&action=edit
test case for LTO crash

In the attached test case, if -flto is turned on then the executable crashes
with floating point exception even though I didn't use any floating point. 
Without -flto everything was fine.

             reply	other threads:[~2020-12-10  8:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-10  8:14 wuz73 at hotmail dot com [this message]
2020-12-10  8:19 ` [Bug c++/98220] " pinskia at gcc dot gnu.org
2020-12-10  8:21 ` wuz73 at hotmail dot com
2020-12-10  8:22 ` marxin at gcc dot gnu.org
2020-12-10  8:30 ` wuz73 at hotmail dot com
2020-12-10  9:03 ` marxin at gcc dot gnu.org
2020-12-10  9:14 ` marxin at gcc dot gnu.org
2020-12-10  9:16 ` marxin at gcc dot gnu.org
2020-12-10 10:15 ` redi at gcc dot gnu.org
2020-12-10 14:07 ` wuz73 at hotmail dot com
2020-12-10 14:23 ` redi at gcc dot gnu.org
2020-12-10 15:53 ` wuz73 at hotmail dot com
2020-12-10 16:12 ` redi 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-98220-4@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).