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/109040] New: [13 Regression] wrong code with v16hi compare & mask on riscv64 at -O2
Date: Mon, 06 Mar 2023 11:14:06 +0000 [thread overview]
Message-ID: <bug-109040-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109040
Bug ID: 109040
Summary: [13 Regression] wrong code with v16hi compare & mask
on riscv64 at -O2
Product: gcc
Version: 13.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 54593
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54593&action=edit
reduced testcase
Output:
$ riscv64-unknown-linux-gnu-gcc -O2 testcase.c -static
$ qemu-riscv64 -- ./a.out
Aborted
$ 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-r13-6494-20230306010510-g2554d90c6c2-checking-yes-rtl-df-extra-riscv64/bin/../libexec/gcc/riscv64-unknown-linux-gnu/13.0.1/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-r13-6494-20230306010510-g2554d90c6c2-checking-yes-rtl-df-extra-riscv64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.0.1 20230305 (experimental) (GCC)
next reply other threads:[~2023-03-06 11:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 11:14 zsojka at seznam dot cz [this message]
2023-03-07 9:01 ` [Bug target/109040] " rguenth at gcc dot gnu.org
2023-03-27 8:29 ` marxin at gcc dot gnu.org
2023-03-27 8:45 ` [Bug target/109040] [13 Regression] wrong code with v16hi compare & mask on riscv64 at -O2 since r13-4907-g2e886eef7f2b5a marxin at gcc dot gnu.org
2023-04-04 12:54 ` jakub at gcc dot gnu.org
2023-04-04 13:41 ` jakub at gcc dot gnu.org
2023-04-04 13:46 ` jakub at gcc dot gnu.org
2023-04-04 15:02 ` jakub at gcc dot gnu.org
2023-04-04 20:08 ` ebotcazou at gcc dot gnu.org
2023-04-05 14:17 ` law at gcc dot gnu.org
2023-04-14 7:32 ` cvs-commit at gcc dot gnu.org
2023-04-19 9:13 ` cvs-commit 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-109040-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).