public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/64821] [AArch64] Improve target folding for vsqrt_f64 intrinsic Date: Sun, 23 Jan 2022 22:18:36 +0000 [thread overview] Message-ID: <bug-64821-4-GeYSW6GOct@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64821-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64821 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>: https://gcc.gnu.org/g:cbcf4a50fa21abd7a4a50a7ce47ada80b115febc commit r12-6824-gcbcf4a50fa21abd7a4a50a7ce47ada80b115febc Author: Andrew Pinski <apinski@marvell.com> Date: Sun Jan 9 23:39:31 2022 -0800 [aarch64/64821]: Simplify __builtin_aarch64_sqrt* into internal function .SQRT. This is a simple patch which simplifies the __builtin_aarch64_sqrt* builtins into the internal function SQRT which allows for constant folding and other optimizations at the gimple level. It was originally suggested we do to __builtin_sqrt just for __builtin_aarch64_sqrtdf when -fno-math-errno but since r6-4969-g686ee9719a4 we have the internal function SQRT which does the same so it makes we don't need to check -fno-math-errno either now. Applied as approved after bootstrapped and tested on aarch64-linux-gnu with no regressions. PR target/64821 gcc/ChangeLog: * config/aarch64/aarch64-builtins.cc (aarch64_general_gimple_fold_builtin): Handle __builtin_aarch64_sqrt* and simplify into SQRT internal function. gcc/testsuite/ChangeLog: * gcc.target/aarch64/vsqrt-1.c: New test. * gcc.target/aarch64/vsqrt-2.c: New test.
next prev parent reply other threads:[~2022-01-23 22:18 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-27 9:43 [Bug target/64821] New: " ktkachov at gcc dot gnu.org 2015-02-16 0:42 ` [Bug target/64821] " pinskia at gcc dot gnu.org 2022-01-10 1:05 ` pinskia at gcc dot gnu.org 2022-01-10 1:19 ` pinskia at gcc dot gnu.org 2022-01-10 7:15 ` pinskia at gcc dot gnu.org 2022-01-10 7:35 ` pinskia at gcc dot gnu.org 2022-01-10 7:53 ` pinskia at gcc dot gnu.org 2022-01-10 11:35 ` pinskia at gcc dot gnu.org 2022-01-23 22:18 ` cvs-commit at gcc dot gnu.org [this message] 2022-01-23 22:19 ` pinskia 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-64821-4-GeYSW6GOct@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).