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/112606] [14 Regression] powerpc64le-linux-gnu: 'FAIL: gcc.target/powerpc/p8vector-fp.c scan-assembler xsnabsdp' Date: Wed, 10 Jan 2024 05:09:36 +0000 [thread overview] Message-ID: <bug-112606-4-prQY7i9Twf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112606-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112606 --- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>: https://gcc.gnu.org/g:cf5f6a048e376ab0d2f7bc283c158605e1166061 commit r14-7090-gcf5f6a048e376ab0d2f7bc283c158605e1166061 Author: Kewen Lin <linkw@linux.ibm.com> Date: Tue Jan 9 23:06:12 2024 -0600 rs6000: Make copysign (x, -1) back to -abs (x) for IEEE128 float [PR112606] I noticed that commit r14-6192 can't help PR112606 #c3 as it only takes care of SF/DF but TF/KF can still suffer the issue. Similar to commit r14-6192, this patch is to take care of copysign<mode>3 with IEEE128 as well. PR target/112606 gcc/ChangeLog: * config/rs6000/rs6000.md (copysign<mode>3 IEEE128): Change predicate of the last argument from altivec_register_operand to any_operand. If operands[2] is CONST_DOUBLE, emit abs or neg abs depending on its sign otherwise if it doesn't satisfy altivec_register_operand, force it to REG using copy_to_mode_reg.
next prev parent reply other threads:[~2024-01-10 5:09 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-18 13:32 [Bug rtl-optimization/112606] New: " tschwinge at gcc dot gnu.org 2023-11-18 14:05 ` [Bug rtl-optimization/112606] " tnfchris at gcc dot gnu.org 2023-11-18 19:45 ` [Bug target/112606] " pinskia at gcc dot gnu.org 2023-11-24 17:59 ` jakub at gcc dot gnu.org 2023-11-28 19:43 ` seurer at gcc dot gnu.org 2023-12-05 20:40 ` cvs-commit at gcc dot gnu.org 2024-01-08 3:34 ` linkw at gcc dot gnu.org 2024-01-10 5:09 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-10 5:20 ` linkw 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-112606-4-prQY7i9Twf@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).