[Bug libfortran/40330] [4.4, 4.5 Regression] incorrect IO

2009-06-10 Thread jvdelisle at gcc dot gnu dot org
--- Comment #22 from jvdelisle at gcc dot gnu dot org 2009-06-10 12:32 --- Thanks for reduced test. $ ./a.out >badfile $ xxd badfile 000: 2020 2020 2020 2020 2020 2020 2020 33203 010: 2020 2020 2020 2020 2020 2020 2020 33003. The NULL in

[Bug libfortran/40330] [4.4, 4.5 Regression] incorrect IO

2009-06-10 Thread jvdelisle at gcc dot gnu dot org
--- Comment #25 from jvdelisle at gcc dot gnu dot org 2009-06-11 01:29 --- Changing priority to normal. I have a patch that fixes the reduced test case. Testing CP2K now. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/40330] [4.4, 4.5 Regression] incorrect IO

2009-06-10 Thread jvdelisle at gcc dot gnu dot org
--- Comment #26 from jvdelisle at gcc dot gnu dot org 2009-06-11 02:25 --- CP2K still fails. However, I think I have discovered the root cause. String constants in formats are saved in the fnode at sting.p which is a pointer. When we use cached parsed string data, those constant

[Bug libfortran/40330] [4.4, 4.5 Regression] incorrect IO

2009-06-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #28 from jvdelisle at gcc dot gnu dot org 2009-06-11 12:49 --- Subject: Bug 40330 Author: jvdelisle Date: Thu Jun 11 12:49:35 2009 New Revision: 148391 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=148391 Log: 2009-06-11 Jerry DeLisle PR li

[Bug libfortran/40330] [4.5 Regression] incorrect IO

2009-06-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #29 from jvdelisle at gcc dot gnu dot org 2009-06-11 14:58 --- Fixed on 4.4.1, 4.5 in review process. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/40149] variable length still 6 ???

2009-06-12 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2009-06-12 18:08 --- Closing -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status

[Bug libfortran/32784] [win32] Using 'CONOUT$', 'CONIN$', or 'CONERR$' as assigned file generates Fortran runtime error: Bad file descriptor

2009-06-13 Thread jvdelisle at gcc dot gnu dot org
--- Comment #33 from jvdelisle at gcc dot gnu dot org 2009-06-14 00:59 --- Patch tested on Cygwin and submitted for approval. Need a tester for mingw. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32784

[Bug fortran/40508] memory leak in internal write of gfortran

2009-06-21 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2009-06-21 12:58 --- I see no memory issues or memory growth on x85-64-linux-gnu with -m64 or -m32. This appears to be target specific. Checked with 4.4.1 and latest trunk. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40508

[Bug fortran/40508] memory leak in internal write of gfortran

2009-06-21 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2009-06-21 17:34 --- I don't doubt there is a problem. Not found with valgrind either on x86-64 linux. It's hard to debug when you can't see the problem. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40508

[Bug fortran/40508] memory leak in internal write of gfortran

2009-06-21 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2009-06-21 18:50 --- Confirmed. Problem narrowed down to format hashing not getting freed by Richi on IRC. I had the problem bypassed on my trunk by another patch. -- jvdelisle at gcc dot gnu dot org changed: What

[Bug fortran/40508] memory leak in internal write of gfortran

2009-06-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2009-06-23 00:16 --- Subject: Bug 40508 Author: jvdelisle Date: Tue Jun 23 00:16:24 2009 New Revision: 148823 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=148823 Log: 2009-06-22 Jerry DeLisle PR li

[Bug libfortran/40330] [4.5 Regression] incorrect IO

2009-06-26 Thread jvdelisle at gcc dot gnu dot org
--- Comment #31 from jvdelisle at gcc dot gnu dot org 2009-06-26 15:50 --- I am working on some ideas here. We are getting double free or corruption related to free_format_data. I think it is because we have two pointers to pay attention to. The one in the hash table and dtp

[Bug fortran/40576] [4.5 Regression] Endless loop in internal write

2009-06-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2009-06-29 02:07 --- I will have a look. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/40576] [4.5 Regression] Endless loop in internal write

