[Bug tree-optimization/20168] const function causes the creation of GLOBAL_VAR
--- 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%] (fallthru,exec) aD.1233_1 = constfunD.1227 (); # .MEMD.1986_5 = VDEF .MEMD.1986_4(D) # USE = nonlocal # CLB = nonlocal bambamD.1229 (); D.1983_3 = aD.1233_1 + aD.1233_1; return D.1983_3; # SUCC: EXIT [100.0%] } -- steven at gcc dot gnu dot org changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20168
[Bug tree-optimization/20168] const function causes the creation of GLOBAL_VAR
--- 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 Status|RESOLVED|REOPENED Resolution|FIXED | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20168
[Bug tree-optimization/20168] const function causes the creation of GLOBAL_VAR
--- 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 Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20168
[Bug tree-optimization/20168] const function causes the creation of GLOBAL_VAR
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-23 15:43 --- Changing this for Diego. -- What|Removed |Added Severity|normal |enhancement Keywords|missed-optimization | Summary|[4.0 regression] const |const function causes the |function calls treated as |creation of GLOBAL_VAR |pure by LIM 20100 fix | Target Milestone|4.0.0 |--- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20168
[Bug tree-optimization/20168] const function causes the creation of GLOBAL_VAR
--- 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 mix of regular and 'const' functions, we will have created .GLOBAL_VAR unnecessarily. that's bad. dnovillo testing for !TREE_SIDE_EFFECTS is too broad. We don't want to consider 'const' functions. ... hp yes, but I don't know how to create a test-case for *that* ... dnovillo hp: this one is good enough. we created .GLOBAL_VAR. we shouldn't have created it. dnovillo the call to bambam shouldn't have a V_MAY_DEF for .GLOBAL_VAR -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20168