public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rdapp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112971] [14] RISC-V rv64gcv_zvl256b vector -O3: internal compiler error: Segmentation fault signal terminated program cc1
Date: Tue, 12 Dec 2023 13:18:50 +0000	[thread overview]
Message-ID: <bug-112971-4-z8Aztw9ccY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112971-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112971

--- Comment #5 from Robin Dapp <rdapp at gcc dot gnu.org> ---
Yes that's what I just tried.  No infinite loop anymore then.  But that's not a
new simplification and looks reasonable so there must be something special for
our backend.

  parent reply	other threads:[~2023-12-12 13:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11 21:47 [Bug target/112971] New: " patrick at rivosinc dot com
2023-12-11 22:17 ` [Bug target/112971] " juzhe.zhong at rivai dot ai
2023-12-12 12:11 ` rdapp at gcc dot gnu.org
2023-12-12 13:14 ` rdapp at gcc dot gnu.org
2023-12-12 13:15 ` juzhe.zhong at rivai dot ai
2023-12-12 13:18 ` rdapp at gcc dot gnu.org [this message]
2023-12-12 17:48 ` [Bug middle-end/112971] " pinskia at gcc dot gnu.org
2023-12-12 17:50 ` pinskia at gcc dot gnu.org
2023-12-12 18:18 ` rdapp at gcc dot gnu.org
2023-12-12 18:25 ` pinskia at gcc dot gnu.org
2023-12-12 18:25 ` pinskia at gcc dot gnu.org
2023-12-12 18:30 ` pinskia at gcc dot gnu.org
2023-12-14 22:08 ` juzhe.zhong at rivai dot ai
2023-12-14 22:15 ` pinskia at gcc dot gnu.org
2023-12-14 22:18 ` juzhe.zhong at rivai dot ai
2023-12-14 22:22 ` patrick at rivosinc dot com
2023-12-14 22:26 ` patrick at rivosinc dot com
2023-12-14 22:56 ` juzhe.zhong at rivai dot ai
2023-12-14 22:59 ` pinskia at gcc dot gnu.org
2023-12-14 23:02 ` juzhe.zhong at rivai dot ai
2023-12-15  3:36 ` juzhe.zhong at rivai dot ai
2024-01-10 13:35 ` juzhe.zhong at rivai dot ai
2024-01-10 13:37 ` rdapp at gcc dot gnu.org
2024-01-25 15:54 ` cvs-commit at gcc dot gnu.org
2024-02-22 21:37 ` 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-112971-4-z8Aztw9ccY@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).