public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lh_mouse at 126 dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99234] [10/11 regression] wrong result for 1.0/3.0 with -O2 -fno-omit-frame-pointer -frounding-math Date: Fri, 26 Feb 2021 06:00:51 +0000 [thread overview] Message-ID: <bug-99234-4-CpU4Hirukx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99234-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99234 --- Comment #14 from Liu Hao <lh_mouse at 126 dot com> --- Created attachment 50259 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50259&action=edit a much simpler testcase Added a much simpler testcase. `xmm6` is set to `123.456`, and an exception is thrown and caught, and `xmm6` is copied back into a `double` and printed. With GCC 10.2.1 a garbage value is output. The bug goes away if the `throw` is commented out.
next prev parent reply other threads:[~2021-02-26 6:00 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-24 1:07 [Bug c++/99234] New: Regression: wrong result for 1.0/3.0 when -fno-omit-frame-pointer -frounding-math used together vz-gcc at zeitlins dot org 2021-02-24 15:54 ` [Bug target/99234] " jakub at gcc dot gnu.org 2021-02-24 16:19 ` vz-gcc at zeitlins dot org 2021-02-24 16:19 ` vz-gcc at zeitlins dot org 2021-02-24 16:23 ` vz-gcc at zeitlins dot org 2021-02-24 16:25 ` vz-gcc at zeitlins dot org 2021-02-25 8:56 ` jakub at gcc dot gnu.org 2021-02-25 9:34 ` ebotcazou at gcc dot gnu.org 2021-02-25 9:36 ` [Bug target/99234] [10/11 regression] wrong result for 1.0/3.0 with -O2 -fno-omit-frame-pointer -frounding-math ebotcazou at gcc dot gnu.org 2021-02-25 9:36 ` ebotcazou at gcc dot gnu.org 2021-02-25 12:07 ` jyong at gcc dot gnu.org 2021-02-25 12:35 ` ebotcazou at gcc dot gnu.org 2021-02-25 14:25 ` lh_mouse at 126 dot com 2021-02-25 18:18 ` ebotcazou at gcc dot gnu.org 2021-02-26 0:36 ` ebotcazou at gcc dot gnu.org 2021-02-26 6:00 ` lh_mouse at 126 dot com [this message] 2021-02-26 8:27 ` lh_mouse at 126 dot com 2021-02-26 9:17 ` ebotcazou at gcc dot gnu.org 2021-02-26 10:18 ` jakub at gcc dot gnu.org 2021-02-26 11:04 ` lh_mouse at 126 dot com 2021-03-01 6:59 ` cvs-commit at gcc dot gnu.org 2021-03-01 7:00 ` cvs-commit at gcc dot gnu.org 2021-03-01 7:12 ` cvs-commit at gcc dot gnu.org 2021-03-01 7:13 ` ebotcazou at gcc dot gnu.org 2021-03-01 11:49 ` vz-gcc at zeitlins dot org 2021-03-03 11:30 ` cvs-commit at gcc dot gnu.org 2021-03-03 11:31 ` cvs-commit at gcc dot gnu.org 2021-03-03 11:34 ` cvs-commit at gcc dot gnu.org 2021-05-05 20:55 ` cvs-commit at gcc dot gnu.org 2021-05-05 20:56 ` cvs-commit at gcc dot gnu.org 2021-05-05 20:58 ` cvs-commit at gcc dot gnu.org 2021-05-05 21:01 ` cvs-commit 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-99234-4-CpU4Hirukx@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: linkBe 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).