public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Uros Bizjak <ubizjak@gmail.com>
To: Hongtao Liu <crazylht@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, "H. J. Lu" <hjl.tools@gmail.com>
Subject: Re: [PATCH] [PR target/96350]Force ENDBR immediate into memory to avoid fake ENDBR opcode.
Date: Tue, 11 Aug 2020 10:38:09 +0200	[thread overview]
Message-ID: <CAFULd4bgHy9qOnpu7imYojPn1JjduLmr3hqOskAQExvUN6vqdg@mail.gmail.com> (raw)
In-Reply-To: <CAMZc-bzr3Oq93Np-Vc9n2mR_mjO_bT6gBZFB-irNdqwnLc_kWA@mail.gmail.com>

On Tue, Aug 11, 2020 at 5:30 AM Hongtao Liu <crazylht@gmail.com> wrote:
>
> Hi:
>   The issue is described in the bugzilla.
>   Bootstrap is ok, regression test for i386/x86-64 backend is ok.
>   Ok for trunk?
>
> ChangeLog
> gcc/
>         PR target/96350
>         * config/i386/i386.c (ix86_legitimate_constant_p): Return
>         false for ENDBR immediate.
>         (ix86_legitimate_address_p): Ditto.
>         * config/i386/predicated.md
>         (x86_64_immediate_operand): Exclude ENDBR immediate.
>         (x86_64_zext_immediate_operand): Ditto.
>         (x86_64_dwzext_immediate_operand): Ditto.
>         (ix86_not_endbr_immediate_operand): New predicate.
>
> gcc/testsuite
>         * gcc.target/i386/endbr_immediate.c: New test.

+;; Return true if VALUE isn't an ENDBR opcode in immediate field.
+(define_predicate "ix86_not_endbr_immediate_operand"
+  (match_test "1")

Please reverse the above logic to introduce
ix86_endbr_immediate_operand, that returns true for unwanted
immediate. Something like:

(define_predicate "ix86_endbr_immediate_operand"
  (match_code "const_int")
...

And you will be able to use it like:

if (ix86_endbr_immediate_operand (x, VOIDmode)
  return false;

   /* Otherwise we handle everything else in the move patterns.  */
-  return true;
+  return ix86_not_endbr_immediate_operand (x, VOIDmode);
 }

Please handle this in CASE_CONST_SCALAR_INT: part.

+  if (disp && !ix86_not_endbr_immediate_operand (disp, VOIDmode))
+    return false;

And this in:

  /* Validate displacement.  */
  if (disp)
    {

Uros.

> --
> BR,
> Hongtao

  reply	other threads:[~2020-08-11  8:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11  3:31 Hongtao Liu
2020-08-11  8:38 ` Uros Bizjak [this message]
2020-08-11  9:36   ` Hongtao Liu
2020-08-11  9:56     ` Uros Bizjak
2020-08-14  4:54       ` Hongtao Liu
2020-08-14 10:03         ` Uros Bizjak

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=CAFULd4bgHy9qOnpu7imYojPn1JjduLmr3hqOskAQExvUN6vqdg@mail.gmail.com \
    --to=ubizjak@gmail.com \
    --cc=crazylht@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    /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).