public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-6321] i386: Update i386-builtin.def file comment description of BDESC{, _FIRST}
Date: Fri, 24 Feb 2023 12:15:37 +0000 (GMT)	[thread overview]
Message-ID: <20230224121537.2D4B33854806@sourceware.org> (raw)

https://gcc.gnu.org/g:05a3fc910c37499323e421e5c8dee2e336b79ca1

commit r13-6321-g05a3fc910c37499323e421e5c8dee2e336b79ca1
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Feb 24 13:07:58 2023 +0100

    i386: Update i386-builtin.def file comment description of BDESC{,_FIRST}
    
    I've noticed the description of these wasn't updated when the mask2
    argument has been added in 2019.
    
    2023-02-24  Jakub Jelinek  <jakub@redhat.com>
    
            * config/i386/i386-builtin.def: Update description of BDESC
            and BDESC_FIRST in file comment to include mask2.

Diff:
---
 gcc/config/i386/i386-builtin.def | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/config/i386/i386-builtin.def b/gcc/config/i386/i386-builtin.def
index a773f5eca49..f1c295c34f6 100644
--- a/gcc/config/i386/i386-builtin.def
+++ b/gcc/config/i386/i386-builtin.def
@@ -23,9 +23,9 @@
    <http://www.gnu.org/licenses/>.  */
 
 /* Before including this file, some macros must be defined:
-   BDESC (mask, icode, name, code, comparison, flag)
+   BDESC (mask, mask2, icode, name, code, comparison, flag)
      -- definition of each builtin
-   BDESC_FIRST (kind, KIND, mask, icode, name, code, comparison, flag)
+   BDESC_FIRST (kind, KIND, mask, mask2, icode, name, code, comparison, flag)
      -- like BDESC, but used for the first builtin in each category;
 	bdesc_##kind will be used in the name of the array and
 	IX86_BUILTIN__BDESC_##KIND##_FIRST will be the low boundary

                 reply	other threads:[~2023-02-24 12:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230224121537.2D4B33854806@sourceware.org \
    --to=jakub@gcc.gnu.org \
    --cc=gcc-cvs@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).