This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/49743] -g enables var_tracking on -O0 - causes long compilations
- From: "gary at intrepid dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 28 Aug 2012 02:20:38 +0000
- Subject: [Bug target/49743] -g enables var_tracking on -O0 - causes long compilations
- Auto-submitted: auto-generated
- References: <bug-49743-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49743
--- Comment #3 from Gary Funck <gary at intrepid dot com> 2012-08-28 02:20:38 UTC ---
Recently, I've been reviewing changes that we made on the GUPC branch (see
comment #2) that are candidates for the trunk revision (or in this case,
possibly the 4.7 branch).
Index: gcc/config/darwin.c
===================================================================
--- gcc/config/darwin.c (.../trunk) (revision 190707)
+++ gcc/config/darwin.c (.../branches/gupc) (revision 190718)
@@ -3039,6 +3039,7 @@ darwin_override_options (void)
}
if (flag_var_tracking
+ && optimize >= 1
&& generating_for_darwin_version >= 9
&& (flag_gtoggle ? (debug_info_level == DINFO_LEVEL_NONE)
: (debug_info_level >= DINFO_LEVEL_NORMAL))
Reading the problem description, unless the option scanning logic has changed
for Darwin, it looks as if this change might still be necessary to suppress var
tracking at -O0?