[Bug libfortran/25594] New: LAPACK regression in schkbl.f

2005-12-28 Thread jvdelisle at gcc dot gnu dot org
Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libfortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jvdelisle at gcc dot gnu dot org GCC host triplet: i686-pc-lin

[Bug libfortran/25594] LAPACK regression in schkbl.f

2005-12-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2005-12-28 23:37 --- This regression was with 4.2 with no compiler options. I will check 4.1 later today. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25594

[Bug libfortran/25594] LAPACK regression in schkbl.f

2005-12-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2005-12-28 23:55 --- I do not see this failure with 4.1 so that pretty much points to something I did. I will withhold my recent patches to 4.2 from 4.1 until I figure this out. The failed line of code is: READ( NIN, FMT

[Bug libfortran/25594] LAPACK regression in schkbl.f

2005-12-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2005-12-29 04:26 --- I have isolated this to the patch for PR25419. Will be studying this one some more. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25594

[Bug libfortran/25598] gfortran - Fortran runtime error: Invalid argument

2005-12-29 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2005-12-30 04:39 --- Confirmed. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/25598] gfortran - Fortran runtime error: Invalid argument

2005-12-29 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2005-12-30 06:17 --- This test case does not fail with 4.0.3. That makes this a regression. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25598

[Bug libfortran/25419] gfortran read does not take comma for default on one entry

2005-12-29 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2005-12-30 07:03 --- The patch in comment #2 causes PR25594. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25419

[Bug libfortran/25594] LAPACK regression in schkbl.f

