public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <richard.sandiford@arm.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Richard Earnshaw <richard.earnshaw@arm.com>,
	 Kyrylo Tkachov <kyrylo.tkachov@arm.com>,
	 gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] aarch64: Fix plugin header install
Date: Wed, 21 Dec 2022 09:56:33 +0000	[thread overview]
Message-ID: <mpto7rx3wry.fsf@arm.com> (raw)
In-Reply-To: <Y6GRTuxVgQmxSZT5@tucnak> (Jakub Jelinek's message of "Tue, 20 Dec 2022 11:41:18 +0100")

Jakub Jelinek <jakub@redhat.com> writes:
> Hi!
>
> The r13-2943-g11a113d501ff64 made aarch64.h include
> aarch64-option-extensions.def, but that file isn't installed
> for building plugins.
>
> The following patch should fix that, ok for trunk if it
> passes bootstrap/regtest + building plugin against it?
>
> 2022-12-20  Jakub Jelinek  <jakub@redhat.com>
>
> 	* config/aarch64/t-aarch64 (OPTIONS_H_EXTRA): Add
> 	aarch64-option-extensions.def.
>
> --- gcc/config/aarch64/t-aarch64.jj	2022-04-04 13:55:46.001615509 +0200
> +++ gcc/config/aarch64/t-aarch64	2022-12-20 11:31:03.245651809 +0100
> @@ -22,7 +22,8 @@ TM_H += $(srcdir)/config/aarch64/aarch64
>  OPTIONS_H_EXTRA += $(srcdir)/config/aarch64/aarch64-cores.def \
>  		   $(srcdir)/config/aarch64/aarch64-arches.def \
>  		   $(srcdir)/config/aarch64/aarch64-fusion-pairs.def \
> -		   $(srcdir)/config/aarch64/aarch64-tuning-flags.def
> +		   $(srcdir)/config/aarch64/aarch64-tuning-flags.def \
> +		   $(srcdir)/config/aarch64/aarch64-option-extensions.def

Should this (and aarch64-fusion-pairs.def and aarch64-tuning-flags.def)
be in TM_H instead?  The first two OPTIONS_H_EXTRA entries seem to be
for aarch64-opt.h (included via aarch64.opt).

I guess TM_H should also have aarch64-arches.def, since it's included
for aarch64_feature.

OK with that change if it works/makes sense.

Thanks,
Richard

>  
>  $(srcdir)/config/aarch64/aarch64-tune.md: s-aarch64-tune-md; @true
>  s-aarch64-tune-md: $(srcdir)/config/aarch64/gentune.sh \
>
> 	Jakub

  reply	other threads:[~2022-12-21  9:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20 10:41 Jakub Jelinek
2022-12-21  9:56 ` Richard Sandiford [this message]
2022-12-21 10:12   ` Jakub Jelinek
2022-12-21 10:43     ` Richard Sandiford

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=mpto7rx3wry.fsf@arm.com \
    --to=richard.sandiford@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=kyrylo.tkachov@arm.com \
    --cc=richard.earnshaw@arm.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).