public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/103008] poor inlined builtin_fmod on x86_64 Date: Sun, 31 Oct 2021 20:05:22 +0000 [thread overview] Message-ID: <bug-103008-4-HgB3F6Y4Wx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103008-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103008 Uroš Bizjak <ubizjak at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2021-10-31 Ever confirmed|0 |1 --- Comment #6 from Uroš Bizjak <ubizjak at gmail dot com> --- Please see PR29852. The only way to avoid the libcall in 2006 was to inline the x87 version also for SSE math. Nowadays a (generic) arithmetic sequence can be provided and x87 fmod builtins can be enabled for x87 math only with: diff --git a/gcc/config/i386/i386.md b/gcc/config/i386/i386.md index e733a40fc90..ed818232ae7 100644 --- a/gcc/config/i386/i386.md +++ b/gcc/config/i386/i386.md @@ -17378,6 +17378,8 @@ (use (match_operand:MODEF 1 "general_operand")) (use (match_operand:MODEF 2 "general_operand"))] "TARGET_USE_FANCY_MATH_387 + && (!(SSE_FLOAT_MODE_P (<MODE>mode) && TARGET_SSE_MATH) + || TARGET_MIX_SSE_I387) && flag_finite_math_only" { rtx (*gen_truncxf) (rtx, rtx);
next prev parent reply other threads:[~2021-10-31 20:05 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-30 18:51 [Bug target/103008] New: " fx at gnu dot org 2021-10-30 18:52 ` [Bug target/103008] " fx at gnu dot org 2021-10-30 18:55 ` fx at gnu dot org 2021-10-30 18:56 ` fx at gnu dot org 2021-10-30 20:15 ` fx at gnu dot org 2021-10-30 20:39 ` anlauf at gcc dot gnu.org 2021-10-31 20:05 ` ubizjak at gmail dot com [this message] 2021-11-01 8:23 ` ubizjak at gmail dot com 2022-02-10 14:18 ` rguenth at gcc dot gnu.org 2022-02-10 14:22 ` rguenth at gcc dot gnu.org 2022-02-10 18:09 ` ubizjak at gmail dot com 2022-02-10 20:50 ` joseph at codesourcery dot com 2022-02-11 7:59 ` rguenth at gcc dot gnu.org 2022-02-11 15:47 ` ubizjak at gmail dot com 2022-02-12 22:07 ` ubizjak at gmail dot com 2022-02-13 21:00 ` Dave.Love at manchester dot ac.uk 2022-02-14 7:12 ` rguenther at suse dot de 2022-02-14 7:35 ` 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-103008-4-HgB3F6Y4Wx@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).