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/99663] [11 Regression] ICE in extract_constrain_insn, at recog.c:2670 on s390x-linux-gnu
Date: Fri, 19 Mar 2021 19:36:16 +0000	[thread overview]
Message-ID: <bug-99663-4-OLtDlTW1wf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99663-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 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:d81019db099ad95febbb2d4b4afd8cbe95762062

commit r11-7741-gd81019db099ad95febbb2d4b4afd8cbe95762062
Author: Vladimir N. Makarov <vmakarov@redhat.com>
Date:   Fri Mar 19 15:34:48 2021 -0400

    [PR99663] Don't use unknown constraint for address constraint in
process_address_1.

    s390x has insns using several alternatives with address constraints.  Even
    if we don't know at this stage what alternative will be used, we still can
say
    that is an address constraint.  So don't use unknown constraint in this
    case when there are multiple constraints or/and alternative.

    gcc/ChangeLog:

            PR target/99663
            * lra-constraints.c (process_address_1): Don't use unknown
            constraint for address constraint.

    gcc/testsuite/ChangeLog:

            PR target/99663
            * gcc.target/s390/pr99663.c: New.

  parent reply	other threads:[~2021-03-19 19:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19  9:33 [Bug target/99663] New: " doko at debian dot org
2021-03-19  9:51 ` [Bug target/99663] " doko at debian dot org
2021-03-19  9:58 ` jakub at gcc dot gnu.org
2021-03-19 10:07 ` rguenth at gcc dot gnu.org
2021-03-19 10:34 ` marxin at gcc dot gnu.org
2021-03-19 11:26 ` doko at debian dot org
2021-03-19 11:27 ` doko at debian dot org
2021-03-19 12:02 ` doko at debian dot org
2021-03-19 12:03 ` doko at gcc dot gnu.org
2021-03-19 12:08 ` jakub at gcc dot gnu.org
2021-03-19 12:19 ` doko at debian dot org
2021-03-19 12:44 ` jakub at gcc dot gnu.org
2021-03-19 17:24 ` vmakarov at gcc dot gnu.org
2021-03-19 19:36 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-22 17:44 ` doko at debian dot 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-99663-4-OLtDlTW1wf@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).