[Bug fortran/40839] gfortran segmentation fault when a unit number is missing

2009-10-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2009-10-04 20:56 --- Can this PR be closed? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40839

[Bug fortran/35009] error on valid with -std=f95 (character arrays in format tags)

2009-10-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #14 from jvdelisle at gcc dot gnu dot org 2009-10-04 21:18 --- Yikes, this slipped in the crack. I am doing triage today and noticed this. Assigning to myself. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/35952] Segmentation fault with character strings only when compiling with -funroll-loops and -O3

2009-10-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2009-10-04 21:25 --- Assigning to myself only to remind me to investigate to see where this stands now. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/40020] Bad value during floating point read

2009-10-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2009-10-04 21:51 --- Any new information on this issue? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40020

[Bug fortran/35009] error on valid with -std=f95 (character arrays in format tags)

2009-10-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #15 from jvdelisle at gcc dot gnu dot org 2009-10-05 02:49 --- OK, This got fixed somewhere along the way and the test case provided works fine. Closing. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug lto/40725] [LTO] ICE in size_binop, at fold-const.c:2072

2009-10-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2009-10-05 02:54 --- Reopening: FAIL: gfortran.dg/lto/pr40725 f_lto_pr40725_0.o-f_lto_pr40725_1.o execute -O2 -fwhopr I think LTO folks already know about this. -- jvdelisle at gcc dot gnu dot org changed: What

[Bug libfortran/35862] [F2003] Implement new rounding modes for run time

2009-10-03 Thread jvdelisle at gcc dot gnu dot org
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2009-10-03 15:10 --- There are two unrelated bugs in output rounding. The following patch fixes both. The smaller hunks were obvious. The larger gets rid of a hack I did to handle the special case with d=0. The rounding logic

[Bug libfortran/35862] [F2003] Implement new rounding modes for run time

2009-10-03 Thread jvdelisle at gcc dot gnu dot org
--- Comment #14 from jvdelisle at gcc dot gnu dot org 2009-10-03 16:17 --- Correction to comment #13, Shifting bytes right not left. Also, I have completed testing using memmove instead of the explicit for loop. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35862

[Bug libfortran/35862] [F2003] Implement new rounding modes for run time

2009-10-01 Thread jvdelisle at gcc dot gnu dot org
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2009-10-02 02:32 --- Reply to comment #10: Thanks for the input and references. The perspective of rounding before conversion to binary representation is interesting. I will think on that a bit. Reply to comment #11: Thanks

[Bug libfortran/35862] [F2003] Implement new rounding modes for run time

2009-09-30 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2009-10-01 01:37 --- Rounding modes are now implemented for formatted WRITE operations. I do not have a clear enough idea of what the rounding modes really mean for READ operations. For example: From Comment #4 Rounding is done

[Bug libfortran/35862] [F2003] Implement new rounding modes for run time

2009-09-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2009-09-29 02:44 --- Subject: Bug 35862 Author: jvdelisle Date: Tue Sep 29 02:44:38 2009 New Revision: 152262 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=152262 Log: 2009-09-28 Jerry DeLisle jvdeli...@gcc.gnu.org

[Bug libfortran/35862] [F2003] Implement new rounding modes for run time

2009-09-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2009-09-29 02:48 --- Subject: Bug 35862 Author: jvdelisle Date: Tue Sep 29 02:47:54 2009 New Revision: 152263 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=152263 Log: 2009-09-28 Jerry DeLisle jvdeli...@gcc.gnu.org

[Bug libfortran/35862] [F2003] Implement new rounding modes for run time

2009-09-28 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2009-09-29 02:51 --- Subject: Bug 35862 Author: jvdelisle Date: Tue Sep 29 02:50:48 2009 New Revision: 152264 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=152264 Log: 2009-09-28 Jerry DeLisle jvdeli...@gcc.gnu.org

[Bug fortran/41478] function pack causes double free violation

