public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "patrick at rivosinc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112597] RISC-V regression testsuite errors with rv64gcv_zvl256b
Date: Tue, 21 Nov 2023 22:38:07 +0000 [thread overview]
Message-ID: <bug-112597-4-1RrdPJ4gPO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112597-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112597
--- Comment #8 from Patrick O'Neill <patrick at rivosinc dot com> ---
(In reply to JuzheZhong from comment #7)
> I think there is middle-end issue here:
>
> FAIL: gfortran.dg/maxval_char_3.f90 -O3 -fomit-frame-pointer
> -funroll-loops -fpeel-loops -ftracer -finline-functions (internal compiler
> error: in duplicate_and_interleave, at tree-vect-slp.cc:8025)
>
> Could you file another PR CC me, Robin and Richard for this ?
Filed: pr112661
next prev parent reply other threads:[~2023-11-21 22:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 21:15 [Bug target/112597] New: " patrick at rivosinc dot com
2023-11-17 21:21 ` [Bug target/112597] " patrick at rivosinc dot com
2023-11-20 10:16 ` juzhe.zhong at rivai dot ai
2023-11-20 13:54 ` cvs-commit at gcc dot gnu.org
2023-11-21 2:41 ` juzhe.zhong at rivai dot ai
2023-11-21 17:36 ` patrick at rivosinc dot com
2023-11-21 17:39 ` patrick at rivosinc dot com
2023-11-21 22:10 ` juzhe.zhong at rivai dot ai
2023-11-21 22:38 ` patrick at rivosinc dot com [this message]
2023-11-27 17:34 ` patrick at rivosinc dot com
2023-11-27 17:39 ` patrick at rivosinc dot com
2023-12-04 21:30 ` patrick at rivosinc dot com
2023-12-11 22:04 ` patrick at rivosinc dot com
2024-01-24 23:53 ` 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-112597-4-1RrdPJ4gPO@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).