public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ewlu at rivosinc dot com" <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: Tue, 14 Nov 2023 20:55:24 +0000	[thread overview]
Message-ID: <bug-111311-4-01W3XdjHvL@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

Edwin Lu <ewlu at rivosinc dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ewlu at rivosinc dot com

--- Comment #17 from Edwin Lu <ewlu at rivosinc dot com> ---
(In reply to Patrick O'Neill from comment #8)

>         === gcc: Unexpected fails for rv64gcv lp64d medlow ===
> FAIL: gcc.dg/unroll-8.c scan-rtl-dump loop2_unroll "Not unrolling loop,
> doesn't roll"
> FAIL: gcc.dg/unroll-8.c scan-rtl-dump loop2_unroll "likely upper bound: 6"
> FAIL: gcc.dg/unroll-8.c scan-rtl-dump loop2_unroll "realistic bound: -1"

tracked in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112531

  parent reply	other threads:[~2023-11-14 20:55 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 ` [Bug target/111311] " juzhe.zhong at rivai dot ai
2023-09-06 22:37 ` 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 [this message]
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-01W3XdjHvL@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).