2009-09-26 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2009-09-27 00:39 --- I can reproduce this on 4.3.3 and 4.5.0 r151904. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/41479] wrong code, mis-initialization

2009-09-26 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2009-09-27 00:50 --- gfortran is not considered release critical and so is never given a blocker status. Changing to normal. Regarding the intent(out) issue. I will defer to others. -- jvdelisle at gcc dot gnu dot org

[Bug fortran/41479] wrong code, mis-initialization

2009-09-26 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2009-09-27 01:13 --- The problem goes away if the allocatable specification is removed from the declaration of 'a' Problem also occurs on gfortran 4.3.0 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41479

[Bug fortran/41403] Optimization: NIST test FM013.f fails at -O1 and above

2009-09-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2009-09-19 06:15 --- Reduced case: Expected result: $ ./a.out 0 ERRORS ENCOUNTERED Wrong result: $ ./a.out 1 ERRORS ENCOUNTERED PROGRAM FM013 I01 = 5

[Bug fortran/41408] Segmentation fault calling DGETRF from gfortran

2009-09-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2009-09-19 15:01 --- Lets keep this bug open while you are hunting so we don't forget. Waiting -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/41328] [4.4 regression] bad iostat when reading DOS file in a character array (non-advancing)

2009-09-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2009-09-19 17:21 --- Subject: Bug 41328 Author: jvdelisle Date: Sat Sep 19 17:21:20 2009 New Revision: 151883 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=151883 Log: 2009-09-19 Jerry DeLisle jvdeli...@gcc.gnu.org

[Bug fortran/41328] [4.4 regression] bad iostat when reading DOS file in a character array (non-advancing)

2009-09-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2009-09-19 17:24 --- Subject: Bug 41328 Author: jvdelisle Date: Sat Sep 19 17:23:43 2009 New Revision: 151884 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=151884 Log: 2009-09-19 Jerry DeLisle jvdeli...@gcc.gnu.org

[Bug fortran/41328] [4.4 regression] bad iostat when reading DOS file in a character array (non-advancing)

2009-09-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #14 from jvdelisle at gcc dot gnu dot org 2009-09-19 17:35 --- Fixed on 4.4, closing -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/41328] [4.4, 4.5 regression] bad iostat when reading DOS file in a character array (non-advancing)

2009-09-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2009-09-18 19:20 --- Here is a new test case, closely related, reported on fortran list: http://gcc.gnu.org/ml/fortran/2009-09/msg00126.html The read of the last line in a file without the end-of-line marker should be treated

[Bug fortran/41328] [4.4, 4.5 regression] bad iostat when reading DOS file in a character array (non-advancing)

2009-09-18 Thread jvdelisle at gcc dot gnu dot org
-- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|4.4.2 |4.5.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41328

[Bug fortran/41328] [4.4, 4.5 regression] bad iostat when reading DOS file in a character array (non-advancing)

2009-09-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2009-09-19 04:42 --- Subject: Bug 41328 Author: jvdelisle Date: Sat Sep 19 04:41:38 2009 New Revision: 151877 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=151877 Log: 2009-09-18 Jerry DeLisle jvdeli...@gcc.gnu.org

[Bug fortran/41328] [4.4, 4.5 regression] bad iostat when reading DOS file in a character array (non-advancing)

2009-09-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2009-09-19 04:45 --- Subject: Bug 41328 Author: jvdelisle Date: Sat Sep 19 04:45:00 2009 New Revision: 151878 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=151878 Log: 2009-09-18 Jerry DeLisle jvdeli...@gcc.gnu.org

[Bug fortran/41328] [4.4 regression] bad iostat when reading DOS file in a character array (non-advancing)

2009-09-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2009-09-19 04:50 --- Refixed on trunk. Patch committed as obvious. Will backport to 4.4 in a day. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/41403] New: Optimization: NIST test FM013.f fails at -O1 and above

2009-09-18 Thread jvdelisle at gcc dot gnu dot org
: UNCONFIRMED Keywords: wrong-code 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: x86_64-unknown-linux-gnu http://gcc.gnu.org/bugzilla

