public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "stsp at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/105936] New: internal compiler error: in move_insn, at haifa-sched.c:5463
Date: Sun, 12 Jun 2022 13:03:32 +0000	[thread overview]
Message-ID: <bug-105936-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105936
           Summary: internal compiler error: in move_insn, at
                    haifa-sched.c:5463
           Product: gcc
           Version: 9.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: gcov-profile
          Assignee: unassigned at gcc dot gnu.org
          Reporter: stsp at users dot sourceforge.net
                CC: marxin at gcc dot gnu.org
  Target Milestone: ---

Created attachment 53124
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53124&action=edit
pre-processed source

The problem happens with 9.4.0
in ubuntu-20, and with more recent
gcc in ubuntu-21.10, but not sure
what exact version of gcc is there.

$ gcc -O2 -c -xc int.E

during RTL pass: sched2
/<<PKGBUILDDIR>>/build/../src/base/core/int.c: In function
‘int33_unrevect_fixup’:
/<<PKGBUILDDIR>>/build/../src/base/core/int.c:1746:1: internal compiler error:
in move_insn, at haifa-sched.c:5463

             reply	other threads:[~2022-06-12 13:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-12 13:03 stsp at users dot sourceforge.net [this message]
2022-06-12 16:57 ` [Bug rtl-optimization/105936] [10 Regression] " pinskia at gcc dot gnu.org
2022-06-12 17:33 ` [Bug rtl-optimization/105936] [10 Regression] ICE with inline-asm and TLS on x86_64 and -O2 in move_insn pinskia at gcc dot gnu.org
2022-06-12 17:35 ` pinskia at gcc dot gnu.org
2022-06-13  7:41 ` ubizjak at gmail dot com
2022-06-13  9:19 ` ubizjak at gmail dot com
2022-06-13 10:04 ` ubizjak at gmail dot com
2022-06-13 10:19 ` stsp at users dot sourceforge.net

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-105936-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).