public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/105206] mis-optimization with -ffast-math and __builtin_powf
Date: Mon, 11 Apr 2022 19:21:52 +0000 [thread overview]
Message-ID: <bug-105206-4-DXvXgl4ygS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105206-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105206
--- Comment #4 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Mon, Apr 11, 2022 at 02:45:22PM +0000, kargl at gcc dot gnu.org wrote:
>
> This might be related to PR89125. The patch I attached to that PR has never
> found its way into the repository. I'll do some more testing later today.
>
Yep. This is related to PR89125. GCC does not use configure
to check for the availability of individual C99 libm functions.
After updating the patch in PR89125 for the *.c to *.cc migration
the patch gcc gives
foof:
.LFB3:
.cfi_startproc
mulss .LC0(%rip), %xmm0
jmp expf
.cfi_endproc
food:
.LFB4:
.cfi_startproc
mulsd .LC1(%rip), %xmm0
jmp exp
.cfi_endproc
fool:
.LFB5:
.cfi_startproc
pushq %rbp
.cfi_def_cfa_offset 16
.cfi_offset 6, -16
movq %rsp, %rbp
.cfi_def_cfa_register 6
fldt 16(%rbp)
popq %rbp
.cfi_def_cfa 7, 8
fldt .LC2(%rip)
fmulp %st, %st(1)
fldl2e
fmulp %st, %st(1)
fld %st(0)
frndint
fsubr %st, %st(1)
fxch %st(1)
f2xm1
fld1
faddp %st, %st(1)
fscale
fstp %st(1)
ret
.cfi_endproc
next prev parent reply other threads:[~2022-04-11 19:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 19:30 [Bug middle-end/105206] New: " kargl at gcc dot gnu.org
2022-04-09 19:35 ` [Bug middle-end/105206] " kargl at gcc dot gnu.org
2022-04-11 7:18 ` rguenth at gcc dot gnu.org
2022-04-11 14:45 ` kargl at gcc dot gnu.org
2022-04-11 19:21 ` sgk at troutmask dot apl.washington.edu [this message]
2022-04-11 19:24 ` [Bug target/105206] " kargl at gcc dot gnu.org
2022-04-12 6:46 ` rguenther at suse dot de
2022-04-12 17:35 ` kargl at gcc dot gnu.org
2022-04-25 7:28 ` 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-105206-4-DXvXgl4ygS@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).