public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mss at tutanota dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/100041] New: ICE in curr_insn_transform, at lra-constraints.c:4022
Date: Mon, 12 Apr 2021 03:39:56 +0000	[thread overview]
Message-ID: <bug-100041-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 100041
           Summary: ICE in curr_insn_transform, at lra-constraints.c:4022
           Product: gcc
           Version: 10.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: mss at tutanota dot de
  Target Milestone: ---

When trying to build LLVM 11.1.0 with GCC 10.3.0 on an x86_64 linux musl
(1.2.1) host, i am getting this ICE:

In file included from
/mss/work/table/llvm-project-llvmorg-11.1.0/llvm/lib/Support/ItaniumManglingCanonicalizer.cpp:13:
/mss/work/table/llvm-project-llvmorg-11.1.0/llvm/include/llvm/Demangle/ItaniumDemangle.h:
In member function 'void
llvm::itanium_demangle::FloatLiteralImpl<Float>::printLeft(llvm::itanium_demangle::OutputStream&)
const [with Float = long double]':
/mss/work/table/llvm-project-llvmorg-11.1.0/llvm/include/llvm/Demangle/ItaniumDemangle.h:2144:3:
error: unable to generate reloads for:
 2144 |   }
      |   ^
(insn 157 156 158 8 (set (mem:XF (pre_modify:DI (reg/f:DI 7 sp)
                (plus:DI (reg/f:DI 7 sp)
                    (const_int -16 [0xfffffffffffffff0]))) [485  S12 A32])
        (mem/j/c:XF (reg/f:DI 19 frame) [0 D.132846.value+0 S12 A64]))
"/mss/work/table/llvm-project-llvmorg-11.1.0/llvm/include/llvm/Demangle/ItaniumDemangle.h":2141:23
105 {*pushxf}
     (expr_list:REG_ARGS_SIZE (const_int 16 [0x10])
        (nil)))
during RTL pass: reload
/mss/work/table/llvm-project-llvmorg-11.1.0/llvm/include/llvm/Demangle/ItaniumDemangle.h:2144:3:
internal compiler error: in curr_insn_transform, at lra-constraints.c:4022
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.

             reply	other threads:[~2021-04-12  3:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12  3:39 mss at tutanota dot de [this message]
2021-04-12  6:17 ` [Bug target/100041] " pinskia at gcc dot gnu.org
2021-04-12  7:30 ` mss at tutanota dot de
2021-04-12  7:32 ` mss at tutanota dot de
2021-04-12  7:34 ` marxin at gcc dot gnu.org
2021-04-12  7:39 ` mss at tutanota dot de
2021-04-12  7:40 ` marxin at gcc dot gnu.org
2021-04-12  8:52 ` mss at tutanota dot de
2021-04-12  8:54 ` mss at tutanota dot de
2021-04-12  8:55 ` mss at tutanota dot de
2021-04-12  9:08 ` mss at tutanota dot de
2021-04-12  9:09 ` rguenth at gcc dot gnu.org
2021-04-12  9:11 ` rguenth at gcc dot gnu.org
2021-04-12  9:31 ` ubizjak at gmail dot com
2021-04-12 11:08 ` marxin at gcc dot gnu.org
2021-04-12 11:21 ` ubizjak at gmail dot com
2021-04-12 11:57 ` ubizjak at gmail dot com
2021-04-12 11:59 ` ubizjak at gmail dot com
2021-04-12 12:04 ` jakub at gcc dot gnu.org
2021-04-12 12:11 ` ubizjak at gmail dot com
2021-04-12 12:14 ` jakub at gcc dot gnu.org
2021-04-12 12:22 ` ubizjak at gmail dot com
2021-04-12 12:26 ` mss at tutanota dot de
2021-04-23 16:46 ` cvs-commit at gcc dot gnu.org
2021-04-24  8:03 ` ubizjak at gmail 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-100041-4@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).