public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "malat at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109244] internal compiler error: in setup_preferred_alternate_classes_for_new_pseudos, at ira.cc:2892
Date: Wed, 22 Mar 2023 07:50:59 +0000	[thread overview]
Message-ID: <bug-109244-4-uZvocMdYO4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109244-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Mathieu Malaterre <malat at debian dot org> ---
Thanks for the quick update. I'll stop my test until this is merged.

As a side note, I am also seeing this one in my log:

internal compiler error: in finalize_new_accesses, at rtl-ssa/changes.cc:471
  133 |   }
      |   ^
0xf6b49f rtl_ssa::function_info::finalize_new_accesses(rtl_ssa::insn_change&)
        ../../src/gcc/rtl-ssa/changes.cc:471
0xf656cd
rtl_ssa::function_info::change_insns(array_slice<rtl_ssa::insn_change*>)
        ../../src/gcc/rtl-ssa/changes.cc:659
0xf6551f rtl_ssa::function_info::change_insn(rtl_ssa::insn_change&)
        ../../src/gcc/rtl-ssa/changes.cc:717
0x57eeb1 change_insn
        ../../src/gcc/config/riscv/riscv-vsetvl.cc:1027
0x57eeb1 pass_vsetvl::cleanup_insns() const
        ../../src/gcc/config/riscv/riscv-vsetvl.cc:3929
0x59070b pass_vsetvl::lazy_vsetvl()
        ../../src/gcc/config/riscv/riscv-vsetvl.cc:4189
0x590891 pass_vsetvl::execute(function*)
        ../../src/gcc/config/riscv/riscv-vsetvl.cc:4219

  parent reply	other threads:[~2023-03-22  7:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22  7:22 [Bug c++/109244] New: " malat at debian dot org
2023-03-22  7:41 ` [Bug target/109244] " juzhe.zhong at rivai dot ai
2023-03-22  7:50 ` malat at debian dot org [this message]
2023-03-22  8:03 ` juzhe.zhong at rivai dot ai
2023-03-23  1:51 ` kito at gcc dot gnu.org
2023-03-23  3:22 ` cvs-commit at gcc dot gnu.org
2023-03-23  3:23 ` kito 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-109244-4-uZvocMdYO4@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).