public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "prathamesh3492 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/98537] [11 Regression] ICE in emit_move_insn since r11-5839
Date: Thu, 07 Jan 2021 09:40:12 +0000	[thread overview]
Message-ID: <bug-98537-4-DDFI1l0y69@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98537-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from prathamesh3492 at gcc dot gnu.org ---
Hi,
It seems to work on my machine for x86_64.
Compiling with -O3 (or -O2),
.optimized dump shows:

v4si foo (v4si b, v4si a)
{
  v4si c;
  vector(4) <signed-boolean:32> _1;

  <bb 2> [local count: 1073741824]:
  _1 = a_2(D) == b_3(D);
  c_4 = VIEW_CONVERT_EXPR<v4si>(_1);
  return c_4;

}

I tried on top of af362af18f405c34840d820143aa3a94f72fce4d.

Btw, on ARM it seems to "scalarize" the code,
.optimized dump shows:

  _6 = BIT_FIELD_REF <a_2(D), 32, 0>;
  _7 = BIT_FIELD_REF <b_3(D), 32, 0>;
  _8 = _6 == _7 ? -1 : 0;
  _9 = BIT_FIELD_REF <a_2(D), 32, 32>;
  _10 = BIT_FIELD_REF <b_3(D), 32, 32>;
  _11 = _9 == _10 ? -1 : 0;
  _12 = BIT_FIELD_REF <a_2(D), 32, 64>;
  _13 = BIT_FIELD_REF <b_3(D), 32, 64>;
  _14 = _12 == _13 ? -1 : 0;
  _15 = BIT_FIELD_REF <a_2(D), 32, 96>;
  _16 = BIT_FIELD_REF <b_3(D), 32, 96>;
  _17 = _15 == _16 ? -1 : 0;
  c_4 = {_8, _11, _14, _17};
  return c_4;

Thanks,
Prathamesh

  parent reply	other threads:[~2021-01-07  9:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-05 16:00 [Bug tree-optimization/98537] New: " jakub at gcc dot gnu.org
2021-01-05 16:02 ` [Bug tree-optimization/98537] " jakub at gcc dot gnu.org
2021-01-06  2:10 ` crazylht at gmail dot com
2021-01-06  3:01 ` crazylht at gmail dot com
2021-01-07  5:10 ` [Bug target/98537] " crazylht at gmail dot com
2021-01-07  9:40 ` prathamesh3492 at gcc dot gnu.org [this message]
2021-01-07 10:32 ` crazylht at gmail dot com
2021-01-08 10:50 ` prathamesh3492 at gcc dot gnu.org
2021-01-14 11:14 ` crazylht at gmail dot com
2021-01-25  9:56 ` crazylht at gmail dot com
2021-02-05  2:01 ` cvs-commit at gcc dot gnu.org
2021-02-07  1:14 ` crazylht at gmail dot com
2021-02-12 14:55 ` 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-98537-4-DDFI1l0y69@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).