[Bug tree-optimization/20168] const function causes the creation of GLOBAL_VAR

2010-07-13 Thread steven at gcc dot gnu dot org
--- Comment #5 from steven at gcc dot gnu dot org 2010-07-13 11:00 --- Insofar something that doesn't exist anymore can be considered broken, this bug is FIXED: ;; Function x (x) x () { intD.0 aD.1233; intD.0 D.1983; # BLOCK 2 freq:1 # PRED: ENTRY [100.0%]

[Bug tree-optimization/20168] const function causes the creation of GLOBAL_VAR

2006-03-13 Thread pinskia at gcc dot gnu dot org
--- Comment #4 from pinskia at gcc dot gnu dot org 2006-03-14 01:28 --- Huh, I still get a .global_var as of yesterday: # .GLOBAL_VAR_6 = V_MAY_DEF .GLOBAL_VAR_5; bambam (); -- pinskia at gcc dot gnu dot org changed: What|Removed |Added

[Bug tree-optimization/20168] const function causes the creation of GLOBAL_VAR

2006-03-10 Thread dnovillo at gcc dot gnu dot org
--- Comment #3 from dnovillo at gcc dot gnu dot org 2006-03-10 15:36 --- Fixed in 4.2. -- dnovillo at gcc dot gnu dot org changed: What|Removed |Added

[Bug tree-optimization/20168] const function causes the creation of GLOBAL_VAR

2005-02-23 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-23 15:43 --- Changing this for Diego. -- What|Removed |Added Severity|normal

[Bug tree-optimization/20168] const function causes the creation of GLOBAL_VAR

2005-02-23 Thread hp at gcc dot gnu dot org
--- Additional Comments From hp at gcc dot gnu dot org 2005-02-23 15:45 --- It deserves mentioning (for the audience) that the right thing happens for the generated code in the test-case; this problem is mainly an internal wart (IIUC): ... dnovillo now, the problem is that if there is a