public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/98730] vceqzq_p64 does not generate vceq with immediate 0 Date: Thu, 21 Jan 2021 17:37:18 +0000 [thread overview] Message-ID: <bug-98730-4-LtTBgG44qC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98730-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98730 --- Comment #4 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> --- Hmm, yeah, looks like it might be a cost issue then. arm_rtx_costs_internal seems to give CONST_VECTOR a cost of 1 or 4 instructions, whereas a zero CONST_VECTOR is free in this context. Although that should be fixed, another approach would be to lower vget_high_* and vget_low_* at the gimple level if the argument is a constant.
next prev parent reply other threads:[~2021-01-21 17:37 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-18 14:32 [Bug target/98730] New: " clyon at gcc dot gnu.org 2021-01-18 14:33 ` [Bug target/98730] " clyon at gcc dot gnu.org 2021-01-21 15:08 ` rsandifo at gcc dot gnu.org 2021-01-21 15:39 ` clyon at gcc dot gnu.org 2021-01-21 17:37 ` rsandifo at gcc dot gnu.org [this message] 2021-01-28 17:56 ` cvs-commit at gcc dot gnu.org 2021-01-28 17:58 ` clyon 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-98730-4-LtTBgG44qC@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).