Weeding out unwanted include files

sriram@tcs.com (Sriram Srinivasan)
Thu, 28 Jul 1994 00:57:56 GMT

          From comp.compilers
Related articles
Weeding out unwanted include files sriram@tcs.com (1994-07-28)
Re: Weeding out unwanted include files nandu@cs.clemson.edu (1994-07-29)
Re: Weeding out unwanted include files pzola@us.oracle.com (1994-07-30)
Re: Weeding out unwanted include files bill@amber.ssd.csd.harris.com (1994-08-02)
Re: Weeding out unwanted include files gary@Intrepid.COM (1994-08-02)
Re: Weeding out unwanted include files g9gwaigh@cdf.toronto.edu (1994-08-03)
Re: Weeding out unwanted include files zstern@adobe.com (1994-08-04)
[10 later articles]
| List of all articles for this month |
Newsgroups: comp.compilers
From: sriram@tcs.com (Sriram Srinivasan)
Keywords: C, tools, question
Organization: Teknekron Communications Systems, Berkeley, California
Date: Thu, 28 Jul 1994 00:57:56 GMT

I want to develop a tool that finds out which include files are
useless, so as to reduce compile time.


My idea was to keep track of all global declarations, such as macro
definitions, typedefs etc, and then look for usage of these declarations.
I would keep track of the include file dependencies, and identify those
include files that are not being referred to at all.


Before I embark on this decidedly non-trivial exercise, I'd like to find
out if someone else has implemented any such thing. I also welcome any
ideas you may have on the subject.


Thanx.


Sriram
(sriram@tcs.com)
--

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.