[Bug fortran/32382] missed optimization in internal read

2010-02-14 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2010-02-14 08:29 --- Subject: Bug 32382 Author: jvdelisle Date: Sun Feb 14 08:28:50 2010 New Revision: 156755 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=156755 Log: 2010-02-14 Jerry DeLisle jvdeli...@gcc.gnu.org

[Bug fortran/32382] missed optimization in internal read

2010-02-14 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2010-02-14 08:33 --- Fixed on trunk. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/32382] missed optimization in internal read

2010-02-14 Thread hjl dot tools at gmail dot com
-- hjl dot tools at gmail dot com changed: What|Removed |Added Target Milestone|--- |4.5.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32382

[Bug fortran/32382] missed optimization in internal read

2010-02-12 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2010-02-13 06:17 --- Created an attachment (id=19856) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19856action=view) Prelinary patch to fix this The attached patch is preliminary. It borrows the existing gfc_trans_do code and

[Bug fortran/32382] missed optimization in internal read

2009-09-13 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2009-09-13 14:30 --- I will not have time to work on this one. Un-assigning. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/32382] missed optimization in internal read

2007-10-05 Thread manfred99 at gmx dot ch
--- Comment #5 from manfred99 at gmx dot ch 2007-10-05 09:37 --- Created an attachment (id=14299) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14299action=view) test case -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32382

[Bug fortran/32382] missed optimization in internal read

2007-10-05 Thread manfred99 at gmx dot ch
--- Comment #6 from manfred99 at gmx dot ch 2007-10-05 09:38 --- (From update of attachment 14299) sorry, for wrong bug -- manfred99 at gmx dot ch changed: What|Removed |Added

[Bug fortran/32382] missed optimization in internal read

2007-09-02 Thread manfred99 at gmx dot ch
--- Comment #3 from manfred99 at gmx dot ch 2007-09-02 11:53 --- Jerry, any news on this? I have seen this pattern many times in legacy fortran77 code, and the code authors seem to assume that ridiculously large loop stop values do not compromize performance. After all, in fortran77

[Bug fortran/32382] missed optimization in internal read

2007-09-02 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2007-09-02 16:08 --- Well, it has not been on my top burner. Looking at -fdump-tree-original the problem can be seen easily. Fixing is not so straight forward. This will probably not happen until 4.4. --

[Bug fortran/32382] missed optimization in internal read

2007-06-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2007-06-23 03:13 --- This problem is frontend related. We are building the switch case that tests for the error conditions outside the loop that is constructed to do the scaler transfers. Thus: i = 1;

[Bug fortran/32382] missed optimization in internal read

2007-06-17 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2007-06-17 20:47 --- I will explore this a bit. Its interesting. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added