[Bug tree-optimization/20165] Pointer does not really escape with write

2010-10-16 Thread tkoenig at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20165 Thomas Koenig changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

[Bug tree-optimization/20165] Pointer does not really escape with write

2010-10-16 Thread tkoenig at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20165 --- Comment #9 from Thomas Koenig 2010-10-16 16:06:14 UTC --- Author: tkoenig Date: Sat Oct 16 16:06:07 2010 New Revision: 165559 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=165559 Log: 2010-10-16 Thomas Koenig PR fortran/20165

[Bug tree-optimization/20165] Pointer does not really escape with write

2009-09-26 Thread rguenth at gcc dot gnu dot org
--- Comment #8 from rguenth at gcc dot gnu dot org 2009-09-26 15:33 --- Mine. -- rguenth at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned

[Bug tree-optimization/20165] Pointer does not really escape with write

2009-07-02 Thread rguenther at suse dot de
--- Comment #7 from rguenther at suse dot de 2009-07-02 15:46 --- Subject: Re: Pointer does not really escape with write On Thu, 2 Jul 2009, steven at gcc dot gnu dot org wrote: > --- Comment #6 from steven at gcc dot gnu dot org 2009-07-02 15:40 > --- > Dan, you mentioned

[Bug tree-optimization/20165] Pointer does not really escape with write

2009-07-02 Thread steven at gcc dot gnu dot org
--- Comment #6 from steven at gcc dot gnu dot org 2009-07-02 15:40 --- Dan, you mentioned a "pointer_no_escape" attribute. What was that about? I've never seen that mentioned before (or a patch to implement it). Sounds like a cool attribute to have (and not just for Fortran, too). -

[Bug tree-optimization/20165] Pointer does not really escape with write

2009-06-08 Thread tkoenig at gcc dot gnu dot org
--- Comment #5 from tkoenig at gcc dot gnu dot org 2009-06-08 18:12 --- This also causes missed warnings about unitizialized variables: $ cat foo.f print *,x end $ gfortran -O3 -Wall -Wextra foo.f We should have some way of marking that pointer as read-only. -- http://

[Bug tree-optimization/20165] Pointer does not really escape with write

2007-04-16 Thread pinskia at gcc dot gnu dot org
--- Comment #4 from pinskia at gcc dot gnu dot org 2007-04-16 22:54 --- *** Bug 31593 has been marked as a duplicate of this bug. *** -- pinskia at gcc dot gnu dot org changed: What|Removed |Added ---

[Bug tree-optimization/20165] Pointer does not really escape with write

2005-08-31 Thread dberlin at gcc dot gnu dot org
--- Additional Comments From dberlin at gcc dot gnu dot org 2005-08-31 15:08 --- These should simply be marked with pointer_no_escape once that goes in -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20165

[Bug tree-optimization/20165] Pointer does not really escape with write

2005-03-01 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-03-01 18:11 --- Confirmed. -- What|Removed |Added Status|UNCONFIRMED |NEW E

[Bug tree-optimization/20165] Pointer does not really escape with write

2005-02-23 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-23 18:59 --- A C testcase (scanf this time): #include int main(void) { int i; int j; scanf("%d", &i); for(;i<=0;i--) printf("H"); return 0; } -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20165