2005-12-31 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2006-01-01 02:45 --- Subject: Bug 25594 Author: jvdelisle Date: Sun Jan 1 02:45:22 2006 New Revision: 109211 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109211 Log: 2005-12-31 Jerry DeLisle <[EMAI

[Bug libfortran/25419] gfortran read does not take comma for default on one entry

2005-12-31 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-01-01 02:45 --- Subject: Bug 25419 Author: jvdelisle Date: Sun Jan 1 02:45:22 2006 New Revision: 109211 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109211 Log: 2005-12-31 Jerry DeLisle <[EMAI

[Bug fortran/5900] [g77 & gfortran] Lapack regressions since g77 2.95.2

2005-12-31 Thread jvdelisle at gcc dot gnu dot org
--- Comment #55 from jvdelisle at gcc dot gnu dot org 2006-01-01 02:50 --- $ gfc -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../main/configure --prefix=/home/jerry/gcc/usr --enable-languages=c,fortran --disable-libmudflap Thread model: posix gcc version 4.2.0

[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-31 Thread jvdelisle at gcc dot gnu dot org
--- Comment #35 from jvdelisle at gcc dot gnu dot org 2006-01-01 03:49 --- Subject: Bug 25139 Author: jvdelisle Date: Sun Jan 1 03:49:00 2006 New Revision: 109212 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109212 Log: 2005-12-31 Jerry DeLisle <[EMAI

[Bug libfortran/25510] Add ERROR_INTERNAL and ERROR_INTERNAL_UNIT

2005-12-31 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2006-01-01 03:49 --- Subject: Bug 25510 Author: jvdelisle Date: Sun Jan 1 03:49:00 2006 New Revision: 109212 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109212 Log: 2005-12-31 Jerry DeLisle <[EMAI

[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-31 Thread jvdelisle at gcc dot gnu dot org
--- Comment #36 from jvdelisle at gcc dot gnu dot org 2006-01-01 03:53 --- Subject: Bug 25139 Author: jvdelisle Date: Sun Jan 1 03:53:12 2006 New Revision: 109213 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109213 Log: 2005-12-31 Jerry DeLisle <[EMAI

[Bug libfortran/25550] file data corrupted after reading end of file

2005-12-31 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2006-01-01 04:16 --- Subject: Bug 25550 Author: jvdelisle Date: Sun Jan 1 04:16:39 2006 New Revision: 109214 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109214 Log: 2005-12-31 Jerry DeLisle <[EMAI

[Bug libfortran/25550] file data corrupted after reading end of file

2005-12-31 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-01-01 04:20 --- Subject: Bug 25550 Author: jvdelisle Date: Sun Jan 1 04:20:41 2006 New Revision: 109215 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109215 Log: 2005-12-31 Jerry DeLisle <[EMAI

[Bug libfortran/25419] gfortran read does not take comma for default on one entry

2005-12-31 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2006-01-01 05:04 --- Subject: Bug 25419 Author: jvdelisle Date: Sun Jan 1 05:04:06 2006 New Revision: 109216 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109216 Log: 2005-12-31 Jerry DeLisle <[EMAI

[Bug libfortran/25594] LAPACK regression in schkbl.f

2005-12-31 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-01-01 05:04 --- Subject: Bug 25594 Author: jvdelisle Date: Sun Jan 1 05:04:06 2006 New Revision: 109216 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109216 Log: 2005-12-31 Jerry DeLisle <[EMAI

[Bug libfortran/25419] gfortran read does not take comma for default on one entry

2005-12-31 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2006-01-01 05:06 --- Subject: Bug 25419 Author: jvdelisle Date: Sun Jan 1 05:06:05 2006 New Revision: 109217 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109217 Log: 2005-12-28 Jerry DeLisle <[EMAI

[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-31 Thread jvdelisle at gcc dot gnu dot org
--- Comment #37 from jvdelisle at gcc dot gnu dot org 2006-01-01 05:14 --- Fixed on 4.1 and 4.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/25419] gfortran read does not take comma for default on one entry

2005-12-31 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2006-01-01 05:16 --- Fixed on 4.1 and 4.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/25510] Add ERROR_INTERNAL and ERROR_INTERNAL_UNIT

2005-12-31 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-01-01 05:16 --- Completed on 4.1 and 4.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/25550] file data corrupted after reading end of file

2005-12-31 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2006-01-01 05:19 --- Fixed on 4.1 and 4.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/25594] LAPACK regression in schkbl.f

2005-12-31 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2006-01-01 05:21 --- Fixed on 4.2 and avoided on 4.1 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/25598] gfortran - Fortran runtime error: Invalid argument

2005-12-31 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2006-01-01 05:36 --- I have started looking into this one. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/25631] New: tl format specifier not working correctly

2006-01-01 Thread jvdelisle at gcc dot gnu dot org
ectly Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jvdelisle at gcc dot gnu dot org GCC host triplet:

[Bug fortran/24268] gfortran rejects valid format statement

2006-01-02 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2006-01-02 08:13 --- Submitted a new patch for approval that is a final fix for this bug. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/24268] gfortran rejects valid format statement

2006-01-02 Thread jvdelisle at gcc dot gnu dot org
-- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added GCC target triplet|4.1 | Target Milestone|--- |4.1.0 http

[Bug libfortran/25598] [4.1/4.2 Regression] gfortran - Fortran runtime error: Invalid argument

2006-01-02 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2006-01-03 05:30 --- Submitting patch for review. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25598

[Bug libfortran/25631] tl format specifier not working correctly

2006-01-02 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2006-01-03 07:16 --- TL does not take into account pending spaces and skips when no bytes have been used yet so it 'thinks' that it is at the beginning of the record and can not go left. -- jvdelisle at gcc dot g

[Bug fortran/24886] another runtime error goes undetected

2006-01-03 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2006-01-04 03:25 --- This is not a bug. gfortran behavior is identical to ifort. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24886

[Bug fortran/24268] gfortran rejects valid format statement

2006-01-05 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2006-01-06 01:22 --- Subject: Bug 24268 Author: jvdelisle Date: Fri Jan 6 01:21:56 2006 New Revision: 109402 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109402 Log: 2006-01-01 Jerry DeLisle <[EMAI

[Bug fortran/24268] gfortran rejects valid format statement

2006-01-05 Thread jvdelisle at gcc dot gnu dot org
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2006-01-06 01:28 --- Subject: Bug 24268 Author: jvdelisle Date: Fri Jan 6 01:28:40 2006 New Revision: 109404 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109404 Log: 2005-01-05 Jerry DeLisle <[EMAI

[Bug libfortran/25598] [4.1/4.2 Regression] gfortran - Fortran runtime error: Invalid argument

2006-01-05 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-01-06 01:39 --- Subject: Bug 25598 Author: jvdelisle Date: Fri Jan 6 01:39:34 2006 New Revision: 109405 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109405 Log: 2006-01-05 Jerry DeLisle <[EMAI

[Bug libfortran/25598] [4.1/4.2 Regression] gfortran - Fortran runtime error: Invalid argument

2006-01-05 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2006-01-06 01:44 --- Subject: Bug 25598 Author: jvdelisle Date: Fri Jan 6 01:44:31 2006 New Revision: 109406 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109406 Log: 2005-01-05 Jerry DeLisle <[EMAI

[Bug libfortran/25598] [4.1/4.2 Regression] gfortran - Fortran runtime error: Invalid argument

2006-01-05 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2006-01-06 05:21 --- Subject: Bug 25598 Author: jvdelisle Date: Fri Jan 6 05:21:01 2006 New Revision: 109408 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109408 Log: 2006-01-05 Jerry DeLisle <[EMAI

[Bug libfortran/25697] libfortran - Segmentation fault/ Bad Address on unformatted read

2006-01-06 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2006-01-07 00:59 --- Confirmed -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status

[Bug fortran/24268] gfortran rejects valid format statement

2006-01-07 Thread jvdelisle at gcc dot gnu dot org
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2006-01-08 01:53 --- Subject: Bug 24268 Author: jvdelisle Date: Sun Jan 8 01:53:06 2006 New Revision: 109467 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109467 Log: 2006-01-07 Jerry DeLisle <[EMAI

[Bug fortran/24268] gfortran rejects valid format statement

2006-01-07 Thread jvdelisle at gcc dot gnu dot org
--- Comment #14 from jvdelisle at gcc dot gnu dot org 2006-01-08 01:56 --- Subject: Bug 24268 Author: jvdelisle Date: Sun Jan 8 01:56:22 2006 New Revision: 109468 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109468 Log: 2005-01-07 Jerry DeLisle <[EMAI

[Bug libfortran/25598] [4.1/4.2 Regression] gfortran - Fortran runtime error: Invalid argument

2006-01-07 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2006-01-08 02:16 --- Subject: Bug 25598 Author: jvdelisle Date: Sun Jan 8 02:16:11 2006 New Revision: 109469 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109469 Log: 2006-01-07 Jerry DeLisle <[EMAI

[Bug libfortran/25598] [4.1/4.2 Regression] gfortran - Fortran runtime error: Invalid argument

2006-01-07 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2006-01-08 02:17 --- Subject: Bug 25598 Author: jvdelisle Date: Sun Jan 8 02:17:54 2006 New Revision: 109470 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109470 Log: 2005-01-07 Jerry DeLisle <[EMAI

[Bug libfortran/25598] [4.1/4.2 Regression] gfortran - Fortran runtime error: Invalid argument

2006-01-07 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2006-01-08 02:21 --- Fixed in 4.1 and 4.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/24268] gfortran rejects valid format statement

2006-01-07 Thread jvdelisle at gcc dot gnu dot org
--- Comment #15 from jvdelisle at gcc dot gnu dot org 2006-01-08 02:22 --- Fixed on 4.1 and 4.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/25631] tl format specifier not working correctly

2006-01-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2006-01-08 09:39 --- Patch submitted for review. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25631

[Bug libfortran/25697] libfortran - Segmentation fault/ Bad Address on unformatted read

2006-01-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2006-01-08 09:40 --- I will take a gander at this. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/25697] libfortran - Segmentation fault/ Bad Address on unformatted read

2006-01-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-01-09 05:27 --- This one is cute. We have user space data showing up in the bytes_left counter. Really! I may have found the root of all evils. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25697

[Bug libfortran/25697] libfortran - Segmentation fault/ Bad Address on unformatted read

2006-01-10 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2006-01-11 03:45 --- Created an attachment (id=10618) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10618&action=view) Prposed patch for pr 25697 Dale, can you give this s spin. I think this fixes it. --

[Bug libfortran/25697] libfortran - Segmentation fault/ Bad Address on unformatted read

2006-01-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2006-01-12 06:46 --- This is interesting. I noticed before that with the previous test case i could get two different error message depending on the size of the data. I will have to study this a bit closer. BTW Thanks for the

[Bug libfortran/25631] tl format specifier not working correctly

2006-01-17 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2006-01-18 00:52 --- Subject: Bug 25631 Author: jvdelisle Date: Wed Jan 18 00:52:21 2006 New Revision: 109858 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109858 Log: 2006-01-17 Jerry DeLisle <[EMAI

[Bug libfortran/25631] tl format specifier not working correctly

2006-01-17 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-01-18 01:06 --- Subject: Bug 25631 Author: jvdelisle Date: Wed Jan 18 01:06:08 2006 New Revision: 109860 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109860 Log: 2006-01-17 Jerry DeLisle <[EMAI

[Bug libfortran/25835] New: Segfault or Bad Address error on unformatted sequential READ

2006-01-17 Thread jvdelisle at gcc dot gnu dot org
ity: normal Priority: P3 Component: libfortran AssignedTo: jvdelisle at gcc dot gnu dot org ReportedBy: jvdelisle at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25835

[Bug libfortran/25835] Segfault or Bad Address error on unformatted sequential READ

2006-01-17 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2006-01-18 02:12 --- The following chunk from fd_alloc is where the problem occurs. Get rid of setting active to zero and the error goes away, but regression occurs in direct_io_2.f90. Perhaps active needs to be set to zero

[Bug libfortran/25631] tl format specifier not working correctly

2006-01-17 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2006-01-18 04:27 --- Subject: Bug 25631 Author: jvdelisle Date: Wed Jan 18 04:27:31 2006 New Revision: 109868 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109868 Log: 2006-01-17 Jerry DeLisle <[EMAI

[Bug libfortran/25631] tl format specifier not working correctly

2006-01-17 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2006-01-18 04:32 --- Subject: Bug 25631 Author: jvdelisle Date: Wed Jan 18 04:32:16 2006 New Revision: 109869 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109869 Log: 2006-01-17 Jerry DeLisle <[EMAI

[Bug libfortran/25697] libfortran - Segmentation fault/ Bad Address on unformatted read

2006-01-17 Thread jvdelisle at gcc dot gnu dot org
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2006-01-18 06:21 --- Subject: Bug 25697 Author: jvdelisle Date: Wed Jan 18 06:21:28 2006 New Revision: 109870 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109870 Log: 2006-01-17 Jerry DeLisle <[EMAI

[Bug libfortran/25697] libfortran - Segmentation fault/ Bad Address on unformatted read

2006-01-17 Thread jvdelisle at gcc dot gnu dot org
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2006-01-18 06:23 --- Subject: Bug 25697 Author: jvdelisle Date: Wed Jan 18 06:23:24 2006 New Revision: 109872 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109872 Log: 2006-01-17 Jerry DeLisle <[EMAI

[Bug libfortran/25697] libfortran - Segmentation fault/ Bad Address on unformatted read

2006-01-17 Thread jvdelisle at gcc dot gnu dot org
--- Comment #14 from jvdelisle at gcc dot gnu dot org 2006-01-18 06:41 --- Fixed on 4.2, will commit to 4.1 in a few days. PR 25835 remains a separate problem. Cases in comment #8 and #9 go to PR25835. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25697

[Bug libfortran/25697] libfortran - Segmentation fault/ Bad Address on unformatted read

2006-01-17 Thread jvdelisle at gcc dot gnu dot org
-- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|--- |4.1.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25697

[Bug libfortran/25631] tl format specifier not working correctly

2006-01-17 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2006-01-18 06:48 --- Fixed on 4.1 and 4.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/28339] gfortran misses a record from a format statement

2006-07-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2006-07-19 05:32 --- Well, I have found the problem here, but still need to formulate the solution. For internal units, if the bytes left in a record is zero we break out of the next_record_w function. Not a good thing

[Bug fortran/28339] gfortran misses a record from a format statement

2006-07-21 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-07-22 03:14 --- Subject: Bug 28339 Author: jvdelisle Date: Sat Jul 22 03:14:27 2006 New Revision: 115670 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=115670 Log: 2006-07-21 Jerry DeLisle <[EMAI

[Bug fortran/28339] gfortran misses a record from a format statement

2006-07-21 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2006-07-22 03:18 --- Subject: Bug 28339 Author: jvdelisle Date: Sat Jul 22 03:18:33 2006 New Revision: 115671 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=115671 Log: 2006-07-21 Jerry DeLisle <[EMAI

[Bug fortran/28339] gfortran misses a record from a format statement

2006-07-21 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2006-07-22 06:05 --- Fixed on 4.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/27964] Wrong line ends on windows (XP)

2006-07-23 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-07-23 16:17 --- I don't think it's a curse, but its spooky. :) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27964

[Bug libfortran/25289] Cannot handle record numbers large than huge(0_4)

2006-07-23 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-07-24 00:18 --- Subject: Bug 25289 Author: jvdelisle Date: Mon Jul 24 00:17:52 2006 New Revision: 115698 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=115698 Log: 2006-07-23 Jerry DeLisle <[EMAI

[Bug libfortran/25289] Cannot handle record numbers large than huge(0_4)

2006-07-23 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2006-07-24 00:19 --- Subject: Bug 25289 Author: jvdelisle Date: Mon Jul 24 00:19:45 2006 New Revision: 115700 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=115700 Log: 2006-07-23 Jerry DeLisle <[EMAI

[Bug libfortran/25289] Cannot handle record numbers large than huge(0_4)

2006-07-23 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2006-07-24 00:26 --- Subject: Bug 25289 Author: jvdelisle Date: Mon Jul 24 00:26:08 2006 New Revision: 115702 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=115702 Log: 2006-07-24 Jerry DeLisle <[EMAI

[Bug fortran/28335] flush() / write() statement on closed units - error?

2006-07-25 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2006-07-26 01:47 --- Subject: Bug 28335 Author: jvdelisle Date: Wed Jul 26 01:47:13 2006 New Revision: 115750 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=115750 Log: 2006-07-25 Jerry DeLisle <[EMAI

[Bug fortran/28335] flush() / write() statement on closed units - error?

2006-07-25 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2006-07-26 01:51 --- Patch was committed also, but I messed up pr number in ChangeLog. Fixed that. This PR is fixed in 4.2 only. -- jvdelisle at gcc dot gnu dot org changed: What|Removed

[Bug fortran/28335] [4.1 only] flush() / write() statement on closed units - error?

2006-07-26 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2006-07-27 01:01 --- OK , simple enough. Will do shortly. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28335

[Bug fortran/28335] [4.1 only] flush() / write() statement on closed units - error?

2006-07-26 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2006-07-27 05:13 --- Subject: Bug 28335 Author: jvdelisle Date: Thu Jul 27 05:12:59 2006 New Revision: 115771 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=115771 Log: 2006-07-26 Jerry DeLisle <[EMAI

[Bug fortran/28335] [4.1 only] flush() / write() statement on closed units - error?

2006-07-26 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2006-07-27 05:14 --- Subject: Bug 28335 Author: jvdelisle Date: Thu Jul 27 05:14:19 2006 New Revision: 115772 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=115772 Log: 2006-07-26 Jerry DeLisle <[EMAI

[Bug fortran/28339] gfortran misses a record from a format statement

2006-07-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2006-07-28 14:56 --- Lately, unless someone requests, I have not been committing to 4.1 branch. However, since you asked, I will gladly do so. BTW Thanks for the bug reports. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id

[Bug fortran/28339] gfortran misses a record from a format statement

2006-07-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2006-07-28 16:47 --- Subject: Bug 28339 Author: jvdelisle Date: Fri Jul 28 16:46:57 2006 New Revision: 115798 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=115798 Log: 2006-07-28 Jerry DeLisle <[EMAI

[Bug fortran/28339] gfortran misses a record from a format statement

2006-07-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2006-07-28 16:49 --- Subject: Bug 28339 Author: jvdelisle Date: Fri Jul 28 16:48:58 2006 New Revision: 115799 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=115799 Log: 2006-07-28 Jerry DeLisle <[EMAI

[Bug libfortran/25289] Cannot handle record numbers large than huge(0_4)

2006-07-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2006-07-29 05:12 --- Fixed on 4.2 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/28335] [4.2 Regression] flush() / write() statement on closed units - error?

2006-07-30 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2006-07-31 00:09 --- Subject: Bug 28335 Author: jvdelisle Date: Mon Jul 31 00:09:16 2006 New Revision: 115828 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=115828 Log: 2006-07-30 Jerry DeLisle <[EMAI

[Bug fortran/28335] [4.2 Regression] flush() / write() statement on closed units - error?

2006-07-30 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2006-07-31 00:15 --- Subject: Bug 28335 Author: jvdelisle Date: Mon Jul 31 00:15:08 2006 New Revision: 115829 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=115829 Log: 2006-07-30 Jerry DeLisle <[EMAI

[Bug fortran/28335] [4.2 Regression] flush() / write() statement on closed units - error?

2006-07-30 Thread jvdelisle at gcc dot gnu dot org
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2006-07-31 01:32 --- Subject: Bug 28335 Author: jvdelisle Date: Mon Jul 31 01:32:38 2006 New Revision: 115835 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=115835 Log: 2006-07-30 Jerry DeLisle <[EMAI

[Bug fortran/28335] [4.2 Regression] flush() / write() statement on closed units - error?

2006-07-30 Thread jvdelisle at gcc dot gnu dot org
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2006-07-31 01:36 --- Subject: Bug 28335 Author: jvdelisle Date: Mon Jul 31 01:36:44 2006 New Revision: 115836 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=115836 Log: 2006-07-30 Jerry DeLisle <[EMAI

[Bug fortran/28335] [4.2 Regression] flush() / write() statement on closed units - error?

2006-07-30 Thread jvdelisle at gcc dot gnu dot org
--- Comment #14 from jvdelisle at gcc dot gnu dot org 2006-07-31 01:57 --- Subject: Bug 28335 Author: jvdelisle Date: Mon Jul 31 01:57:25 2006 New Revision: 115837 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=115837 Log: 2006-07-30 Jerry DeLisle <[EMAI

[Bug fortran/28335] [4.2 Regression] flush() / write() statement on closed units - error?

2006-07-30 Thread jvdelisle at gcc dot gnu dot org
--- Comment #15 from jvdelisle at gcc dot gnu dot org 2006-07-31 02:02 --- Fixed on 4.1 and 4.2. Please accept my apologies. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/28603] FAIL: gfortran.dg/direct_io_6.f90 -O0 execution test

2006-08-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2006-08-04 21:17 --- This test is expected to fail on platforms that do not support large file I/O so we just need to mark it as xfail for this platform. Can you do that John? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id

[Bug libfortran/28607] New: [4.1/4.2 Regression]Namelist read does not handle default case of delim="none"

2006-08-04 Thread jvdelisle at gcc dot gnu dot org
Status: UNCONFIRMED Severity: normal Priority: P3 Component: libfortran AssignedTo: jvdelisle at gcc dot gnu dot org ReportedBy: jvdelisle at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28607

[Bug libfortran/28607] [4.1/4.2 Regression]Namelist read does not handle default case of delim="none"

2006-08-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2006-08-05 02:15 --- >From F95 Standard: 9.3.4.9 "DELIM = " in OPEN statement If the value of this specifier is NONE, a character value when written shall not be delimited by apostrophes or quotation marks,nor shall

[Bug libfortran/28607] [4.1/4.2 Regression]Namelist read does not handle default case of delim="none"

2006-08-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2006-08-05 02:17 --- S/specifier/specifier/ Copy garbage from PDF file, sorry. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28607

[Bug fortran/25828] [f2003] ACCESS='STREAM' io support

2006-08-15 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2006-08-15 23:03 --- Subject: Bug 25828 Author: jvdelisle Date: Tue Aug 15 23:03:28 2006 New Revision: 116171 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=116171 Log: 2006-08-15 Jerry DeLisle <[EMAI

[Bug fortran/25828] [f2003] ACCESS='STREAM' io support

2006-08-15 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2006-08-15 23:06 --- Subject: Bug 25828 Author: jvdelisle Date: Tue Aug 15 23:06:44 2006 New Revision: 116172 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=116172 Log: 2006-08-15 Jerry DeLisle <[EMAI

[Bug fortran/25828] [f2003] ACCESS='STREAM' io support

2006-08-15 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2006-08-15 23:14 --- Subject: Bug 25828 Author: jvdelisle Date: Tue Aug 15 23:14:03 2006 New Revision: 116173 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=116173 Log: 2006-08-15 Jerry DeLisle <[EMAI

[Bug libfortran/27964] Wrong line ends on windows (XP)

2006-08-15 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2006-08-16 03:04 --- OK, I have an XP box up and running. Now to get a build going here and I may be able to look into this one. Was this with the cygwin or mingw versio that had the problem, or both? -- http://gcc.gnu.org

[Bug libfortran/28747] New: Empty write STREAM I/O file positioning problem

2006-08-15 Thread jvdelisle at gcc dot gnu dot org
st -- Summary: Empty write STREAM I/O file positioning problem Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libfortran AssignedTo: unassigned at gcc dot gnu dot org

[Bug fortran/25828] [f2003] ACCESS='STREAM' io support

2006-08-15 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2006-08-16 03:14 --- Fixed on 4.2. Will not go to 4.1 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/28747] Empty write STREAM I/O file positioning problem

2006-08-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2006-08-18 16:08 --- Created an attachment (id=12093) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12093&action=view) assembly output for reduced case There is wrong code generated setting up the parameters for the

[Bug libfortran/28747] Empty write STREAM I/O file positioning problem

2006-08-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2006-08-18 16:12 --- Simplified test case used in discussion above. program streamtest implicit none real, dimension(2,3) :: anarray open(10, file="teststream", access="stream", form="unformatted"

[Bug libfortran/28747] Empty write STREAM I/O file positioning problem

2006-08-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2006-08-18 16:29 --- Using -fdump-tree-final_cleanup all looks OK. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28747

[Bug libfortran/28747] Empty write STREAM I/O file positioning problem

2006-08-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-08-18 20:54 --- Here is a debug trace showing the steps leading up to the mutation of the dtp pointer. StevebB on IRC indicated that the assembly output on linux x86-64 natch the freebsd version I posted here and the problem

[Bug libfortran/28747] Empty write STREAM I/O file positioning problem

2006-08-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2006-08-19 03:29 --- Here is a comparison of no optimization and with -O1. Does this code look the same on x86-64 that is not FreeBSD? Code with no optimization: This does not work. call_gfortran_st_write_done

[Bug libfortran/28747] Empty write STREAM I/O file positioning problem

2006-08-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2006-08-19 16:52 --- I think this confirms the problem is in __gthrw_(pthread_mutex_unlock) (mutex) on FreeBSD. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28747

[Bug libfortran/28747] Empty write STREAM I/O file positioning problem

2006-08-19 Thread jvdelisle at gcc dot gnu dot org
-- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last

[Bug libfortran/28354] 0.99999 printed as 0. instead of 1. by format(f3.0)

2006-08-21 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2006-08-22 00:25 --- I will take this on, -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/28813] gfortran.dg/direct_io_6.f90 can exhaust system disk space

2006-08-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2006-08-23 04:19 --- I can temporarily delete this test until I can come up with a better approach. On my linux system the actual disk space used is less then 100 bytes even though it logically consumes a huge amount. It depends on

<    1   2   3   4   5   6   7   8   9   10   >