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/101985] vec_cpsgn parameter order Date: Tue, 12 Oct 2021 22:39:25 +0000 [thread overview] Message-ID: <bug-101985-4-FaOhlQGPis@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101985-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101985 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by William Schmidt <wschmidt@gcc.gnu.org>: https://gcc.gnu.org/g:76ba473b99c30ddec6171840a76292d6d4b67e7c commit r12-4361-g76ba473b99c30ddec6171840a76292d6d4b67e7c Author: Bill Schmidt <wschmidt@linux.ibm.com> Date: Tue Oct 12 17:37:16 2021 -0500 rs6000: Fix vec_cpsgn parameter order (PR101985) The vec_cpsgn built-in function API differs in argument order from the copysign<mode>3 convention. Currently that pattern is incorrctly used to implement vec_cpsgn. Fix that by reversing the operand order of the builtin while leaving the existing pattern in place to implement copysignf for vector modes. Part of the fix when using the new built-in support requires an adjustment to a pending patch that replaces much of altivec.h with an automatically generated file. Also fix a bug in the new built-in overload infrastructure where we were using the VSX form of the VEC_COPYSIGN built-in when we should default to the VMX form. 2021-10-12 Bill Schmidt <wschmidt@linux.ibm.com> gcc/ PR target/101985 * config/rs6000/altivec.h (vec_cpsgn): Swap operand order. * config/rs6000/rs6000-overload.def (VEC_COPYSIGN): Use SKIP to avoid generating an automatic #define of vec_cpsgn. Use the correct built-in for V4SFmode that doesn't depend on VSX. gcc/testsuite/ PR target/101985 * gcc.target/powerpc/pr101985-1.c: New. * gcc.target/powerpc/pr101985-2.c: New.
next prev parent reply other threads:[~2021-10-12 22:39 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-19 18:36 [Bug c/101985] New: " simb611alt at gmail dot com 2021-09-23 16:40 ` [Bug target/101985] " wschmidt at gcc dot gnu.org 2021-09-24 15:33 ` wschmidt at gcc dot gnu.org 2021-09-28 15:28 ` wschmidt at gcc dot gnu.org 2021-09-29 19:33 ` simb611alt at gmail dot com 2021-10-12 22:39 ` cvs-commit at gcc dot gnu.org [this message] 2021-10-12 22:43 ` wschmidt at gcc dot gnu.org 2021-11-23 21:26 ` cvs-commit at gcc dot gnu.org 2021-11-23 22:40 ` cvs-commit at gcc dot gnu.org 2021-11-23 23:06 ` cvs-commit at gcc dot gnu.org 2021-11-23 23:07 ` wschmidt at gcc dot gnu.org 2022-11-17 21:02 ` mark.j.abraham at gmail dot com
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-101985-4-FaOhlQGPis@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).