tree 60076078abd1b823bb7ed695db1addec40c81312
parent eb3a183b900889e1d1d8d5edc13e1b7aa26dcab6
author Googler <noreply@google.com> 1531213151 -0700
committer Copybara-Service <copybara-piper@google.com> 1531213231 -0700

Restructure the NestedSet usage in CcCompilationContext. Goals:
- Don't use NestedSets of NestedSets. Not sure whether this is a performance
  improvement or has serialization benefits, but it does make understanding the
  structure a lot easier.
- Use the same large NestedSet for all header information (whether or not they
  are modular and what pregrepped headers might exist). This speeds up the
  include scanner calls getLegalGeneratedScannerFileMap and getModularHeaders
  because they now iterate over just a single NestedSet and the second
  evaluation of a NestedSet is much cheaper. In a subsequent change, we can
  likely fold all three iterations over this NestedSet into one (in
  getLegalGeneratedScannerFileMap, getModularHeaders and getUsedModules).

Measurements show a small reduction in heap usage.

RELNOTES: None.
PiperOrigin-RevId: 203909308