public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug plugins/110610] [14 Regression] File insn-opinit.h not installed ?
Date: Mon, 17 Jul 2023 16:04:02 +0000 [thread overview]
Message-ID: <bug-110610-4-QIH8BQG2VR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110610-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110610
--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andre Simoes Dias Vieira
<avieira@gcc.gnu.org>:
https://gcc.gnu.org/g:caabf0973a4e9a26421c94d540e3e20051e93e77
commit r14-2585-gcaabf0973a4e9a26421c94d540e3e20051e93e77
Author: Andre Vieira <andre.simoesdiasvieira@arm.com>
Date: Mon Jul 17 17:00:54 2023 +0100
Include insn-opinit.h in PLUGIN_H [PR110610]
This patch fixes PR110610 by including insn-opinit.h in the INTERNAL_FN_H
list,
as insn-opinit.h is now required by internal-fn.h. This will lead to
insn-opinit.h being installed in the plugin directory.
gcc/ChangeLog:
PR plugins/110610
* Makefile.in (INTERNAL_FN_H): Add insn-opinit.h.
next prev parent reply other threads:[~2023-07-17 16:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 7:04 [Bug plugins/110610] New: " dcb314 at hotmail dot com
2023-07-10 7:42 ` [Bug plugins/110610] " xry111 at gcc dot gnu.org
2023-07-10 8:06 ` avieira at gcc dot gnu.org
2023-07-10 8:57 ` dcb314 at hotmail dot com
2023-07-10 9:28 ` xry111 at gcc dot gnu.org
2023-07-10 9:41 ` avieira at gcc dot gnu.org
2023-07-10 10:13 ` xry111 at gcc dot gnu.org
2023-07-10 10:15 ` avieira at gcc dot gnu.org
2023-07-10 10:24 ` avieira at gcc dot gnu.org
2023-07-10 10:25 ` avieira at gcc dot gnu.org
2023-07-10 21:35 ` pinskia at gcc dot gnu.org
2023-07-11 15:53 ` [Bug plugins/110610] [14 Regression] " pinskia at gcc dot gnu.org
2023-07-17 16:04 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-17 16:04 ` avieira at gcc dot gnu.org
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=bug-110610-4-QIH8BQG2VR@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).