public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fx at gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/97142] __builtin_fmod not optimized on POWER Date: Mon, 21 Sep 2020 14:47:14 +0000 [thread overview] Message-ID: <bug-97142-4-5i0YxXeQoG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97142-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97142 --- Comment #5 from Dave Love <fx at gnu dot org> --- I meant to show that x86_64 expands the built in fmod too. (I wasn't sure whether "inline" was the right term, as it seems not to be done by -finline-functions.) Yes, xlf -O3 (?) and above imlies something like -ffast-math. xlf also does vectorized maths functions, but I don't think the speed of libm is as relevant as not calling out to it. (Nothing leapt out from profiles for the rest of that set to suggest other builtins are similar, but I haven't examined them closely.) I'll attach the assembler, which there's an awful lot of compared with x86_64.
next prev parent reply other threads:[~2020-09-21 14:47 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-21 10:57 [Bug target/97142] New: " fx at gnu dot org 2020-09-21 11:24 ` [Bug target/97142] " rguenth at gcc dot gnu.org 2020-09-21 11:26 ` rguenth at gcc dot gnu.org 2020-09-21 14:42 ` bergner at gcc dot gnu.org 2020-09-21 14:45 ` fx at gnu dot org 2020-09-21 14:47 ` fx at gnu dot org [this message] 2020-09-21 17:52 ` segher at gcc dot gnu.org 2020-09-21 18:10 ` bergner at gcc dot gnu.org 2020-09-21 19:33 ` segher at gcc dot gnu.org 2020-09-21 21:54 ` bergner at gcc dot gnu.org 2021-04-13 6:24 ` luoxhu at gcc dot gnu.org 2021-04-13 16:26 ` segher at gcc dot gnu.org 2021-05-27 0:54 ` luoxhu at gcc dot gnu.org 2021-09-02 22:05 ` bergner at gcc dot gnu.org 2021-09-02 22:38 ` segher at gcc dot gnu.org 2021-09-03 2:33 ` luoxhu at gcc dot gnu.org 2021-09-07 1:29 ` cvs-commit at gcc dot gnu.org 2021-09-07 17:58 ` bergner at gcc dot gnu.org 2021-09-07 19:34 ` segher at gcc dot gnu.org 2021-09-07 21:20 ` segher at gcc dot gnu.org 2021-09-14 5:33 ` cvs-commit at gcc dot gnu.org 2021-09-14 5:34 ` cvs-commit at gcc dot gnu.org 2021-09-14 5:36 ` luoxhu 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-97142-4-5i0YxXeQoG@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).