> The debugger isn't the only consumer of debug info, and other tools might need > a finer granularity than a GIMPLE location, so clearing EXPR_LOCATION to work > around a debug info size issue seems very short-sighted (to say the least).
Hi, Eric, There might be some misunderstanding here. Clearing EXPR_LOCATION is not a work around to reduce debug size. It is aiming at making gcc implementation cleaner. And before we resetting it, we need to truely make sure nothing after gimple-low is dependent on it. Please let me know if you have other concerns. Thanks, Dehao > > -- > Eric Botcazou
