This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
RE: var-track-assignment.
- From: vijay nag <vijunag at gmail dot com>
- To: "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
- Date: Mon, 25 Nov 2013 11:01:06 +0530
- Subject: RE: var-track-assignment.
- Authentication-results: sourceware.org; auth=none
Hello Gcc,
Compilation of production build(-O2 optimization turned on) of my
project is taking a very long time and on further analysis I found
that most of the compile time is eaten up by "var-tracking assignment"
gcc pass. I see significant improvements in build time If I use
"-fno-var-tracking" and also I don't intend to debug production build.
However it is important that we be able to do post-mortem analysis of
core file on production build. I tried loading a sample core-file in
gdb and could see gdb complaining "optimized out" for couple of stack
variables. So the question is, does "-fno-var-tracking" have any
impact on post-mortem analysis of core file or does it just disable
run time debugging capabilities ?