From: Michael Matz <matz@suse.de>
To: gcc Patches <gcc-patches@gcc.gnu.org>
Subject: Re: flatten cfgloop.h
Date: Mon, 06 Jul 2015 13:38:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1507061534350.23227@wotan.suse.de> (raw)
In-Reply-To: <CAAgBjMnkJNFMT00Y8xP9R_6xxdFwfvOUAiu-Jf+e8cJGBGdU6A@mail.gmail.com>
Hi,
On Sun, 5 Jul 2015, Prathamesh Kulkarni wrote:
> Hi,
> The attached patches flatten cfgloop.h.
> patch-1.diff moves around prototypes and structures to respective header-files.
> patch-2.diff (mostly auto-generated) replicates cfgloop.h includes in c files.
> Bootstrapped and tested on x86_64-unknown-linux-gnu with all front-ends.
> Built on all targets using config-list.mk.
> I left includes in cfgloop.h commented with #if 0 ... #endif.
> OK for trunk ?
Does nobody else think that header files for one or two prototypes are
fairly silly?
Anyway, your autogenerated part contains changes that seem exaggerated,
e.g.:
+++ b/gcc/bt-load.c
@@ -54,6 +54,14 @@ along with GCC; see the file COPYING3. If not see
#include "predict.h"
#include "basic-block.h"
#include "df.h"
+#include "bitmap.h"
+#include "sbitmap.h"
+#include "cfgloopmanip.h"
+#include "loop-init.h"
+#include "cfgloopanal.h"
+#include "loop-doloop.h"
+#include "loop-invariant.h"
+#include "loop-iv.h"
Surely bt-load doesn't need anything from doloop.h or invariant.h. Before
this goes into trunk this whole autogenerated thing should be cleaned up
to add includes only for things that are actually needed.
Ciao,
Michael.
next prev parent reply other threads:[~2015-07-06 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-05 13:25 Prathamesh Kulkarni
2015-07-06 13:38 ` Michael Matz [this message]
2015-07-06 15:26 ` Andrew MacLeod
2015-07-06 18:11 ` Jeff Law
2015-07-07 8:47 ` Richard Biener
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=alpine.LSU.2.20.1507061534350.23227@wotan.suse.de \
--to=matz@suse.de \
--cc=gcc-patches@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).