Adjust Variable Tracking Assignment Length

c++ gcc compiler-options
paxos1977 picture paxos1977 · May 6, 2014 · Viewed 13.2k times · Source

In a release build I'm getting the following informational warning from GCC 4.4.7.

note: variable tracking size limit exceeded with -fvar-tracking-assignments, retrying without

Have I exceeded the variable name length supported by variable tracking assignment?
If so, is there a way to adjust the supported size?

Answer

Öö Tiib picture Öö Tiib · May 6, 2014

This is just a note from the compiler that the debug info for the particular function will have lower quality, because your code of function is too large/complex so variable tracking reached limit of hash table slots.

The max is likely lot of millions and it can be raised with something (like --param=max-vartrack-size=60000000) but you could end up with very slow compilation or the compiler could take very lot of memory to compute the debug info location lists.

So unless you have trouble debugging the code just ignore that warning.

Related questions

What does the fpermissive flag do?

I'm just wondering what the -fpermissive flag does in the g++ compiler? I am getting: error: taking address of temporary [-fpermissive] which I can solve by giving the -fpermissive flag to the compiler. EDIT: I just found what was causing …

Read More
How to disable narrowing conversion warnings?

I use -Wall and updating to new gcc I have got a lot of warning: narrowing conversion. I want to disable them, but leave all other warnings untouched (ideally). I can find nothing about narrowing in http://gcc.gnu.org/…

Read More
What's the difference in GCC between -std=gnu++0x and -std=c++0x and which one should be used?

I'm having troubles with <stdint.h> when using -std=c++0x in GCC 4.4.3 (for Android): // using -std=c++0x #include <stdint.h> uint64_t value; // error: 'uint64_t' does not name a type But using -std=…

Read More