https://gcc.gnu.org/bugzilla/show_bug.cgi?id=126801
Bug ID: 126801
Summary: [13/14/15/16/17 Regression] fvar-tracking-uninit is on
by accident via r12-4397
Product: gcc
Version: 17.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: pinskia at gcc dot gnu.org
Target Milestone: ---
>From what I can tell -fvar-tracking-uninit should not be on by default. It
should only be on if supplied by an option.
>From I gathered was r0-120247-g1267ca30d1bf95 which changed the behavior
slightly but the initial value of flag_var_tracking_uninit was not set to
AUTODETECT_VALUE; it was kept at 0. Rather later on with
r12-4397-g4cb52980e5d5fb which changed the behavior thinking the initial value
of flag_var_tracking_uninit was 2.
At one point it was mentioned -fvar-tracking-uninit should be removed and
should not have been added to GCC either.
https://gcc.gnu.org/pipermail/gcc/2015-July/218202.html
I wonder if we should just finally remove it from GCC 17 then.