[Bug fortran/41403] Optimization: NIST test FM013.f fails at -O1 and above

2009-09-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2009-09-19 05:44 --- Created an attachment (id=18605) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18605action=view) NIST test case that is failing I will try to reduce this. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id

[Bug fortran/41403] Optimization: NIST test FM013.f fails at -O1 and above

2009-09-18 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2009-09-19 05:47 --- Its ugly code so remember to compile with -w and save the attachment as a .f file so that fixed form is used. This will turn off all of the warnings. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41403

[Bug libfortran/41387] OPEN, STATUS='NEW' of a symbolic link to a non-existing file fails.

2009-09-17 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2009-09-17 19:15 --- I agree, this is enhancement only. Code that relies on or expects consistent behavior when the users has created and symlink is likely not protable. See http://gcc.gnu.org/ml/fortran/2009-09/msg00107.html

[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/41192] NAMELIST input with just a comment (NAME ! comment \) fails

2009-09-13 Thread jvdelisle at gcc dot gnu dot org
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2009-09-13 14:31 --- Fixed. I see no point in warning on a comment. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/41219] libgfortran build warnings

2009-09-12 Thread jvdelisle at gcc dot gnu dot org
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2009-09-12 14:48 --- I will do the write.c one. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/41328] [4.4/4.5 regression] bad iostat when reading DOS file in a character array (non-advancing)

2009-09-12 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2009-09-13 03:41 --- Subject: Bug 41328 Author: jvdelisle Date: Sun Sep 13 03:41:41 2009 New Revision: 151665 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=151665 Log: 2009-09-12 Jerry DeLisle jvdeli...@gcc.gnu.org

[Bug fortran/41328] [4.4/4.5 regression] bad iostat when reading DOS file in a character array (non-advancing)

2009-09-12 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2009-09-13 03:44 --- Subject: Bug 41328 Author: jvdelisle Date: Sun Sep 13 03:44:34 2009 New Revision: 151666 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=151666 Log: 2009-09-12 Jerry DeLisle jvdeli...@gcc.gnu.org

[Bug fortran/41328] [4.4/4.5 regression] bad iostat when reading DOS file in a character array (non-advancing)

2009-09-12 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2009-09-13 03:46 --- Fixed on trunk. Will commit to 4.4.x in a few days. (approved by Janne on IRC) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41328

[Bug fortran/41328] [4.4/4.5 regression] bad iostat when reading DOS file in a character array (non-advancing)

2009-09-10 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2009-09-11 00:16 --- yes, this is a duplicate of the other PR I am workinmg on (PR41168). The code snippet in comment #1 is the exact spot I am working on. Two problems here. We can possiblly accessing memory that has not been

[Bug fortran/41328] [4.4/4.5 regression] bad iostat when reading DOS file in a character array (non-advancing)

2009-09-10 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2009-09-11 05:33 --- Patch submitted. See: http://gcc.gnu.org/ml/fortran/2009-09/msg00062.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41328

[Bug fortran/41168] incorrect processing of formatted records in mingw port

2009-09-10 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2009-09-11 05:38 --- PR41328 was submitted which has a little bit easier test case to use while not requiring mingw environment. So, I am closing this bug as the duplicate even though it was reported here first. A patch has been

[Bug fortran/41298] wrong-code: Default initializer C_NULL_PTR ignored

2009-09-09 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2009-09-10 01:08 --- Features, features, features, always features... :) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41298

[Bug fortran/41168] incorrect processing of formatted records in mingw port

2009-09-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2009-09-09 00:58 --- It is not clear whether we have two bugs or one here yet. I am investigating. One way to possibly reproduce this on linux machines is to define HAVE_CRLF in libgfortran/io/io.h. This way, all files affected

[Bug fortran/41168] incorrect processing of formatted records in mingw port

