public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112837] [12 Regression] ICE: RTL check: expected elt 1 type 'i' or 'n', have 'e' (rtx plus) in ix86_elim_entry_set_got, at config/i386/i386.cc:8612 with -fcompare-elim -fpie -fprofile
Date: Sun, 17 Dec 2023 13:55:26 +0000	[thread overview]
Message-ID: <bug-112837-4-DWnHJGFIqu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112837-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:05e3cff4e8b3b544afb1bbefddc342de42641cc1

commit r11-11153-g05e3cff4e8b3b544afb1bbefddc342de42641cc1
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Mon Dec 4 09:01:09 2023 +0100

    i386: Fix rtl checking ICE in ix86_elim_entry_set_got [PR112837]

    The following testcase ICEs with RTL checking, because it sets if
    XINT (SET_SRC (set), 1) is UNSPEC_SET_GOT without checking if SET_SRC (set)
    is actually an UNSPEC, so any time we see any other insn with PARALLEL
    and a SET in it which is not an UNSPEC we ICE during RTL checking or
    access there some other union member as if it was an rt_int.
    The rest is just small cleanup.

    2023-12-04  Jakub Jelinek  <jakub@redhat.com>

            PR target/112837
            * config/i386/i386.c (ix86_elim_entry_set_got): Before checking
            for UNSPEC_SET_GOT check that SET_SRC is UNSPEC.  Use SET_SRC and
            SET_DEST macros instead of XEXP, rename vec variable to set.

            * gcc.dg/pr112837.c: New test.

    (cherry picked from commit 4586d7d0a92e9b60d0c01043e0ae262b1e06f337)

      parent reply	other threads:[~2023-12-17 13:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-03 19:52 [Bug target/112837] New: [12/13/14 " zsojka at seznam dot cz
2023-12-03 22:13 ` [Bug target/112837] " jakub at gcc dot gnu.org
2023-12-03 22:28 ` jakub at gcc dot gnu.org
2023-12-04  8:01 ` cvs-commit at gcc dot gnu.org
2023-12-04  8:03 ` [Bug target/112837] [12/13 " jakub at gcc dot gnu.org
2023-12-04  8:44 ` rguenth at gcc dot gnu.org
2023-12-05 16:33 ` cvs-commit at gcc dot gnu.org
2023-12-05 17:02 ` [Bug target/112837] [12 " jakub at gcc dot gnu.org
2023-12-16  0:38 ` cvs-commit at gcc dot gnu.org
2023-12-17 13:55 ` cvs-commit at gcc dot gnu.org [this message]

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-112837-4-DWnHJGFIqu@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).