2009-06-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2009-06-29 04:09 --- I can confirm the regression is from the I/O patch, but not related to format caching. The test case is looping here: (gdb) bt #0 mem_alloc_w () at ../../../gcc45/libgfortran/io/unix.c:579 #1 mem_write (s

[Bug fortran/40576] [4.4, 4.5 Regression] Endless loop in internal write

2009-06-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2009-06-29 04:35 --- I think this fixes it. Still testing. Will need to get this into 4.4 if this is it. This fix is consistent with fd_set in 4.3 which loops as long as trans > 0. (similar code) Index: transfe

[Bug fortran/40576] [4.4/4.5 Regression] Endless loop in internal write

2009-06-29 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2009-06-30 00:46 --- Subject: Bug 40576 Author: jvdelisle Date: Tue Jun 30 00:46:35 2009 New Revision: 149075 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149075 Log: 2009-06-29 Jerry DeLisle PR li

[Bug fortran/40576] [4.4/4.5 Regression] Endless loop in internal write

2009-06-29 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2009-06-30 00:52 --- Subject: Bug 40576 Author: jvdelisle Date: Tue Jun 30 00:52:06 2009 New Revision: 149077 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149077 Log: 2009-06-29 Jerry DeLisle PR li

[Bug fortran/40576] [4.4/4.5 Regression] Endless loop in internal write

2009-06-29 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2009-06-30 00:55 --- Fixed on 4.4 and 4.5, closing. Thanks to Thomas for report and reduced test case. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40576

[Bug fortran/40576] [4.4/4.5 Regression] Endless loop in internal write

2009-06-29 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2009-06-30 01:47 --- Closed. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status

[Bug fortran/40008] F2008: Add NEWUNIT= for OPEN statement

2009-07-02 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2009-07-02 18:15 --- Complete. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status

[Bug fortran/40638] RTE: "Unit number in I/O statement too large" -- fails with any low value

2009-07-03 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2009-07-03 15:20 --- I will add that I suspect that the bug may be latent in 4.5 since I did change the error code when I added NEWUNIT to 4.5. After we get to the bottom of it, we need to consider backporting a fix to 4.4 since

[Bug fortran/40638] RTE: "Unit number in I/O statement too large" -- fails with any low value

2009-07-03 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2009-07-03 15:16 --- I can reproduce the problem on 4.3 and 4.4. I would like to investigate further, especially regarding 4.4 and what did we change between 4.4 and 4.5 to fix this. -- jvdelisle at gcc dot gnu dot org changed

[Bug fortran/40638] RTE: "Unit number in I/O statement too large" -- fails with any low value

2009-07-03 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2009-07-03 23:24 --- Yes, I have the patch already. Its a one liner. Index: trans-io.c === --- trans-io.c (revision 149123) +++ trans-io.c (working copy) @@ -471,7

[Bug fortran/40638] RTE: "Unit number in I/O statement too large" -- fails with any low value

2009-07-03 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2009-07-04 03:07 --- Subject: Bug 40638 Author: jvdelisle Date: Sat Jul 4 03:07:12 2009 New Revision: 149218 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149218 Log: 2009-07-03 Jerry DeLisle PR fortr

[Bug fortran/40638] RTE: "Unit number in I/O statement too large" -- fails with any low value

2009-07-03 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2009-07-04 04:05 --- Subject: Bug 40638 Author: jvdelisle Date: Sat Jul 4 04:05:19 2009 New Revision: 149219 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149219 Log: 2009-07-03 Jerry DeLisle PR fortr

[Bug fortran/40638] RTE: "Unit number in I/O statement too large" -- fails with any low value

2009-07-03 Thread jvdelisle at gcc dot gnu dot org
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2009-07-04 04:17 --- Subject: Bug 40638 Author: jvdelisle Date: Sat Jul 4 04:16:59 2009 New Revision: 149220 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149220 Log: 2009-07-03 Jerry DeLisle PR fortr

[Bug fortran/40638] RTE: "Unit number in I/O statement too large" -- fails with any low value

