public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug plugins/61176] plugin builds including gimple.h not building Date: Thu, 26 Mar 2015 10:57:00 -0000 [thread overview] Message-ID: <bug-61176-4-zWK6a1OHwV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61176-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61176 --- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> --- And comparing the right now installed headers with what is in gcc/*.h gcc/*.def reveals also: addresses.h asan.h bb-reorder.h builtin-attrs.def builtins.h builtin-types.def cilk.h collect2-aix.h collect2.h conditions.h convert.h coverage.h cppbuiltin.h cselib.h data-streamer.h dbgcnt.def dbgcnt.h dbxout.h dce.h ddg.h dfp.h domwalk.h dwarf2asm.h dwarf2out.h errors.h et-forest.h expmed.h expr.h file-find.h gcc.h gcov-counter.def gcov-io.h gcse.h gengtype.h gensupport.h ggc-internal.h gimple-streamer.h glimits.h graphds.h graph.h graphite-poly.h graphite-scop-detection.h graphite-sese-to-poly.h gstab.h gsyms.h gsyslimits.h hooks.h hosthooks-def.h hosthooks.h hw-doloop.h insn-addr.h ipa-inline.h ira.h ira-int.h langhooks-def.h libfuncs.h limitx.h limity.h lower-subreg.h lra.h lra-int.h lto-compress.h lto-streamer.h machmode.def omega.h omp-low.h optabs.def optabs.h opts-diagnostic.h passes.def profile.h read-md.h recog.h regrename.h regs.h reload.h rtl-error.h rtlhooks-def.h sched-int.h sdbout.h sel-sched-dump.h sel-sched.h sel-sched-ir.h sese.h sparseset.h sreal.h stab.def streamer-hooks.h target-def.h target-globals.h targhooks.h trans-mem.h tree-affine.h tree-browser.def tree-chrec.h tree-data-ref.h tree-diagnostic.h tree-scalar-evolution.h tree-ssa-live.h tree-ssa-propagate.h tree-stdarg.h tree-streamer.h tree-vectorizer.h tsan.h tsystem.h typeclass.h ubsan.h valtrack.h value-prof.h vmsdbg.h vtable-verify.h xcoff.h xcoffout.h (already existing in 4.9). So, how do we decide which of these headers are interesting to plugin writers?
next prev parent reply other threads:[~2015-03-26 10:36 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-05-13 14:01 [Bug plugins/61176] New: [4.9/4.10 Regression] " doko at gcc dot gnu.org 2014-05-13 14:41 ` [Bug plugins/61176] " rguenth at gcc dot gnu.org 2014-05-14 8:51 ` doko at gcc dot gnu.org 2014-05-14 10:00 ` jakub at gcc dot gnu.org 2014-05-14 12:14 ` amacleod at redhat dot com 2014-05-14 12:21 ` amacleod at redhat dot com 2014-05-14 12:38 ` doko at ubuntu dot com 2014-05-14 13:39 ` amacleod at redhat dot com 2014-05-25 20:07 ` pageexec at gmail dot com 2014-05-26 4:20 ` amacleod at redhat dot com 2014-07-16 13:27 ` jakub at gcc dot gnu.org 2014-10-30 10:38 ` [Bug plugins/61176] [4.9/5 " jakub at gcc dot gnu.org 2014-12-01 12:03 ` [Bug plugins/61176] " rguenth at gcc dot gnu.org 2014-12-01 13:58 ` amacleod at redhat dot com 2015-03-26 5:58 ` pageexec at gmail dot com 2015-03-26 10:56 ` jakub at gcc dot gnu.org 2015-03-26 10:57 ` jakub at gcc dot gnu.org [this message] 2015-03-26 11:06 ` jakub at gcc dot gnu.org 2015-03-26 12:41 ` pageexec at gmail dot com 2015-03-31 8:30 ` jakub at gcc dot gnu.org 2023-05-06 18:41 ` pinskia 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-61176-4-zWK6a1OHwV@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).