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 inline-asm/99123] [8/9/10/11 Regression] ICE in decompose_normal_address, at rtlanal.c:6710
Date: Wed, 24 Feb 2021 18:58:03 +0000	[thread overview]
Message-ID: <bug-99123-4-3xLsFQG07t@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99123-4@http.gcc.gnu.org/bugzilla/>

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

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

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

commit r11-7373-gb6680c2084521d2612c3a08aa01b274078c4f3e3
Author: Vladimir N. Makarov <vmakarov@redhat.com>
Date:   Wed Feb 24 13:54:10 2021 -0500

    [PR99123] inline-asm: Don't use decompose_mem_address to find used hard
regs

    Inline asm in question has empty constraint which means anything
    including memory with invalid address.  To check used hard regs we
    used decompose_mem_address which assumes memory with valid address.
    The patch implements the same semantics without assuming valid
    addresses.

    gcc/ChangeLog:

            PR inline-asm/99123
            * lra-constraints.c (uses_hard_regs_p): Don't use
decompose_mem_address.

    gcc/testsuite/ChangeLog:

            PR inline-asm/99123
            * gcc.target/i386/pr99123.c: New.

  parent reply	other threads:[~2021-02-24 18:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16 17:40 [Bug c/99123] New: " gscfq@t-online.de
2021-02-16 18:19 ` [Bug inline-asm/99123] [8/9/10/11 Regression] " jakub at gcc dot gnu.org
2021-02-23 18:58 ` vmakarov at gcc dot gnu.org
2021-02-24 18:58 ` cvs-commit at gcc dot gnu.org [this message]
2021-02-26 11:54 ` [Bug inline-asm/99123] [8/9/10 " rguenth at gcc dot gnu.org
2021-05-14  9:54 ` [Bug inline-asm/99123] [9/10 " jakub at gcc dot gnu.org
2021-06-01  8:19 ` rguenth at gcc dot gnu.org
2022-05-27  9:44 ` [Bug rtl-optimization/99123] [10 " rguenth at gcc dot gnu.org
2022-06-28 10:43 ` jakub at gcc dot gnu.org
2023-07-07  9:27 ` rguenth 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-99123-4-3xLsFQG07t@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).