public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/99767] [9/10/11 Regression] ICE in expand_direct_optab_fn, at internal-fn.c:3360
Date: Thu, 15 Apr 2021 14:58:43 +0000	[thread overview]
Message-ID: <bug-99767-4-xp1xHTNYYf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99767-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Note, we have already:
      /* Stub out scalar statements that must not survive vectorization.
         Doing this here helps with grouped statements, or statements that
         are involved in patterns.  */
      for (gimple_stmt_iterator gsi = gsi_start_bb (bb);
           !gsi_end_p (gsi); gsi_next (&gsi))
        {
          gcall *call = dyn_cast <gcall *> (gsi_stmt (gsi));
          if (call && gimple_call_internal_p (call, IFN_MASK_LOAD))
            {
              tree lhs = gimple_get_lhs (call);
              if (!VECTOR_TYPE_P (TREE_TYPE (lhs)))
                {
                  tree zero = build_zero_cst (TREE_TYPE (lhs));
                  gimple *new_stmt = gimple_build_assign (lhs, zero);
                  gsi_replace (&gsi, new_stmt, true);
                }
            }
        }
in tree-vect-loop.c.
Perhaps we should handle similarly IFN_COND_* ?
Instead of using zero for those perhaps we could just use the last argument of
those calls (i.e. the ELSE part).

  parent reply	other threads:[~2021-04-15 14:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25 11:19 [Bug target/99767] New: " asolokha at gmx dot com
2021-03-25 11:57 ` [Bug target/99767] " rguenth at gcc dot gnu.org
2021-03-25 11:57 ` rguenth at gcc dot gnu.org
2021-03-25 15:22 ` jakub at gcc dot gnu.org
2021-03-25 15:27 ` jakub at gcc dot gnu.org
2021-04-15 13:09 ` rguenth at gcc dot gnu.org
2021-04-15 14:58 ` jakub at gcc dot gnu.org [this message]
2021-04-15 15:32 ` jakub at gcc dot gnu.org
2021-04-16  9:46 ` cvs-commit at gcc dot gnu.org
2021-04-16  9:58 ` [Bug target/99767] [9/10 " jakub at gcc dot gnu.org
2021-04-20  9:46 ` cvs-commit at gcc dot gnu.org
2021-04-20  9:53 ` [Bug target/99767] [9 " jakub at gcc dot gnu.org
2021-04-20 23:34 ` cvs-commit at gcc dot gnu.org
2021-04-22 15:01 ` jakub 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-99767-4-xp1xHTNYYf@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).