2009-09-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2009-09-09 02:11 --- I am able to reproduce this now, so I will begin to see if I can pinpoint the problem. Using: Index: io.h === --- io.h(revision 151491

[Bug fortran/40812] Files 2GB are incorrectly handled on mingw

2009-09-07 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2009-09-07 23:58 --- I worked on some of the current large file defines in libgfortran. Show me a patch of what you want to do. It should be OK. A patch is worth a thousand words. -- http://gcc.gnu.org/bugzilla/show_bug.cgi

[Bug fortran/41219] libgfortran build warnings

2009-09-07 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2009-09-08 00:59 --- Subject: Bug 41219 Author: jvdelisle Date: Tue Sep 8 00:59:05 2009 New Revision: 151495 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=151495 Log: 2009-09-07 Jerry DeLisle jvdeli...@gcc.gnu.org

[Bug fortran/41192] NAMELIST input with just a comment (NAME ! comment \) fails

2009-09-07 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2009-09-08 00:59 --- Subject: Bug 41192 Author: jvdelisle Date: Tue Sep 8 00:59:05 2009 New Revision: 151495 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=151495 Log: 2009-09-07 Jerry DeLisle jvdeli...@gcc.gnu.org

[Bug fortran/41192] NAMELIST input with just a comment (NAME ! comment \) fails

2009-09-07 Thread jvdelisle at gcc dot gnu dot org
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2009-09-08 01:19 --- Subject: Bug 41192 Author: jvdelisle Date: Tue Sep 8 01:18:48 2009 New Revision: 151496 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=151496 Log: 2009-09-07 Jerry DeLisle jvdeli...@gcc.gnu.org

[Bug fortran/41219] libgfortran build warnings

2009-09-06 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2009-09-06 18:17 --- Let me fix this. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/41219] libgfortran build warnings

