On 05/15/2012 10:17 AM, Dodji Seketeli wrote:
It fixes the test case gcc.dg/cpp/paste12.c because that test case runs with -ftrack-macro-expansion turned off. Otherwise, you are right that the issue exists only when we aren't tracking virtual locations.
I still don't understand why this change should be needed; it seems like a kludge disguised as a trivial change from one function to another. If we're going to kludge, I'd rather explicitly set the flag with a comment.
But why do we need the set_invocation_location flag at all? When do we not want to set invocation_location if we're beginning to expand a macro?
Jason
