[Bug libfortran/19303] Unformatted record header is 4-bytes on 32-bit targets

2005-05-31 Thread blime at cox dot net
--- Additional Comments From blime at cox dot net 2005-05-31 14:04 --- Subject: Re: Unformatted record header is 4-bytes on 32-bit targets I second the "thanks a million", and also don't think g77 belongs in the option name. I have been using a very fast sort pr

[Bug fortran/21673] gfortran binary file format

2005-05-19 Thread blime at cox dot net
--- Additional Comments From blime at cox dot net 2005-05-20 00:58 --- Subject: Re: gfortran binary file format Thanks for pointing me to the background. I searched, but used the wrong words. I also recall something about 32 bit initial implementation for gfortran in gcc-4.0, and a

[Bug fortran/21673] New: gfortran binary file format

2005-05-19 Thread blime at cox dot net
rtran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: blime at cox dot net CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21673

[Bug fortran/21570] Unformatted sequential read/write

2005-05-15 Thread blime at cox dot net
--- Additional Comments From blime at cox dot net 2005-05-15 13:59 --- Subject: Re: Unformatted sequential read/write Okay - Its 32 bit -- but sorry I don't understand portable (one computer involved) or target? What I have been doing over the last couple of months is testin

[Bug fortran/21570] New: Unformatted sequential read/write

2005-05-14 Thread blime at cox dot net
Version: 4.0.0 Status: UNCONFIRMED Severity: critical Priority: P1 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: blime at cox dot net CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.or

[Bug fortran/21253] Bounds Check

2005-04-27 Thread blime at cox dot net
--- Additional Comments From blime at cox dot net 2005-04-27 17:58 --- Subject: Re: Bounds Check Sorry, I do not have a simple test case, but might be able to construct one if part 1 is solved. blime pinskia at gcc dot gnu dot org wrote: >--- Additional Comments From pins

[Bug fortran/21253] New: Bounds Check

2005-04-27 Thread blime at cox dot net
ry: Bounds Check Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: blime at cox dot net CC: gcc-bugs at g

[Bug fortran/20235] Gfortran internal read error

2005-02-27 Thread blime at cox dot net
--- Additional Comments From blime at cox dot net 2005-02-27 17:26 --- added input data to bug 20236 omitted in 20235 bug report -- What|Removed |Added BugsThisDependsOn

[Bug fortran/20236] Gfortran internal read error

2005-02-27 Thread blime at cox dot net
-- What|Removed |Added OtherBugsDependingO||20235 nThis|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20236

[Bug fortran/20236] New: Gfortran internal read error

2005-02-27 Thread blime at cox dot net
rsion: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: blime at cox dot net CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20236

[Bug fortran/20235] New: Gfortran internal read error

2005-02-27 Thread blime at cox dot net
: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: blime at cox dot net CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20235