public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kurt at intricatesoftware dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99115] New: ICE in extract_insn, at recog.c:2309 on hppa (error: unrecognizable insn) with -O2
Date: Mon, 15 Feb 2021 21:56:29 +0000	[thread overview]
Message-ID: <bug-99115-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99115
           Summary: ICE in extract_insn, at recog.c:2309 on hppa (error:
                    unrecognizable insn) with -O2
           Product: gcc
           Version: 8.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: kurt at intricatesoftware dot com
  Target Milestone: ---

Created attachment 50191
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50191&action=edit
testcase

Noticed while compiling src/deps_log.cc ninja 1.10.2 on hppa. I trimmed down
the file to test.cc.

g++ -O2 -c ./test.cc -o test.o
./test.cc: In member function 'LoadStatus DepsLog::Load(const string&, State*,
std::__cxx11::string*)':
./test.cc:176:1: error: unrecognizable insn:
 }
 ^
(insn 218 217 219 25 (set (reg:DI 217)
        (plus:DI (reg/f:DI 65 virtual-stack-vars)
            (const_int -524292 [0xfffffffffff7fffc]))) "./test.cc":122 -1
     (nil))
during RTL pass: vregs
./test.cc:176:1: internal compiler error: in extract_insn, at recog.c:2309

             reply	other threads:[~2021-02-15 21:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 21:56 kurt at intricatesoftware dot com [this message]
2021-02-15 21:57 ` [Bug c++/99115] " kurt at intricatesoftware dot com
2021-02-15 22:00 ` [Bug c++/99115] ICE in extract_insn, at recog.c:2309 on alpha " kurt at intricatesoftware dot com
2021-02-16  8:16 ` [Bug target/99115] " ubizjak at gmail dot com
2021-02-17 10:28 ` 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-99115-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).