2009-09-06 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2009-09-06 21:21 --- The following patch gets rid of the two warnings in list_read.c. The two enumerators have equivalent value. Regression tests fine. @@ -2377,7 +2377,7 @@ /* GFC_TYPE_UNKNOWN through for nulls

[Bug fortran/41219] libgfortran build warnings

2009-09-06 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2009-09-07 02:57 --- Regarding comment #6. In write_a_char4, one has: const char crlf[] = \r\n; write_default_char4 (dtp, crlf, 2, 0); but the second argument should be gfc_char4_t* Right. So what is \r\n

[Bug fortran/41278] internal compiler error related to matmul and transpose

2009-09-05 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2009-09-05 14:54 --- ICE confirmed with test case on 4.5 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41278

[Bug fortran/41192] NAMELIST input with just a comment (NAME ! comment \) fails

2009-09-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2009-09-04 20:16 --- Putting the standards discussion aside, this test case actually uncovered a real bug. In list_read.c, eat_line does nothing for internal units. If the test had used a real file, the comment would have been

[Bug fortran/41192] NAMELIST input with just a comment (NAME ! comment \) fails

2009-09-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2009-09-04 20:19 --- A side note: there are several places where we should use eat_line but instead we now have explicit loops. I will take a scan through and find those while I am at it. Just code clean-up. -- http

[Bug fortran/41168] incorrect processing of formatted records in mingw port

2009-09-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2009-09-04 23:09 --- I will add this to my list. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

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

2009-09-01 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2009-09-02 01:03 --- Subject: Bug 39229 Author: jvdelisle Date: Wed Sep 2 01:03:34 2009 New Revision: 151309 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=151309 Log: 2009-09-01 Jerry DeLisle jvdeli...@gcc.gnu.org

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

2009-09-01 Thread jvdelisle at gcc dot gnu dot org
--- Comment #8 from jvdelisle at gcc dot gnu dot org 2009-09-02 01:19 --- Closing. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status

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

2009-08-31 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2009-09-01 03:02 --- Subject: Bug 39229 Author: jvdelisle Date: Tue Sep 1 03:02:07 2009 New Revision: 151258 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=151258 Log: 2009-08-31 Jerry DeLisle jvdeli...@gcc.gnu.org

[Bug fortran/41192] NAMELIST input with just a comment (NAME ! comment \) fails

2009-08-30 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2009-08-30 18:15 --- Strictly speaking, Steve, I think you are correct. I have not finished my review of the standard. This is the first time I have seen namelist used like this for command line input. I suspect because it allows

[Bug fortran/41192] NAMELIST input with just a comment (NAME ! comment \) fails

2009-08-30 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2009-08-30 17:32 --- Thanks for report , I will fix this. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/41168] incorrect processing of formatted records in mingw port

2009-08-25 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2009-08-26 00:39 --- Works for me on latest trunk. 4.5 $ ./a.out 1234567890 end of file detected Please post the output from gfortran -v and also the exact URL where you got the download. The binaries from the wiki

[Bug fortran/41168] incorrect processing of formatted records in mingw port

2009-08-25 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2009-08-26 01:03 --- oops, you got it from equation.com. Hmm, I don't know much how they create their distribution.Suggest you contact them and see what they think. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41168

[Bug fortran/41162] [4.5 Regression] 416.gamess in SPEC CPU 2006 failed to build

2009-08-25 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2009-08-26 03:20 --- No bad news for a day, closing -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/41154] [4.5 Regression] Comma required after P descriptor

2009-08-24 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2009-08-25 01:03 --- Patch is simple and obvious. I will commit shortly. Index: io.c === --- io.c(revision 151045) +++ io.c(working copy) @@ -694,7

[Bug fortran/41154] [4.5 Regression] Comma required after P descriptor

2009-08-24 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2009-08-25 01:05 --- Subject: Bug 41154 Author: jvdelisle Date: Tue Aug 25 01:05:11 2009 New Revision: 151070 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=151070 Log: 2009-08-24 Jerry DeLisle jvdeli...@gcc.gnu.org

[Bug fortran/41154] [4.5 Regression] Comma required after P descriptor

2009-08-24 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2009-08-25 01:14 --- Subject: Bug 41154 Author: jvdelisle Date: Tue Aug 25 01:14:13 2009 New Revision: 151071 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=151071 Log: 2009-08-24 Jerry DeLisle jvdeli...@gcc.gnu.org

[Bug fortran/41154] [4.5 Regression] Comma required after P descriptor

2009-08-24 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2009-08-25 01:21 --- Closing. By all means let me know if anything else crops up. Thanks for catching this. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/35754] -std=f95: Reject 1P2E12.4 w/o a comma after the P

2009-08-24 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2009-08-25 01:22 --- Closing, fixed on trunk. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/37446] Diagnostic of edit descriptors, esp. EN

2009-08-24 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2009-08-25 01:24 --- Closing, fixed on trunk. Note to self. Have some locus clean-ups to do relative to 38439. Will pick those off next. -- jvdelisle at gcc dot gnu dot org changed: What|Removed

[Bug fortran/41162] [4.5 Regression] 416.gamess in SPEC CPU 2006 failed to build

2009-08-24 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2009-08-25 05:22 --- Subject: Bug 41162 Author: jvdelisle Date: Tue Aug 25 05:22:14 2009 New Revision: 151074 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=151074 Log: 2009-08-24 Jerry DeLisle jvdeli...@gcc.gnu.org

[Bug fortran/41162] [4.5 Regression] 416.gamess in SPEC CPU 2006 failed to build

2009-08-24 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2009-08-25 05:24 --- Fixed. I will leave this open for a bit. At the rate I am going I will break everything by midnight. (zzz) -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/35754] -std=f95: Reject 1P2E12.4 w/o a comma after the P

2009-08-23 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2009-08-23 06:25 --- F95 Standard: 10.1.1 Constraint: The comma used to separate format-items in a format-item-list may be omitted (1) Between a P edit descriptor and an immediately following F, E, EN, ES, D, or G edit descriptor

[Bug fortran/37446] Diagnostic of edit descriptors, esp. EN

2009-08-23 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2009-08-24 03:42 --- Subject: Bug 37446 Author: jvdelisle Date: Mon Aug 24 03:41:56 2009 New Revision: 151043 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=151043 Log: 2009-08-23 Jerry DeLisle jvdeli...@gcc.gnu.org

[Bug fortran/35754] -std=f95: Reject 1P2E12.4 w/o a comma after the P

2009-08-23 Thread jvdelisle at gcc dot gnu dot org
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2009-08-24 04:42 --- Subject: Bug 35754 Author: jvdelisle Date: Mon Aug 24 04:41:51 2009 New Revision: 151045 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=151045 Log: 2009-08-23 Jerry DeLisle jvdeli...@gcc.gnu.org

[Bug fortran/41075] [F2008] Implement unlimited format item

2009-08-16 Thread jvdelisle at gcc dot gnu dot org
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2009-08-17 03:51 --- Patch submitted to list. http://gcc.gnu.org/ml/fortran/2009-08/msg00195.html -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/31593] Invariant DO loop variables and subroutines

2009-08-14 Thread jvdelisle at gcc dot gnu dot org
--- Comment #18 from jvdelisle at gcc dot gnu dot org 2009-08-14 20:18 --- Patch applied cleanly, building , and will test shortly -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31593

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

2009-08-14 Thread jvdelisle at gcc dot gnu dot org
--- Comment #37 from jvdelisle at gcc dot gnu dot org 2009-08-15 00:50 --- Fixed on 4.5. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/34771] [4.3 only] Parenthesis around character variables: No expression

2009-08-14 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2009-08-15 02:03 --- I think we have moved past this and close it. 4.3 is regressions only. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/39668] Wrongly read namelist with two dimensional array.

2009-08-14 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2009-08-15 02:06 --- Toon, any word on this? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39668

[Bug fortran/36825] F2008: Rank 7 arrays [will break library ABI] libgfortran I/O+intrinsics:

2009-08-14 Thread jvdelisle at gcc dot gnu dot org
--- Comment #11 from jvdelisle at gcc dot gnu dot org 2009-08-15 02:17 --- Updating summary to reflect the focus of this PR. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/41075] New: [F2008] Implement unlimited format item

2009-08-14 Thread jvdelisle at gcc dot gnu dot org
: fortran 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=41075

[Bug fortran/41062] [4.4, 4.5 Regression] internal compiler error

2009-08-13 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2009-08-14 00:29 --- Severity is never considered a blocker with gfortran. Marking as a regression. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/40955] STDCALL attributes are not saved in the .MOD files

2009-08-13 Thread jvdelisle at gcc dot gnu dot org
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2009-08-14 02:35 --- Subject: Bug 40955 Author: jvdelisle Date: Fri Aug 14 02:35:32 2009 New Revision: 150733 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=150733 Log: 2009-08-13 Jerry DeLisle jvdeli...@gcc.gnu.org

[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 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=gccview=revrev=150476 Log: 2009-08-04 Jerry DeLisle jvdeli...@gcc.gnu.org

[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=gccview=revrev=150477 Log: 2009-08-04 Jerry DeLisle jvdeli...@gcc.gnu.org

[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/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=gccview=revrev=150357 Log: 2009-08-02 Jerry DeLisle jvdeli...@gcc.gnu.org

[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-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=18265action=view) A simple patch to resolve the problem This patch solves the original test case. It does require modification

[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/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

[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=gccview=revrev=149970 Log: 2009-07-22 Jerry DeLisle jvdeli...@gcc.gnu.org

[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 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 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=gccview=revrev=149795 Log: 2009-07-19 Janne Blomqvist j...@gcc.gnu.org

[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=gccview=revrev=149796 Log: 2009-07-19 Janne Blomqvist j...@gcc.gnu.org

[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=gccview=revrev=149797 Log: 2009-07-19 Janne Blomqvist j...@gcc.gnu.org

[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/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

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