public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Kwok Yeung <kcy@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/omp/gcc-12] amdgcn: Fix expansion of builtin for vector fabs operation Date: Wed, 2 Nov 2022 00:37:29 +0000 (GMT) [thread overview] Message-ID: <20221102003740.87D573858D35@sourceware.org> (raw) https://gcc.gnu.org/g:a3c04a367a90597e729874ccadb9ce004d76f515 commit a3c04a367a90597e729874ccadb9ce004d76f515 Author: Kwok Cheung Yeung <kcy@codesourcery.com> Date: Tue Nov 1 23:05:44 2022 +0000 amdgcn: Fix expansion of builtin for vector fabs operation 2022-11-01 Kwok Cheung Yeung <kcy@codesourcery.com> * config/gcn/gcn.cc (gcn_expand_builtin_1): Fix expansion of GCN_BUILTIN_FABSV. Diff: --- gcc/ChangeLog.omp | 5 +++++ gcc/config/gcn/gcn.cc | 4 +--- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/gcc/ChangeLog.omp b/gcc/ChangeLog.omp index b636fa5baf4..467a2497fb2 100644 --- a/gcc/ChangeLog.omp +++ b/gcc/ChangeLog.omp @@ -1,3 +1,8 @@ +2022-11-01 Kwok Cheung Yeung <kcy@codesourcery.com> + + * config/gcn/gcn.cc (gcn_expand_builtin_1): Fix expansion of + GCN_BUILTIN_FABSV. + 2022-11-01 Marcel Vollweiler <marcel@codesourcery.com> * omp-expand-metadirective.cc (omp_expand_metadirective): Add already diff --git a/gcc/config/gcn/gcn.cc b/gcc/config/gcn/gcn.cc index d24e7aec9ef..08dd3d618c6 100644 --- a/gcc/config/gcn/gcn.cc +++ b/gcc/config/gcn/gcn.cc @@ -4365,13 +4365,11 @@ gcn_expand_builtin_1 (tree exp, rtx target, rtx /*subtarget */ , { if (ignore) return target; - rtx exec = get_exec (-1); rtx arg = force_reg (V64DFmode, expand_expr (CALL_EXPR_ARG (exp, 0), NULL_RTX, V64DFmode, EXPAND_NORMAL)); - emit_insn (gen_absv64df2_exec - (target, arg, gcn_gen_undef (V64DFmode), exec)); + emit_insn (gen_absv64df2 (target, arg)); return target; } case GCN_BUILTIN_LDEXPVF:
reply other threads:[~2022-11-02 0:37 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221102003740.87D573858D35@sourceware.org \ --to=kcy@gcc.gnu.org \ --cc=gcc-cvs@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).