public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Richard Sandiford <rsandifo@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-2933] Add OPTIONS_H_EXTRA to GTFILES Date: Thu, 29 Sep 2022 10:33:47 +0000 (GMT) [thread overview] Message-ID: <20220929103347.3D2293858D28@sourceware.org> (raw) https://gcc.gnu.org/g:c1e1fa054970a30844eb94d726b4954dcb8b9063 commit r13-2933-gc1e1fa054970a30844eb94d726b4954dcb8b9063 Author: Richard Sandiford <richard.sandiford@arm.com> Date: Thu Sep 29 11:32:50 2022 +0100 Add OPTIONS_H_EXTRA to GTFILES I have a patch that adds a typedef to aarch64's <cpu>-opts.h. The typedef is used for a TargetVariable in the .opt file, which means that it is covered by PCH and so needs to be visible to gengtype. <cpu>-opts.h is not included directly in tm.h, but indirectly by target headers (in this case aarch64.h). There was therefore nothing that caused it to be added to GTFILES. gcc/ * Makefile.in (GTFILES): Add OPTIONS_H_EXTRA. Diff: --- gcc/Makefile.in | 1 + 1 file changed, 1 insertion(+) diff --git a/gcc/Makefile.in b/gcc/Makefile.in index 59b67d99441..c1d04384399 100644 --- a/gcc/Makefile.in +++ b/gcc/Makefile.in @@ -2661,6 +2661,7 @@ s-match: build/genmatch$(build_exeext) $(srcdir)/match.pd cfn-operators.pd GTFILES = $(CPPLIB_H) $(srcdir)/input.h $(srcdir)/coretypes.h \ $(host_xm_file_list) \ + $(OPTIONS_H_EXTRA) \ $(tm_file_list) $(HASHTAB_H) $(SPLAY_TREE_H) $(srcdir)/bitmap.h \ $(srcdir)/wide-int.h $(srcdir)/alias.h \ $(srcdir)/coverage.cc $(srcdir)/rtl.h \
reply other threads:[~2022-09-29 10:33 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=20220929103347.3D2293858D28@sourceware.org \ --to=rsandifo@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: linkBe 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).