public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/111114] RISC-V: Failed combine extend + vcond_mask when modify by vect_recog_over_widening_pattern
Date: Wed, 23 Aug 2023 17:46:50 +0000	[thread overview]
Message-ID: <bug-111114-4-1JDpDFUNyY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111114-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111114

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2023-08-23
     Ever confirmed|0                           |1
          Component|target                      |tree-optimization
                 CC|                            |pinskia at gcc dot gnu.org

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
There is a match pattern which handles the case where the convert (cast) will
fold both sides of the vec_cond now (since r14-3337-g70c50c87273d94).

  vect__5.14_56 = .MASK_LEN_LOAD (vectp_a.12_54, 8B, mask__24.11_52, _67, 0);

Is there a way to simplify that with the convert?

Or maybe we want to it if one or the other conversion simplifies ....

Confirmed.

  reply	other threads:[~2023-08-23 17:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23  9:37 [Bug target/111114] New: RISC-V: False " lehua.ding at rivai dot ai
2023-08-23 17:46 ` pinskia at gcc dot gnu.org [this message]
2023-08-24  3:51 ` [Bug tree-optimization/111114] RISC-V: Failed " lehua.ding at rivai dot ai
2023-08-24  4:18 ` pinskia at gcc dot gnu.org
2023-08-24  4:37 ` lehua.ding at rivai dot ai
2023-08-24  4:43 ` pinskia at gcc dot gnu.org
2023-08-24  4:50 ` lehua.ding at rivai dot ai

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-111114-4-1JDpDFUNyY@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: link
Be 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).