public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-2027] [AARCH64] Remove reference to MD_INCLUDES
Date: Fri, 12 Aug 2022 00:36:38 +0000 (GMT)	[thread overview]
Message-ID: <20220812003638.9498D3858D28@sourceware.org> (raw)

https://gcc.gnu.org/g:1595794f804ed3e925dcdf5f21b7fa762c74ca15

commit r13-2027-g1595794f804ed3e925dcdf5f21b7fa762c74ca15
Author: Andrew Pinski <apinski@marvell.com>
Date:   Fri Aug 12 00:26:17 2022 +0000

    [AARCH64] Remove reference to MD_INCLUDES
    
    The comment reference to MD_INCLUDES is not needed
    as it is auto generated for long time now even before
    aarch64 target was added.
    
    MD_INCLUDES has been auto generated since r0-64489.
    Note some targets still manually set MD_INCLUDES and
    I suspect those can be changed but I don't have access
    to those targets.
    
    Committed as obvious.
    
    Thanks,
    Andrew Pinski
    
    gcc/ChangeLog:
    
            * config/aarch64/aarch64.md: Remove comment
            about MD_INCLUDES as it is out of date and not needed.

Diff:
---
 gcc/config/aarch64/aarch64.md | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/gcc/config/aarch64/aarch64.md b/gcc/config/aarch64/aarch64.md
index ef0aed25c6b..3ea16dbc255 100644
--- a/gcc/config/aarch64/aarch64.md
+++ b/gcc/config/aarch64/aarch64.md
@@ -347,9 +347,6 @@
    ; must not operate on inactive inputs if doing so could induce a fault.
    (SVE_STRICT_GP 1)])
 
-;; If further include files are added the defintion of MD_INCLUDES
-;; must be updated.
-
 (include "constraints.md")
 (include "predicates.md")
 (include "iterators.md")


                 reply	other threads:[~2022-08-12  0:36 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=20220812003638.9498D3858D28@sourceware.org \
    --to=pinskia@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).