public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "juzhe.zhong at rivai dot ai" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111311] RISC-V regression testsuite errors with --param=riscv-autovec-preference=scalable Date: Wed, 06 Sep 2023 22:25:55 +0000 [thread overview] Message-ID: <bug-111311-4-tycBIuc1gG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111311-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111311 --- Comment #1 from JuzheZhong <juzhe.zhong at rivai dot ai> --- Except the known issue (LTO issue). All other issues are either bugus FAILS or very simple bugs. Fixing them just need a few days (maybe 2 ~ 3days). I will fix them first before sending new feature patches and the future new patches should always pass all regression tests with enablig vector extension.
next prev parent reply other threads:[~2023-09-06 22:25 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-06 21:10 [Bug target/111311] New: " rdapp at gcc dot gnu.org 2023-09-06 22:25 ` juzhe.zhong at rivai dot ai [this message] 2023-09-06 22:37 ` [Bug target/111311] " juzhe.zhong at rivai dot ai 2023-09-07 7:56 ` juzhe.zhong at rivai dot ai 2023-09-08 8:51 ` juzhe.zhong at rivai dot ai 2023-09-10 2:14 ` cvs-commit at gcc dot gnu.org 2023-09-11 3:32 ` cvs-commit at gcc dot gnu.org 2023-09-11 13:21 ` cvs-commit at gcc dot gnu.org 2023-11-02 17:12 ` patrick at rivosinc dot com 2023-11-02 17:18 ` vineetg at gcc dot gnu.org 2023-11-02 18:46 ` rdapp at gcc dot gnu.org 2023-11-02 21:23 ` vineetg at gcc dot gnu.org 2023-11-02 22:31 ` juzhe.zhong at rivai dot ai 2023-11-02 22:47 ` pinskia at gcc dot gnu.org 2023-11-03 2:56 ` law at gcc dot gnu.org 2023-11-08 1:42 ` juzhe.zhong at rivai dot ai 2023-11-08 20:12 ` vineetg at gcc dot gnu.org 2023-11-14 20:55 ` ewlu at rivosinc dot com 2023-11-15 23:39 ` patrick at rivosinc dot com 2023-11-16 1:08 ` juzhe.zhong at rivai dot ai 2023-11-16 1:15 ` patrick at rivosinc dot com
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-111311-4-tycBIuc1gG@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).