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/114696] ICE: in extract_constrain_insn_cached, at recog.cc:2725 insn does not satisfy its constraints: {*anddi_1} with -mapxf -mx32
Date: Mon, 15 Apr 2024 11:21:47 +0000	[thread overview]
Message-ID: <bug-114696-4-zSXWz5uzB1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114696-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by H.J. Lu <hjl@gcc.gnu.org>:

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

commit r14-9970-ga3281dd0f4b46c16ec1192ad411c0a96e6d086eb
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Fri Apr 12 15:42:12 2024 -0700

    x86: Allow TImode offsettable memory only with 8-bit constant

    The x86 instruction size limit is 15 bytes.  If a NDD instruction has
    a segment prefix byte, a 4-byte opcode prefix, a MODRM byte, a SIB byte,
    a 4-byte displacement and a 4-byte immediate, adding an address size
    prefix will exceed the size limit.  Change TImode ADD, AND, OR and XOR
    to allow offsettable memory only with 8-bit signed integer constant,
    which is encoded with a 1-byte immediate, if the address size prefix
    is used.

    gcc/

            PR target/114696
            * config/i386/i386.md (isa): Add apx_ndd_64.
            (enabled): Likewise.
            (*add<dwi>3_doubleword): Change rjO to r,ro,jO with 8-bit
            signed integer constant and enable jO only for apx_ndd_64.
            (*add<dwi>3_doubleword_cc_overflow_1): Likewise.
            (*and<dwi>3_doubleword): Likewise.
            (*<code><dwi>3_doubleword): Likewise.

    gcc/testsuite/

            PR target/114696
            * gcc.target/i386/apx-ndd-x32-2a.c: New test.
            * gcc.target/i386/apx-ndd-x32-2b.c: Likewise.
            * gcc.target/i386/apx-ndd-x32-2c.c: Likewise.
            * gcc.target/i386/apx-ndd-x32-2d.c: Likewise.

  parent reply	other threads:[~2024-04-15 11:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11 17:37 [Bug target/114696] New: " zsojka at seznam dot cz
2024-04-12 11:46 ` [Bug target/114696] " hjl.tools at gmail dot com
2024-04-12 15:32 ` hjl.tools at gmail dot com
2024-04-12 22:44 ` hjl.tools at gmail dot com
2024-04-15 11:21 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-15 11:30 ` hjl.tools 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-114696-4-zSXWz5uzB1@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).