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 middle-end/112740] [14 Regression] wrong code with vector compare on riscv64 at -O0
Date: Thu, 30 Nov 2023 21:57:08 +0000	[thread overview]
Message-ID: <bug-112740-4-MV2TusXA8m@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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|target                      |middle-end

--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Oh it is not the ~ but rather `_3 = {_16};` which produces the wrong code:
//  <signed-boolean:128> _16;
//   vector(1) <signed-boolean:128> _3;

;; _3 = {_16};

(insn 36 35 37 (set (reg:TI 114)
        (reg:TI 102 [ _16 ])) "/app/example.cpp":15:6 -1
     (nil))

(insn 37 36 38 (set (subreg:DI (reg:TI 113) 0)
        (and:DI (subreg:DI (reg:TI 114) 0)
            (const_int 1 [0x1]))) "/app/example.cpp":15:6 -1
     (nil))

(insn 38 37 39 (set (reg:DI 115)
        (const_int 0 [0])) "/app/example.cpp":15:6 -1
     (nil))

(insn 39 38 40 (set (subreg:DI (reg:TI 113) 8)
        (and:DI (subreg:DI (reg:TI 114) 8)
            (reg:DI 115))) "/app/example.cpp":15:6 -1
     (nil))

(insn 40 39 0 (set (reg:TI 94 [ _3 ])
        (reg:TI 113)) "/app/example.cpp":15:6 -1
     (nil))


That is wrong. that is producing 1 in _3 when it should have been -1 .
That is it is doing `r94 = r102 & 0x1` which is totally wrong/broken ...

  parent reply	other threads:[~2023-11-30 21:57 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
2023-11-30 21:57 ` pinskia at gcc dot gnu.org [this message]
2023-11-30 22:02 ` [Bug middle-end/112740] " 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-MV2TusXA8m@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).