public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112740] New: [14 Regression] wrong code with vector compare on riscv64 at -O0
Date: Tue, 28 Nov 2023 06:34:58 +0000 [thread overview]
Message-ID: <bug-112740-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112740
Bug ID: 112740
Summary: [14 Regression] wrong code with vector compare on
riscv64 at -O0
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: zsojka at seznam dot cz
Target Milestone: ---
Host: x86_64-pc-linux-gnu
Target: riscv64-unknown-linux-gnu
Created attachment 56704
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56704&action=edit
reduced testcase
Output:
$ riscv64-unknown-linux-gnu-gcc testcase.c -static
$ qemu-riscv64 -- ./a.out
Aborted
"x" is "ffff...ffff" instead of 0
I am using qemu userspace emulation, so this might be a false positive:
$ qemu-riscv64 -version
qemu-riscv64 version 8.1.3
Copyright (c) 2003-2023 Fabrice Bellard and the QEMU Project developers
$ riscv64-unknown-linux-gnu-gcc -v
Using built-in specs.
COLLECT_GCC=/repo/gcc-trunk/binary-latest-riscv64/bin/riscv64-unknown-linux-gnu-gcc
COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r14-5898-20231127211931-gce52f1f7074-checking-yes-rtl-df-extra-riscv64/bin/../libexec/gcc/riscv64-unknown-linux-gnu/14.0.0/lto-wrapper
Target: riscv64-unknown-linux-gnu
Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++
--enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra
--with-cloog --with-ppl --with-isl --with-isa-spec=2.2
--with-sysroot=/usr/riscv64-unknown-linux-gnu --build=x86_64-pc-linux-gnu
--host=x86_64-pc-linux-gnu --target=riscv64-unknown-linux-gnu
--with-ld=/usr/bin/riscv64-unknown-linux-gnu-ld
--with-as=/usr/bin/riscv64-unknown-linux-gnu-as --disable-multilib
--disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r14-5898-20231127211931-gce52f1f7074-checking-yes-rtl-df-extra-riscv64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.0 20231128 (experimental) (GCC)
next reply other threads:[~2023-11-28 6:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 6:34 zsojka at seznam dot cz [this message]
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 ` [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@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).