public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105980] New: [11/12/13 Regression] ICE in final_scan_insn_1, at final.cc:2811
Date: Tue, 14 Jun 2022 17:53:12 +0000	[thread overview]
Message-ID: <bug-105980-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105980
           Summary: [11/12/13 Regression] ICE in final_scan_insn_1, at
                    final.cc:2811
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Started with r11 between 20201115 and 20201122, using -m16 or -m32 :
(with files pr41257.C, pr47366.C, pr83549.C, pr83619.C, etc.)


$ gcc-13-20220612 -c pr41257.C -fpie -m32 -mforce-indirect-call
pr41257.C: In member function 'virtual void C::_ZTv0_n16_N1CD1Ev()':
pr41257.C:20:1: error: insn does not satisfy its constraints:
   20 | }
      | ^
(insn 6 5 7 (set (reg:SI 82)
        (plus:SI (reg:SI 82)
            (const:SI (unspec:SI [
                        (symbol_ref:SI ("*.LTHUNK2") [flags 0x3] <function_decl
0x7f8b38853200 *.LTHUNK2>)
                    ] UNSPEC_GOTOFF)))) "pr41257.C":12:8 227 {*leasi}
     (nil))
pr41257.C:20:1: internal compiler error: in final_scan_insn_1, at final.cc:2811
0x698229 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
        ../../gcc/rtl-error.cc:108
0x698252 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
        ../../gcc/rtl-error.cc:118
0xa85023 final_scan_insn_1
        ../../gcc/final.cc:2811
0xa8505b final_scan_insn(rtx_insn*, _IO_FILE*, int, int, int*)
        ../../gcc/final.cc:2940
0xa85304 final_1
        ../../gcc/final.cc:1997
0x10c6f52 x86_output_mi_thunk
        ../../gcc/config/i386/i386.cc:21482
0x98b867 expand_thunk(cgraph_node*, bool, bool)
        ../../gcc/symtab-thunks.cc:388
0x99bca6 cgraph_node::assemble_thunks_and_aliases()
        ../../gcc/cgraphunit.cc:1757
0x99bc61 cgraph_node::assemble_thunks_and_aliases()
        ../../gcc/cgraphunit.cc:1779
0x99be90 cgraph_node::expand()
        ../../gcc/cgraphunit.cc:1898
0x99d10f output_in_order
        ../../gcc/cgraphunit.cc:2142
0x99d10f symbol_table::compile()
        ../../gcc/cgraphunit.cc:2346
0x99fa9f symbol_table::compile()
        ../../gcc/cgraphunit.cc:2533
0x99fa9f symbol_table::finalize_compilation_unit()
        ../../gcc/cgraphunit.cc:2530

             reply	other threads:[~2022-06-14 17:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 17:53 gscfq@t-online.de [this message]
2022-06-15  9:13 ` [Bug target/105980] " rguenth at gcc dot gnu.org
2022-06-16 14:03 ` marxin at gcc dot gnu.org
2022-06-17 10:21 ` ubizjak at gmail dot com
2022-07-25 16:00 ` rguenth at gcc dot gnu.org
2022-07-29 13:46 ` jakub at gcc dot gnu.org
2022-07-29 18:41 ` hjl.tools at gmail dot com
2022-07-29 20:10 ` jakub at gcc dot gnu.org
2022-07-29 20:37 ` hjl.tools at gmail dot com
2023-01-16 18:02 ` jakub at gcc dot gnu.org
2023-01-16 19:00 ` hjl.tools at gmail dot com
2023-01-16 22:11 ` cvs-commit at gcc dot gnu.org
2023-03-24 16:15 ` [Bug target/105980] [11/12 " jakub at gcc dot gnu.org
2023-04-27 13:18 ` cvs-commit at gcc dot gnu.org
2023-05-29 10:07 ` [Bug target/105980] [11 " jakub at gcc dot gnu.org
2024-02-10 18:19 ` fxcoudert 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-105980-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).