public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug plugins/61176] [4.9/4.10 Regression] plugin builds including gimple.h not building
Date: Wed, 14 May 2014 13:39:00 -0000	[thread overview]
Message-ID: <bug-61176-4-ubWxlzcMsZ@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 #7 from Andrew Macleod <amacleod at redhat dot com> ---
Thats part of the fun.  There is little rhyme nor reason to what includes what
right now.. it was purely demand driven over many years.  For your current
purposes, gimple.h and tree.h were the primary accumulators we have already
flattened, but there are a lot of include files which include 4 or 5 or 7 or
more other files. Some where flattened, others haven't been tackled yet.

We're trying to move to the include what you use model... with .h files
containing just the exports for their .c file, and a few module headers which
do some aggregation of common/required headers.  Eventually including gimple.h
alone will compile and provide basic manipulation routines, but you may still
need to include other files depending on what you actually require. 

Plugins can either follow the same model, or could have one giant accumulator
which includes everything... It sounds like the latter may be better for the
interm, but I would encourage it to revert to the same model once the work is
complete.


  parent reply	other threads:[~2014-05-14 13:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 14:01 [Bug plugins/61176] New: " 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 [this message]
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
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-ubWxlzcMsZ@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).