public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/34678] Optimization generates incorrect code with -frounding-math option (#pragma STDC FENV_ACCESS not implemented) Date: Sat, 07 Jan 2023 11:14:47 +0000 [thread overview] Message-ID: <bug-34678-4-TBr5628b6W@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-34678-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34678 --- Comment #48 from Thomas Koenig <tkoenig at gcc dot gnu.org> --- Clang gets this right, even without the pragma; the original test case is compiled to pushq %r14 pushq %rbx subq $24, %rsp movq %rsi, %r14 movq %rdi, %rbx movsd %xmm1, 16(%rsp) # 8-byte Spill movsd %xmm0, 8(%rsp) # 8-byte Spill movl $1024, %edi # imm = 0x400 callq fesetround@PLT movsd 8(%rsp), %xmm0 # 8-byte Reload divsd 16(%rsp), %xmm0 # 8-byte Folded Reload movsd %xmm0, (%rbx) movl $2048, %edi # imm = 0x800 callq fesetround@PLT movsd 8(%rsp), %xmm0 # 8-byte Reload divsd 16(%rsp), %xmm0 # 8-byte Folded Reload movsd %xmm0, (%r14) addq $24, %rsp popq %rbx popq %r14 retq
next prev parent reply other threads:[~2023-01-07 11:14 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-34678-4@http.gcc.gnu.org/bugzilla/> 2010-10-26 10:33 ` paolo.carlini at oracle dot com 2011-02-08 2:02 ` pinskia at gcc dot gnu.org 2011-04-01 19:22 ` pinskia at gcc dot gnu.org 2013-11-11 9:30 ` nmm1 at cam dot ac.uk 2013-11-11 13:37 ` vincent-gcc at vinc17 dot net 2013-11-11 16:38 ` joseph at codesourcery dot com 2013-11-11 17:32 ` nmm1 at cam dot ac.uk 2014-01-10 11:40 ` vincent-gcc at vinc17 dot net 2014-01-14 14:58 ` vincent-gcc at vinc17 dot net 2014-01-14 15:13 ` nmm1 at cam dot ac.uk 2014-01-14 15:52 ` vincent-gcc at vinc17 dot net 2014-01-14 17:22 ` nmm1 at cam dot ac.uk 2014-01-14 23:16 ` vincent-gcc at vinc17 dot net 2014-02-16 10:03 ` jackie.rosen at hushmail dot com 2020-04-16 15:35 ` vincent-gcc at vinc17 dot net 2023-01-06 17:29 ` pinskia at gcc dot gnu.org 2023-01-06 17:31 ` pinskia at gcc dot gnu.org 2023-01-06 19:29 ` tkoenig at gcc dot gnu.org 2023-01-06 22:14 ` tkoenig at gcc dot gnu.org 2023-01-07 11:14 ` tkoenig at gcc dot gnu.org [this message] 2023-01-07 12:14 ` tkoenig at gcc dot gnu.org 2008-01-04 18:56 [Bug c/34678] New: Optimization generates incorrect code with -frounding-math option merkert at comcast dot net 2008-01-05 12:08 ` [Bug middle-end/34678] Optimization generates incorrect code with -frounding-math option (#pragma STDC FENV_ACCESS not implemented) rguenth at gcc dot gnu dot org 2008-01-05 16:48 ` merkert at comcast dot net 2008-01-05 21:00 ` joseph at codesourcery dot com 2008-01-05 21:29 ` rguenth at gcc dot gnu dot org 2008-01-06 16:21 ` joseph at codesourcery dot com 2008-01-06 17:19 ` rguenth at gcc dot gnu dot org 2008-01-06 18:03 ` joseph at codesourcery dot com 2008-10-15 15:44 ` rguenth at gcc dot gnu dot org 2008-10-15 21:31 ` vincent at vinc17 dot org 2008-10-15 22:15 ` rguenth at gcc dot gnu dot org 2008-10-15 22:35 ` vincent at vinc17 dot org 2008-10-16 9:46 ` rguenth at gcc dot gnu dot org 2008-10-16 11:58 ` merkert at comcast dot net 2008-10-16 14:21 ` vincent at vinc17 dot org 2008-10-16 16:40 ` joseph at codesourcery dot com 2008-10-16 17:41 ` vincent at vinc17 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-34678-4-TBr5628b6W@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).