2009-07-03 Thread jvdelisle at gcc dot gnu dot org
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2009-07-04 04:20 --- Subject: Bug 40638 Author: jvdelisle Date: Sat Jul 4 04:20:24 2009 New Revision: 149221 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149221 Log: 2009-07-03 Jerry DeLisle PR fortr

[Bug fortran/40638] RTE: "Unit number in I/O statement too large" -- fails with any low value

2009-07-03 Thread jvdelisle at gcc dot gnu dot org
--- Comment #14 from jvdelisle at gcc dot gnu dot org 2009-07-04 04:25 --- Subject: Bug 40638 Author: jvdelisle Date: Sat Jul 4 04:25:20 2009 New Revision: 149222 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149222 Log: 2009-07-03 Jerry DeLisle PR fortr

[Bug fortran/40638] RTE: "Unit number in I/O statement too large" -- fails with any low value

2009-07-03 Thread jvdelisle at gcc dot gnu dot org
--- Comment #15 from jvdelisle at gcc dot gnu dot org 2009-07-04 04:28 --- Fixed on 4.3 and 4.4. Added new test case to 4.5 as well as 4.3 and 4.4 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/40638] RTE: "Unit number in I/O statement too large" -- fails with any low value

2009-07-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #17 from jvdelisle at gcc dot gnu dot org 2009-07-04 19:47 --- *** Bug 40652 has been marked as a duplicate of this bug. *** -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/40652] fortran io unit number specified in a short integer causes open to fail.

2009-07-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2009-07-04 19:47 --- see PR40638 which was recently reported and fixed yesterday. There is a patch in the PR *** This bug has been marked as a duplicate of 40638 *** -- jvdelisle at gcc dot gnu dot org changed: What

[Bug bootstrap/40455] gcc trunk does not bootstrap as of commit r148408

2009-07-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #14 from jvdelisle at gcc dot gnu dot org 2009-07-04 21:29 --- I am on cygwin-1.5. will these fixes get pushed to setup? or am I stuck? or is there a work around? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40455

[Bug bootstrap/40455] gcc trunk does not bootstrap as of commit r148408

2009-07-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #16 from jvdelisle at gcc dot gnu dot org 2009-07-04 23:52 --- I was resisting the change to 1.7 because the website states "Beta". I will go ahead and do so now. :) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40455

[Bug libfortran/40330] [4.5 Regression] incorrect IO

2009-07-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #32 from jvdelisle at gcc dot gnu dot org 2009-07-05 02:12 --- I am getting close now. I have a patch that actually passes the CP2K test case and regression testing. It turns out that the parse_format_list function is called recursively so one must be careful about

[Bug libfortran/40330] [4.5 Regression] incorrect IO

2009-07-05 Thread jvdelisle at gcc dot gnu dot org
--- Comment #33 from jvdelisle at gcc dot gnu dot org 2009-07-05 12:25 --- Created an attachment (id=18138) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18138&action=view) Patch ready for testing Joost, if you can, please test this patch on all of CP2K. Other testors

[Bug fortran/40662] gfortran 4.5 segfaults when specific FORMAT is invoked twice

2009-07-06 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2009-07-06 18:12 --- Yes indeed it is fixed with my patch of this morning. This is the reduced test case we can use for the test suite. Thanks for the report Michael! -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40662

[Bug target/34764] A Flame About 64-bit Pointers

2009-07-06 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2009-07-06 19:45 --- 2 cents. Memory is cheap, very cheap. When you can buy a x86-64 based laptop with 3 gig for under 500 dollars, it does not matter that much. Now, if you are doing embedded systems, that may be a different tune

[Bug libfortran/40330] [4.5 Regression] incorrect IO

2009-07-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #34 from jvdelisle at gcc dot gnu dot org 2009-07-09 01:20 --- Subject: Bug 40330 Author: jvdelisle Date: Thu Jul 9 01:20:23 2009 New Revision: 149398 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149398 Log: 2009-07-08 Jerry DeLisle PR li

[Bug fortran/40662] gfortran 4.5 segfaults when specific FORMAT is invoked twice

