[Bug libfortran/33298] Wrong code for SPREAD on zero-sized arrays

2007-09-06 Thread tkoenig at alice-dsl dot net
--- Comment #11 from tkoenig at alice-dsl dot net 2007-09-06 21:13 --- Subject: Re: Wrong code for SPREAD on zero-sized arrays Hi Toon, --- Comment #8 from toon at moene dot indiv dot nluug dot nl 2007-09-06 08:56 --- Wouldn't it be an option to simply bail out

[Bug libfortran/32954] mask and -fdefault-integer-8

2007-08-01 Thread tkoenig at alice-dsl dot net
--- Comment #7 from tkoenig at alice-dsl dot net 2007-08-01 17:46 --- Subject: Re: mask and -fdefault-integer-8 On Wed, 2007-08-01 at 15:36 +, dominiq at lps dot ens dot fr wrote: --- Comment #5 from dominiq at lps dot ens dot fr 2007-08-01 15:36 --- I have had

[Bug fortran/32131] knowing that stride==1 when using allocated arrays and escaping allocatable arrays

2007-05-29 Thread tkoenig at alice-dsl dot net
--- Comment #5 from tkoenig at alice-dsl dot net 2007-05-29 17:47 --- Subject: Re: knowing that stride==1 when using allocated arrays and escaping allocatable arrays On Tue, 2007-05-29 at 04:52 +, pinskia at gcc dot gnu dot org wrote: we think we change a's stride which

[Bug fortran/31366] Last record truncated for read after short write, direct access file

2007-03-31 Thread tkoenig at alice-dsl dot net
--- Comment #7 from tkoenig at alice-dsl dot net 2007-03-31 08:11 --- Subject: Re: Last record truncated for read after short write, direct access file On Sat, 2007-03-31 at 00:45 +, jvdelisle at gcc dot gnu dot org wrote: Michael sent me this excellent test case

[Bug fortran/31196] wrong code generated with RESHAPE/TRANSPOSE

2007-03-24 Thread tkoenig at alice-dsl dot net
--- Comment #3 from tkoenig at alice-dsl dot net 2007-03-24 21:35 --- Created an attachment (id=13278) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13278action=view) proposed patch This should fix it. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31196

[Bug libfortran/31297] Use of uninitialized variables in libgfortran's I/O

2007-03-24 Thread tkoenig at alice-dsl dot net
--- Comment #1 from tkoenig at alice-dsl dot net 2007-03-24 22:17 --- This is a bug in the test case. I'll commit a correct version. Thomas -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31297

[Bug libfortran/31297] Use of uninitialized variables in libgfortran's I/O

2007-03-24 Thread tkoenig at alice-dsl dot net
--- Comment #2 from tkoenig at alice-dsl dot net 2007-03-24 22:44 --- Created an attachment (id=13279) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13279action=view) patch for the test cases All but one of these were errors in the test cases, which are corrected with this patch

[Bug libfortran/31297] Use of uninitialized variables in libgfortran's I/O

2007-03-24 Thread tkoenig at alice-dsl dot net
--- Comment #3 from tkoenig at alice-dsl dot net 2007-03-24 23:07 --- Created an attachment (id=13280) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13280action=view) proposed patch This one also fixes the last case. It does so by reading size bytes instead of the kind number

[Bug fortran/31295] Uninitialized variable in libgfortran's _gfortran_eoshift0_4

2007-03-23 Thread tkoenig at alice-dsl dot net
--- Comment #1 from tkoenig at alice-dsl dot net 2007-03-23 20:14 --- The eoshift.f90 case is 'mostly harmless'. We are doing calculations with the value, but don't actually use this for anything. We can fix this (cosmetic fix for valgrind, really) by setting sstride[0] to an arbitray