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 target/99621] [8/9/10/11 Regression] Wrong code with -m32 -O1 -fcaller-saves -fexpensive-optimizations since g:058e97ecf33ad0dfd926b3876a4bcf59ac9556ff Date: Wed, 17 Mar 2021 08:12:54 +0000 [thread overview] Message-ID: <bug-99621-4-hGKS4SCYCD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99621-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99621 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Are you sure this just isn't an excess precision problem in all the floating point calculations? -mfpmath=sse -msse2 makes it go away, -fexcess-precision=standard too. Why is 5167 bad but both 4806 and 5749 I'm getting with other options are good? When I try it on with -m64, at -O0 I get 7019, at -O1 and higher 4806.
next prev parent reply other threads:[~2021-03-17 8:12 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-17 0:11 [Bug c/99621] New: [5-11 REGRESSION] [bisected to 058e97ecf33ad0dfd926b3876a4bcf59ac9556ff] regression with -m32 -O1 -fcaller-saves -fexpensive-optimizations williambader at hotmail dot com 2021-03-17 0:14 ` [Bug rtl-optimization/99621] " williambader at hotmail dot com 2021-03-17 0:20 ` [Bug target/99621] [8,9,10,11 " pinskia at gcc dot gnu.org 2021-03-17 7:22 ` [Bug target/99621] [8/9/10/11 " marxin at gcc dot gnu.org 2021-03-17 7:32 ` [Bug target/99621] [8/9/10/11 Regression] Wrong code with -m32 -O1 -fcaller-saves -fexpensive-optimizations since g:058e97ecf33ad0dfd926b3876a4bcf59ac9556ff marxin at gcc dot gnu.org 2021-03-17 8:12 ` jakub at gcc dot gnu.org [this message] 2021-03-17 8:14 ` williambader at hotmail dot com 2021-03-17 8:27 ` jakub at gcc dot gnu.org 2021-03-17 8:32 ` williambader at hotmail dot com 2021-03-17 8:44 ` williambader at hotmail dot com 2021-03-17 8:56 ` marxin at gcc dot gnu.org 2021-03-17 9:03 ` williambader at hotmail dot com 2021-03-17 9:06 ` marxin at gcc dot gnu.org 2021-03-17 9:19 ` williambader at hotmail dot com 2021-03-17 9:23 ` marxin at gcc dot gnu.org 2021-03-17 9:35 ` williambader at hotmail dot com 2021-03-17 9:37 ` marxin at gcc dot gnu.org 2021-03-17 9:41 ` williambader at hotmail dot com 2021-03-17 9:44 ` marxin at gcc dot gnu.org 2021-03-17 9:58 ` williambader at hotmail dot com 2021-03-17 10:02 ` marxin at gcc dot gnu.org 2021-03-17 10:06 ` jakub at gcc dot gnu.org 2021-03-17 10:08 ` marxin at gcc dot gnu.org 2021-03-17 10:11 ` marxin at gcc dot gnu.org 2021-03-17 10:12 ` jakub at gcc dot gnu.org 2021-03-17 10:23 ` williambader at hotmail dot com
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-99621-4-hGKS4SCYCD@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).