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/99378] [8/9/10/11 Regression] ICE in decompose_normal_address, at rtlanal.c:6710
Date: Fri, 05 Mar 2021 16:44:19 +0000	[thread overview]
Message-ID: <bug-99378-4-xxFxw8v8GK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99378-4@http.gcc.gnu.org/bugzilla/>

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

--- 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:9105757a59b890194ebf5b4fcbacd58db34ef332

commit r11-7526-g9105757a59b890194ebf5b4fcbacd58db34ef332
Author: Vladimir N. Makarov <vmakarov@redhat.com>
Date:   Fri Mar 5 11:41:25 2021 -0500

    [PR99378] LRA: Skip decomposing address for asm insn operand with unknown
constraint.

      Function get_constraint_type returns CT__UNKNOWN for empty constraint
    and CT_FIXED_FORM for "X".  So process_address_1 skipped
    decompose_mem_address only for "X" constraint.  To do the same for empty
    constraint, skip decompose_mem_address for CT__UNKNOWN.

    gcc/ChangeLog:

            PR target/99378
            * lra-constraints.c (process_address_1): Skip decomposing address
            for asm insn operand with unknown constraint.

    gcc/testsuite/ChangeLog:

            PR target/99378
            * gcc.target/i386/pr99123-2.c: New.

  parent reply	other threads:[~2021-03-05 16:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04  8:09 [Bug rtl-optimization/99378] New: " marxin at gcc dot gnu.org
2021-03-04  9:39 ` [Bug target/99378] [8/9/10/11 Regression] " jakub at gcc dot gnu.org
2021-03-04 16:53 ` vmakarov at gcc dot gnu.org
2021-03-05 16:44 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-07 14:41 ` asolokha at gmx dot com
2021-03-08 16:33 ` [Bug target/99378] [8/9/10 " jakub at gcc dot gnu.org
2021-05-14  9:54 ` [Bug target/99378] [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 target/99378] [10 " rguenth at gcc dot gnu.org
2022-06-28 10:43 ` jakub at gcc dot gnu.org
2023-07-07  9:30 ` 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-99378-4-xxFxw8v8GK@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).