On Mon, Jun 19, 2017 at 3:45 AM, Richard Biener <richard.guenther@xxxxxxxxx> wrote: > On Sat, Jun 17, 2017 at 9:09 AM, Siva Narayanan <sinaraya@xxxxxxxxxx> wrote: >> Hello all, >> >> My colleague Peter managed to use "git bisect" on the git mirror of >> gcc source code. The commit from a branch called "debug-early" seems >> like a possible point when the new behavior got introduced. >> >> We have also looked at this conversation: >> https://gcc.gnu.org/ml/gcc/2015-05/msg00046.html >> >> We would like to know if this work: >> >>>Shortly after the merge I'll work on a pass to prune unused decl DIEs as >we're presently creating more DIEs than mainline. This was expected, >and if I understood Jason correctly, it is ok to work on this post-merge. >However, even without such a pass, the .debug_info size difference is >reasonable: >> >> happened along with a future commit or if there is still some work >> pending. As I wrote, in our environment the debug_info size difference >> (from earlier 5.4 version of gcc) is significant that the object file >> size change is non-trivial with gcc 6.3.1. > > To my knowledge this hasn't happened yet. Is there an open PR for this? Jason
