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/105927] ICE: RTL check: expected code 'reg', have 'mem' in rhs_regno, at rtl.h:1932 with -mtune=k6-3 -msse
Date: Mon, 13 Jun 2022 15:11:03 +0000	[thread overview]
Message-ID: <bug-105927-4-OBcRyqWuuq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105927-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Uros Bizjak <uros@gcc.gnu.org>:

https://gcc.gnu.org/g:b3dd7d8b48227d3489039ca66b6c0ea2da743255

commit r13-1071-gb3dd7d8b48227d3489039ca66b6c0ea2da743255
Author: Uros Bizjak <ubizjak@gmail.com>
Date:   Mon Jun 13 17:08:18 2022 +0200

    i386: Return true for (SUBREG (MEM....)) in register_no_elim_operand
[PR105927]

    Under certain conditions register_operand predicate also allows
    subregs of memory operands.  When RTL checking is enabled, these
    will fail with REGNO (op).

    Allow subregs of memory operands, these are guaranteed
    to be reloaded to a register.

    2022-06-13  Uroš Bizjak  <ubizjak@gmail.com>

    gcc/ChangeLog:

            PR target/105927
            * config/i386/predicates.md (register_no_elim_operand):
            Return true for subreg of a memory operand.

    gcc/testsuite/ChangeLog:

            PR target/105927
            * gcc.target/i386/pr105927.c: New test.

  parent reply	other threads:[~2022-06-13 15:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11 19:50 [Bug target/105927] New: " zsojka at seznam dot cz
2022-06-12 19:37 ` [Bug target/105927] " ubizjak at gmail dot com
2022-06-12 20:33 ` ubizjak at gmail dot com
2022-06-13 15:11 ` cvs-commit at gcc dot gnu.org [this message]
2022-06-13 15:16 ` 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-105927-4-OBcRyqWuuq@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).