Add a flag which causes equivalent data constructors in the same module to use a single info table (per-module distinct constructor tables)
Distinct constructor tables can bloat the size of an executable due to each allocation site getting its own info table.
It would be good to add a flag that which causes every occurrence of the same data constructor within a single module to use the same info table. This would allow you to determine, per module, the allocations coming from a certain constructor. Once you knew which modules were "hotspots", you could "zoom in" and do a more targeted profile using the normal -fdistinct-constructor-tables (especially with !10958). This would also result in smaller executables than with -finfo-table-map -fdistinct-constructor-tables.