On Nov 9, 2012, at 1:42 AM, Eric Botcazou wrote:
> this is a regression present on the mainline and 4.7 branch. -fvar-tracking
> is automatically enabled on Darwin when -g is passed, including at -O0. This
> results in bloated and incomplete debug info.
> OK for mainline and 4.7 branch?
Ok.
>Is this a hack around the underlying problem on darwin or the
> implementation of the same approach used on other targets? If the former,
> shouldn't we have a PR opened to properly fix this in the long term?
Neither, it's a fix and other targets don't care about -fvar-tracking-uninit.
--
E
On Fri, Nov 09, 2012 at 10:42:45AM +0100, Eric Botcazou wrote:
> Hi,
>
> this is a regression present on the mainline and 4.7 branch. -fvar-tracking
> is automatically enabled on Darwin when -g is passed, including at -O0. This
> results in bloated and incomplete debug info.
>
> This comes fr
Hi,
this is a regression present on the mainline and 4.7 branch. -fvar-tracking
is automatically enabled on Darwin when -g is passed, including at -O0. This
results in bloated and incomplete debug info.
This comes from a latent issue in the handling of flag_var_tracking_uninit in
the Darwin
