public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pan2.li at intel dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/111970] [14 regression] SLP for non-IFN gathers result in RISC-V test failure on gather since r14-4745-gbeab5b95c58145 Date: Wed, 25 Oct 2023 02:53:43 +0000 [thread overview] Message-ID: <bug-111970-4-VUsZKj96nG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111970-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111970 --- Comment #2 from Li Pan <pan2.li at intel dot com> --- Add more information about how to build and run the test cases. Build: ../__RISC-V_INSTALL___RV64/bin/riscv64-unknown-elf-gcc -march=rv64imafdcv -mabi=lp64d -ftree-vectorize -O3 --param riscv-autovec-preference=fixed-vlmax --param riscv-autovec-lmul=dynamic -ffast-math -lm gcc/testsuite/gcc.target/riscv/rvv/autovec/gather-scatter/gather_load_run-12.c -o test.elf Run: qemu-riscv64 -cpu rv64,v=true,vlen=128,elen=64,vext_spec=v1.0 test.elf assertion "dest_float_uint8_t[i * 2] == (src_float_uint8_t [index_float_uint8_t[i * 2]] + 1)" failed: file "gcc/testsuite/gcc.target/riscv/rvv/autovec/gather-scatter/gather_load_run-12.c", line 106, function: main
next prev parent reply other threads:[~2023-10-25 2:53 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-25 2:02 [Bug c/111970] New: [tree-optimization] SLP for non-IFN gathers result in RISC-V test failure on gather pan2.li at intel dot com 2023-10-25 2:03 ` [Bug c/111970] " pan2.li at intel dot com 2023-10-25 2:53 ` pan2.li at intel dot com [this message] 2023-10-25 8:05 ` [Bug tree-optimization/111970] [14 regression] SLP for non-IFN gathers result in RISC-V test failure on gather since r14-4745-gbeab5b95c58145 pan2.li at intel dot com 2023-10-27 12:29 ` rguenth at gcc dot gnu.org 2023-10-27 13:03 ` pan2.li at intel dot com 2023-10-31 12:49 ` rguenth at gcc dot gnu.org 2023-10-31 14:07 ` pan2.li at intel dot com 2023-10-31 14:16 ` pan2.li at intel dot com 2023-11-13 12:42 ` rguenth at gcc dot gnu.org 2023-11-13 22:07 ` juzhe.zhong at rivai dot ai 2023-11-20 6:49 ` juzhe.zhong at rivai dot ai 2023-11-20 6:51 ` juzhe.zhong at rivai dot ai 2023-11-20 6:52 ` juzhe.zhong at rivai dot ai 2023-11-20 8:10 ` juzhe.zhong at rivai dot ai 2023-11-20 8:22 ` rguenther at suse dot de 2023-11-20 8:30 ` rguenth at gcc dot gnu.org 2023-11-20 14:20 ` rguenth at gcc dot gnu.org 2023-11-20 14:58 ` rdapp at gcc dot gnu.org 2023-11-20 22:24 ` tnfchris at gcc dot gnu.org 2023-11-20 22:30 ` pinskia at gcc dot gnu.org 2023-11-20 23:56 ` pan2.li at intel dot com 2023-11-21 7:20 ` cvs-commit at gcc dot gnu.org 2023-11-21 7:24 ` 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-111970-4-VUsZKj96nG@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: linkBe 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).