2009-07-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2009-07-09 01:20 --- Subject: Bug 40662 Author: jvdelisle Date: Thu Jul 9 01:20:23 2009 New Revision: 149398 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149398 Log: 2009-07-08 Jerry DeLisle PR li

[Bug libfortran/40330] [4.5 Regression] incorrect IO

2009-07-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #35 from jvdelisle at gcc dot gnu dot org 2009-07-09 01:55 --- Subject: Bug 40330 Author: jvdelisle Date: Thu Jul 9 01:54:47 2009 New Revision: 149399 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149399 Log: 2009-07-08 Jerry DeLisle PR li

[Bug fortran/40662] gfortran 4.5 segfaults when specific FORMAT is invoked twice

2009-07-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2009-07-09 01:55 --- Subject: Bug 40662 Author: jvdelisle Date: Thu Jul 9 01:54:47 2009 New Revision: 149399 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149399 Log: 2009-07-08 Jerry DeLisle PR li

[Bug libfortran/40330] [4.5 Regression] incorrect IO

2009-07-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #36 from jvdelisle at gcc dot gnu dot org 2009-07-09 01:59 --- Fixed on trunk. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/40662] gfortran 4.5 segfaults when specific FORMAT is invoked twice

2009-07-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2009-07-09 02:01 --- Fixed on trunk. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/40508] memory leak in internal write of gfortran

2009-07-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2009-07-09 02:02 --- Fixed. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status

[Bug fortran/40714] Fortran runtime error: Invalid argument

2009-07-10 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2009-07-11 02:13 --- I will take this one on. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/40714] [4.4, 4.5 Regression] Fortran runtime error: Invalid argument

2009-07-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2009-07-11 15:15 --- Marked as regression. Not platform specific. I confirmed this on x86-64 Linux. We have an illegal seek in transfer.c (next_record_w_unf) at line 2824. -- jvdelisle at gcc dot gnu dot org changed

[Bug fortran/40714] [4.4, 4.5 Regression] Fortran runtime error: Invalid argument

2009-07-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2009-07-11 17:16 --- Another aspect of this bug. If we do this: PROGRAM test OPEN(UNIT=32,FILE="fort.32",STATUS="NEW",ACCESS="SEQUENTIAL",FORM="UNFORMATTED") !READ(32,END=100) 100 CONT

[Bug fortran/40734] ICE on attempt to compile trivial Fortran program

2009-07-13 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2009-07-13 18:12 --- Try compiling without these: -lgfortranbegin -lgfortran Should not need to do this. Lets see what it does. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40734

[Bug fortran/40714] [4.4, 4.5 Regression] Fortran runtime error: Invalid argument

2009-07-15 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2009-07-16 01:31 --- I was trying to do it in hit_eof after the return from the error. I have not figured it out yet. I will keep trying, but hope you find it first. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40714

[Bug fortran/40714] [4.4, 4.5 Regression] Fortran runtime error: Invalid argument

2009-07-15 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2009-07-16 03:23 --- Taking myself off of this one. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/32784] [win32] Using 'CONOUT$', 'CONIN$', or 'CONERR$' as assigned file generates Fortran runtime error: Bad file descriptor

2009-07-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #34 from jvdelisle at gcc dot gnu dot org 2009-07-19 13:43 --- Cygwin only patch submitted. MingW next. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32784

[Bug fortran/40714] [4.4/4.5 Regression] Fortran runtime error: Invalid argument

2009-07-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2009-07-19 23:10 --- Subject: Bug 40714 Author: jvdelisle Date: Sun Jul 19 23:10:22 2009 New Revision: 149795 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149795 Log: 2009-07-19 Janne Blomqvist

[Bug fortran/40714] [4.4/4.5 Regression] Fortran runtime error: Invalid argument

2009-07-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2009-07-19 23:22 --- Subject: Bug 40714 Author: jvdelisle Date: Sun Jul 19 23:22:37 2009 New Revision: 149796 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149796 Log: 2009-07-19 Janne Blomqvist

[Bug fortran/40714] [4.4/4.5 Regression] Fortran runtime error: Invalid argument

