[Bug target/49743] -g enables var_tracking on -O0 - causes long compilations

2019-01-02 Thread gary at intrepid dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49743

--- Comment #5 from Gary Funck  ---
(In reply to Eric Gallager from comment #4)
> Any plans to resubmit the GUPC branch again?

Eric, no not at this time.  Thanks.

[Bug target/49743] -g enables var_tracking on -O0 - causes long compilations

2019-01-02 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49743

--- Comment #4 from Eric Gallager  ---
(In reply to Gary Funck from comment #3)
> 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?

Any plans to resubmit the GUPC branch again?

[Bug target/49743] -g enables var_tracking on -O0 - causes long compilations

2012-08-27 Thread gary at intrepid dot com
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?


[Bug target/49743] -g enables var_tracking on -O0 - causes long compilations

2011-07-15 Thread nenadv at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49743

--- Comment #2 from nenadv at gcc dot gnu.org 2011-07-16 01:06:53 UTC ---
Author: nenadv
Date: Sat Jul 16 01:06:51 2011
New Revision: 176348

URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=176348
Log:
2011-07-15  Nenad Vukicevic ne...@intrepid.com

* config/darwin.c: Disable var_tracking option
  on -O0 as it is supposed to run only when optimization
  is applied. See GCC bug 49743. 'upcfish' test was
  taking to long to compile.

Modified:
branches/gupc/gcc/ChangeLog.upc
branches/gupc/gcc/config/darwin.c


[Bug target/49743] -g enables var_tracking on -O0 - causes long compilations

2011-07-14 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49743

Richard Guenther rguenth at gcc dot gnu.org changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2011.07.14 09:09:24
  Component|c   |target
 Ever Confirmed|0   |1

--- Comment #1 from Richard Guenther rguenth at gcc dot gnu.org 2011-07-14 
09:09:24 UTC ---
var-tracking isn't supposed to run at -O0.