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 target/112740] [14 Regression] wrong code with vector compare on riscv64 at -O0
Date: Thu, 30 Nov 2023 21:50:32 +0000	[thread overview]
Message-ID: <bug-112740-4-fYBUAK6vxb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112740-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Veclower -O0 produces
  c.0_6 = c_5(D);
  _2 = (__int128 unsigned) c.0_6;
  _1 = {_2};
  _10 = VIEW_CONVERT_EXPR<__int128 unsigned>(v_7(D));
  _11 = _10 >= _2; // 1 true
  _12 = (int128_t) _11; // 1
  _13 = -_12; // -1
  _14 = (<signed-boolean:128>) _13; // -1 aka true
  _3 = {_14}; // {-1} aka true
  _4 = ~_3; // 0 aka false
  _15 = VIEW_CONVERT_EXPR<<signed-boolean:128>>(_4); // 0 aka false
  _16 = _15 != 0; // 0 != 0, 0 false
  _17 = (__int128 unsigned) _16; // 0
  _18 = -_17; // 0
  _8 = {_18};

Which looks correct.
NOTE the ~ there, I am suspecting it is producing the wrong result ...

  parent reply	other threads:[~2023-11-30 21:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28  6:34 [Bug target/112740] New: " zsojka at seznam dot cz
2023-11-28  7:07 ` [Bug target/112740] " pinskia at gcc dot gnu.org
2023-11-30  0:23 ` pinskia at gcc dot gnu.org
2023-11-30  8:17 ` zsojka at seznam dot cz
2023-11-30  8:20 ` pinskia at gcc dot gnu.org
2023-11-30 18:47 ` pinskia at gcc dot gnu.org
2023-11-30 21:50 ` pinskia at gcc dot gnu.org [this message]
2023-11-30 21:57 ` [Bug middle-end/112740] " pinskia at gcc dot gnu.org
2023-11-30 22:02 ` pinskia at gcc dot gnu.org
2023-11-30 22:15 ` pinskia at gcc dot gnu.org
2023-11-30 22:35 ` pinskia at gcc dot gnu.org
2023-12-01 11:46 ` rguenth at gcc dot gnu.org
2024-01-10 13:42 ` rguenth at gcc dot gnu.org
2024-01-10 13:56 ` rguenth at gcc dot gnu.org
2024-01-11  8:15 ` cvs-commit at gcc dot gnu.org
2024-01-11  8:15 ` rguenth 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-112740-4-fYBUAK6vxb@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).