2009-07-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2009-07-19 23:26 --- Subject: Bug 40714 Author: jvdelisle Date: Sun Jul 19 23:26:20 2009 New Revision: 149797 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149797 Log: 2009-07-19 Janne Blomqvist

[Bug fortran/40714] [4.4/4.5 Regression] Fortran runtime error: Invalid argument

2009-07-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2009-07-19 23:44 --- Fixed on 4.5.0 and 4.4.1. Thanks for bug report. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/40812] Incorrectly writes/reads formatted ASCII files greater than 2Gb

2009-07-20 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2009-07-21 05:04 --- Works OK on i86-64-linux. I also ran the original test programs on Cygwin and results are also OK all the way through. I wonder if we can get another mingw attempt Note: 4 Gb file here. -- http

[Bug fortran/39654] ABI bug: FTELL intrinsic function not capable of large files

2009-07-21 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2009-07-22 00:02 --- Is there a particular reason why we can not change this to off_t with 4.5.? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39654

[Bug libfortran/32784] [win32] Using 'CONOUT$', 'CONIN$', or 'CONERR$' as assigned file generates Fortran runtime error: Bad file descriptor

2009-07-22 Thread jvdelisle at gcc dot gnu dot org
--- Comment #35 from jvdelisle at gcc dot gnu dot org 2009-07-23 00:59 --- Subject: Bug 32784 Author: jvdelisle Date: Thu Jul 23 00:58:46 2009 New Revision: 149970 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149970 Log: 2009-07-22 Jerry DeLisle PR li

[Bug fortran/39229] No warning of truncated lines if a continuation line follows

2009-07-25 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2009-07-25 16:46 --- There are two things going on here. First, because of the continuation, the scanner actually combines the two lines into one line. Secondly, we have code that deliberately clears the truncation flag because it

[Bug fortran/40853] I/O: Namelist read error

2009-07-27 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2009-07-28 02:00 --- I will get started on this. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/40853] I/O: Namelist read error

2009-07-27 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2009-07-28 03:09 --- As a work-around, re-arranging the derived type like this: type tao_plot_page_struct real size(2) real shape_height_max type (tao_title_struct) title end type May help, until I get this sorted

[Bug fortran/40853] I/O: Namelist read error

2009-07-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2009-07-29 04:40 --- Created an attachment (id=18265) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18265&action=view) A simple patch to resolve the problem This patch solves the original test case. It does

[Bug fortran/40853] I/O: Namelist read error

2009-08-01 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2009-08-01 15:42 --- Patch submitted for approval: http://gcc.gnu.org/ml/fortran/2009-08/msg1.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40853

[Bug fortran/40853] I/O: Namelist read error

2009-08-02 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2009-08-02 18:31 --- Subject: Bug 40853 Author: jvdelisle Date: Sun Aug 2 18:31:07 2009 New Revision: 150356 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=150356 Log: 2009-08-02 Jerry DeLisle PR li

[Bug fortran/40853] I/O: Namelist read error

2009-08-02 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2009-08-02 18:48 --- Subject: Bug 40853 Author: jvdelisle Date: Sun Aug 2 18:47:46 2009 New Revision: 150357 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=150357 Log: 2009-08-02 Jerry DeLisle PR li

[Bug fortran/40853] I/O: Namelist read error

2009-08-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2009-08-05 03:15 --- Subject: Bug 40853 Author: jvdelisle Date: Wed Aug 5 03:15:18 2009 New Revision: 150476 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=150476 Log: 2009-08-04 Jerry DeLisle PR li

[Bug fortran/40853] I/O: Namelist read error

2009-08-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2009-08-05 03:18 --- Subject: Bug 40853 Author: jvdelisle Date: Wed Aug 5 03:17:52 2009 New Revision: 150477 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=150477 Log: 2009-08-04 Jerry DeLisle PR li

[Bug fortran/40853] I/O: Namelist read error

2009-08-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2009-08-05 03:19 --- Fixed on 4.4 and 4.5, closing -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/40993] Empty error message with long lines

2009-08-07 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2009-08-07 16:06 --- The problem is that the error locus is at the end of the line rather then the end of the non-whitespace characters of the related statement. -- jvdelisle at gcc dot gnu dot org changed: What

