public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug plugins/63410] New: [Regression] pass_instances.def is not installed Date: Mon, 29 Sep 2014 18:12:00 -0000 [thread overview] Message-ID: <bug-63410-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63410 Bug ID: 63410 Summary: [Regression] pass_instances.def is not installed Product: gcc Version: 4.9.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: plugins Assignee: unassigned at gcc dot gnu.org Reporter: dmalcolm at gcc dot gnu.org Created attachment 33614 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33614&action=edit Trivial patch to add pass-instances.def to installed headers We install the header "pass_manager.h", but it can't be included by a plugin, since it includes "pass-instances.def", and we don't current install that. /home/david/coding/gcc-python/gcc-svn-4.9/install/lib/gcc/x86_64-unknown-linux-gnu/4.9.2/plugin/include/pass_manager.h:123:30: fatal error: pass-instances.def: No such file or directory #include "pass-instances.def" Affects 4.9 branch (e.g. r215685), and, I believe, trunk. Marking as [Regression] since this currently makes it impossible to access the "roots" of the pass tree ("all_passes" et al) from a plugin in 4.9+, since they were moved from being globals to being member data of the pass_manager in 4.9, hence we need to include pass_manager.h for that. (My fault, sorry: I was the one who moved these from being globals to being member data. The gcc-python-plugin needs this, and hence this is one thing blocking that plugin from being built against 4.9) Am currently verifying the obvious patch.
next reply other threads:[~2014-09-29 18:12 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-09-29 18:12 dmalcolm at gcc dot gnu.org [this message] 2014-09-30 15:41 ` [Bug plugins/63410] " dmalcolm at gcc dot gnu.org 2014-09-30 16:33 ` dmalcolm at gcc dot gnu.org 2014-09-30 16:33 ` dmalcolm 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-63410-4@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: 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).