This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Traversing typedef hierarchy in C/C++ tree


Boris Kolpackov <boris@codesynthesis.com> writes:

> I was also thinking if adding an extra member would be a big deal,
> memory usage-wise. This member is only going to be added to the
> TYPE nodes (struct tree_type). I may be wrong, but I would expect
> that there aren't that many such nodes in a typical translation
> unit. Much fewer than, say, nodes that are used to build function
> bodies. Let's say we have 10,000 such nodes. Then on a 64-bit
> box we will use extra ~80Kb.

Unfortunately we have discovered over time that all the memory usage
matters.  A rule of thumb for gcc is that compilation speed is roughly
proportional to the amount of memory used.  One of the main reasons that
clang is faster than gcc is that clang uses smaller data structures.

Ian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]