[Bug libfortran/24699] New: READ with T format specifier fails on end-of-record condition

2005-11-06 Thread jvdelisle at gcc dot gnu dot org
ecifier fails on end-of-record condition Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libfortran AssignedTo: jvdelisle at gcc dot gnu dot org ReportedBy: jvdeli

[Bug libfortran/24700] New: Bad write after backing up from end of file

2005-11-06 Thread jvdelisle at gcc dot gnu dot org
urrent_record = 0; break; } } Test results to follow: -- Summary: Bad write after backing up from end of file Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libfortran Assigned

[Bug libfortran/24700] Bad write after backing up from end of file

2005-11-06 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2005-11-06 23:58 --- Testing that patch gives the following results. I will put together a test case and commit this as obvious unless there are objections. hex dump of TEST file created using gfortran 4.0.1 gives, with no patch

[Bug libfortran/24719] [4.1 Regression] Nonadvancing read does not read more than 1 line

2005-11-07 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2005-11-08 01:46 --- This is precisly when I committed the patch to pr24489. I am also seeing some possible connections with pr24699. I will investigate further. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24719

[Bug libfortran/24719] [4.1 Regression] Nonadvancing read does not read more than 1 line

2005-11-07 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2005-11-08 02:18 --- I have confirmed that when I revert the patch to pr24489 that this bug goes away. Isn't life wonderful! -- jvdelisle at gcc dot gnu dot org changed: What|Removed |

[Bug libfortran/24719] [4.1 Regression] Nonadvancing read does not read more than 1 line

2005-11-07 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2005-11-08 06:22 --- I believe I have a fix for this one that works with the previous patch to pr24489. I am testing along with work on pr24699 to make sure we have no conflicts or regressions. pr24719, pr24699, pr24700, and

[Bug libfortran/24785] X edit descriptor lost with ADVANCE="NO"

2005-11-10 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2005-11-11 02:07 --- Another trasnfer.c bug possibly. I will investigate. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24785

[Bug libfortran/24785] X edit descriptor lost with ADVANCE="NO"

2005-11-10 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2005-11-11 02:16 --- Confirmed on 4.1 and 4.0.3 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/24785] X edit descriptor lost with ADVANCE="NO"

2005-11-10 Thread jvdelisle at gcc dot gnu dot org
-- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |jvdelisle at gcc dot gnu dot |dot org

[Bug libfortran/24794] problem with namelist input of character array

2005-11-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2005-11-11 16:32 --- Confirmed in 4.1 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/24796] end-of-record error when writing

2005-11-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2005-11-11 16:38 --- This works fine in 4.1 with my upcoming patches. Hex dump of file looks good. May be a duplicate of pr24700. Could someone else try this with an unpatched tree so I don't have to mess with my very delic

[Bug libfortran/24796] end-of-record error when writing

2005-11-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2005-11-11 18:52 --- Well that confirms the bug and the fix is ready to be committed shortly. Thanks Steve *** This bug has been marked as a duplicate of 24700 *** -- jvdelisle at gcc dot gnu dot org changed: What

[Bug libfortran/24700] Bad write after backing up from end of file

2005-11-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2005-11-11 18:52 --- *** Bug 24796 has been marked as a duplicate of this bug. *** -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/24699] READ with T format specifier fails on end-of-record condition

2005-11-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2005-11-11 20:19 --- Subject: Bug 24699 Author: jvdelisle Date: Fri Nov 11 20:19:21 2005 New Revision: 106797 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106797 Log: 2005-11-09 Jerry DeLisle <[EMAI

[Bug libfortran/24489] read_block wrong execution order

2005-11-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2005-11-11 20:31 --- Subject: Bug 24489 Author: jvdelisle Date: Fri Nov 11 20:31:06 2005 New Revision: 106798 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106798 Log: 2005-11-11 Jerry DeLisle <[EMAI

[Bug libfortran/24699] READ with T format specifier fails on end-of-record condition

2005-11-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2005-11-11 20:31 --- Subject: Bug 24699 Author: jvdelisle Date: Fri Nov 11 20:31:06 2005 New Revision: 106798 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106798 Log: 2005-11-11 Jerry DeLisle <[EMAI

[Bug libfortran/24719] [4.1 Regression] Nonadvancing read does not read more than 1 line

2005-11-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2005-11-11 20:31 --- Subject: Bug 24719 Author: jvdelisle Date: Fri Nov 11 20:31:06 2005 New Revision: 106798 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106798 Log: 2005-11-11 Jerry DeLisle <[EMAI

[Bug libfortran/24584] Segfault when reading empty string in namelist file

2005-11-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2005-11-11 20:31 --- Subject: Bug 24584 Author: jvdelisle Date: Fri Nov 11 20:31:06 2005 New Revision: 106798 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106798 Log: 2005-11-11 Jerry DeLisle <[EMAI

[Bug libfortran/24785] X edit descriptor lost with ADVANCE="NO"

2005-11-11 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2005-11-11 20:31 --- Subject: Bug 24785 Author: jvdelisle Date: Fri Nov 11 20:31:06 2005 New Revision: 106798 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106798 Log: 2005-11-11 Jerry DeLisle <[EMAI

[Bug libfortran/24584] Segfault when reading empty string in namelist file

2005-11-12 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2005-11-12 22:22 --- Subject: Bug 24584 Author: jvdelisle Date: Sat Nov 12 22:22:53 2005 New Revision: 106838 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106838 Log: 2005-11-12 Jerry DeLisle <[EMAI

[Bug libfortran/24699] READ with T format specifier fails on end-of-record condition

2005-11-12 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2005-11-12 22:22 --- Subject: Bug 24699 Author: jvdelisle Date: Sat Nov 12 22:22:53 2005 New Revision: 106838 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106838 Log: 2005-11-12 Jerry DeLisle <[EMAI

[Bug libfortran/24719] [4.1 Regression] Nonadvancing read does not read more than 1 line

2005-11-12 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2005-11-12 22:31 --- Subject: Bug 24719 Author: jvdelisle Date: Sat Nov 12 22:31:18 2005 New Revision: 106839 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106839 Log: 2005-11-12 Jerry DeLisle <[EMAI

[Bug libfortran/24785] X edit descriptor lost with ADVANCE="NO"

2005-11-12 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2005-11-12 22:31 --- Subject: Bug 24785 Author: jvdelisle Date: Sat Nov 12 22:31:18 2005 New Revision: 106839 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106839 Log: 2005-11-12 Jerry DeLisle <[EMAI

[Bug libfortran/24699] READ with T format specifier fails on end-of-record condition

2005-11-12 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2005-11-12 22:31 --- Subject: Bug 24699 Author: jvdelisle Date: Sat Nov 12 22:31:18 2005 New Revision: 106839 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106839 Log: 2005-11-12 Jerry DeLisle <[EMAI

[Bug libfortran/24584] Segfault when reading empty string in namelist file

2005-11-12 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2005-11-12 22:31 --- Subject: Bug 24584 Author: jvdelisle Date: Sat Nov 12 22:31:18 2005 New Revision: 106839 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106839 Log: 2005-11-12 Jerry DeLisle <[EMAI

[Bug libfortran/24699] READ with T format specifier fails on end-of-record condition

2005-11-12 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2005-11-12 23:13 --- Fixed in 4.0.3 and 4.1 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/24700] Bad write after backing up from end of file

2005-11-12 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2005-11-12 23:13 --- Fixed in 4.0.3 and 4.1. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/24719] [4.1 Regression] Nonadvancing read does not read more than 1 line

2005-11-12 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2005-11-12 23:20 --- Fixed in 4.0.3 and 4.1 -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/24785] X edit descriptor lost with ADVANCE="NO"

2005-11-12 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2005-11-12 23:21 --- Fixed in 4.0.3 and 4.1 . -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/24584] Segfault when reading empty string in namelist file

2005-11-12 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2005-11-12 23:22 --- Fixed in 4.0.3 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24584

[Bug libfortran/24919] GFORTRAN input and carriage returns

2005-11-17 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2005-11-18 00:47 --- This is near stuff I am working on so I will work it. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

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