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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71404 Jerry DeLisle changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |jvdelisle at gcc dot gnu.org

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71404 --- Comment #2 from Jerry DeLisle --- I can only guess until I get a test case. Perhaps the undo_symbols was too agressive.

[Bug fortran/52393] I/O: "READ format" statement with parenthesed default-char-expr

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52393 Jerry DeLisle changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/52393] I/O: "READ format" statement with parenthesed default-char-expr

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52393 --- Comment #12 from Jerry DeLisle --- Author: jvdelisle Date: Fri Jun 3 01:25:31 2016 New Revision: 237051 URL: https://gcc.gnu.org/viewcvs?rev=237051=gcc=rev Log: 2016-06-02 Jerry DeLisle PR fortran/52393

[Bug fortran/52393] I/O: "READ format" statement with parenthesed default-char-expr

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52393 --- Comment #11 from Jerry DeLisle --- Author: jvdelisle Date: Wed Jun 1 17:06:50 2016 New Revision: 237003 URL: https://gcc.gnu.org/viewcvs?rev=237003=gcc=rev Log: 2016-06-01 Jerry DeLisle PR fortran/52393

[Bug libfortran/48925] Code cleanup in write_float.def

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48925 Jerry DeLisle changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |jvdelisle at gcc dot gnu.org

[Bug fortran/66461] [4.9/5/6/7 Regression] ICE on missing end program in fixed source

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66461 Jerry DeLisle changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/66461] [4.9/5/6/7 Regression] ICE on missing end program in fixed source

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66461 --- Comment #27 from Jerry DeLisle --- Author: jvdelisle Date: Fri May 27 04:47:11 2016 New Revision: 236808 URL: https://gcc.gnu.org/viewcvs?rev=236808=gcc=rev Log: 2016-05-26 Jerry DeLisle Backport from

[Bug fortran/66461] [4.9/5/6/7 Regression] ICE on missing end program in fixed source

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66461 --- Comment #26 from Jerry DeLisle --- Author: jvdelisle Date: Fri May 27 03:17:03 2016 New Revision: 236807 URL: https://gcc.gnu.org/viewcvs?rev=236807=gcc=rev Log: 2016-05-26 Jerry DeLisle Backport from

[Bug fortran/66461] [4.9/5/6/7 Regression] ICE on missing end program in fixed source

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66461 --- Comment #25 from Jerry DeLisle --- Author: jvdelisle Date: Fri May 27 01:05:21 2016 New Revision: 236806 URL: https://gcc.gnu.org/viewcvs?rev=236806=gcc=rev Log: 2016-05-26 Jerry DeLisle Backport from

[Bug libfortran/71123] Namelist read failure on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71123 Jerry DeLisle changed: What|Removed |Added CC||ktietz at gcc dot gnu.org --- Comment

[Bug fortran/52393] I/O: "READ format" statement with parenthesed default-char-expr

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52393 --- Comment #10 from Jerry DeLisle --- Created attachment 38577 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38577=edit Final patch, regression tested I will submit this patch to list for approval.

[Bug fortran/52393] I/O: "READ format" statement with parenthesed default-char-expr

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52393 --- Comment #9 from Jerry DeLisle --- The following patch allows the program to compile. I just need to check the standard to confirm if the syntax in question also applies to WRITE. diff --git a/gcc/fortran/io.c b/gcc/fortran/io.c index

[Bug libfortran/71123] Namelist read failure on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71123 --- Comment #5 from Jerry DeLisle --- (In reply to Jerry DeLisle from comment #4) > Author: jvdelisle > Date: Tue May 24 06:16:00 2016 > New Revision: 236629 > > URL: https://gcc.gnu.org/viewcvs?rev=236629=gcc=rev > Log: > 2016-05-23 Jerry

[Bug libfortran/70684] [4.9/5/6/7 Regression] incorrect reading of values from file on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70684 --- Comment #22 from Jerry DeLisle --- (In reply to Jerry DeLisle from comment #21) > Author: jvdelisle > Date: Tue May 24 06:11:21 2016 > New Revision: 236628 > > URL: https://gcc.gnu.org/viewcvs?rev=236628=gcc=rev > Log: > 2016-05-23 Jerry

[Bug libfortran/71123] Namelist read failure on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71123 --- Comment #4 from Jerry DeLisle --- Author: jvdelisle Date: Tue May 24 06:16:00 2016 New Revision: 236629 URL: https://gcc.gnu.org/viewcvs?rev=236629=gcc=rev Log: 2016-05-23 Jerry DeLisle PR

[Bug libfortran/70684] [4.9/5/6/7 Regression] incorrect reading of values from file on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70684 --- Comment #21 from Jerry DeLisle --- Author: jvdelisle Date: Tue May 24 06:11:21 2016 New Revision: 236628 URL: https://gcc.gnu.org/viewcvs?rev=236628=gcc=rev Log: 2016-05-23 Jerry DeLisle PR

[Bug fortran/66461] [4.9/5/6/7 Regression] ICE on missing end program in fixed source

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66461 --- Comment #24 from Jerry DeLisle --- Author: jvdelisle Date: Tue May 24 04:15:39 2016 New Revision: 236627 URL: https://gcc.gnu.org/viewcvs?rev=236627=gcc=rev Log: 2016-05-23 Jerry DeLisle PR fortran/66461

[Bug fortran/66461] [4.9/5/6/7 Regression] ICE on missing end program in fixed source

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66461 --- Comment #22 from Jerry DeLisle --- This patch, by itself, fixes the whole issue. Regression tested on x86-64. Mikael shook the old brain cells. diff --git a/gcc/fortran/scanner.c b/gcc/fortran/scanner.c index f4dedd69..6a7a5b68 100644 ---

[Bug fortran/66461] [4.9/5/6/7 Regression] ICE on missing end program in fixed source

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66461 --- Comment #21 from Jerry DeLisle --- (In reply to Mikael Morin from comment #20) > (In reply to Mikael Morin from comment #19) > > > > what I don't understand is that error itself, > > It comes from scanner.c's end_flag which is cleared on

[Bug fortran/66461] [4.9/5/6/7 Regression] ICE on missing end program in fixed source

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66461 --- Comment #17 from Jerry DeLisle --- Steve, I like your patch much better. I will test and commit for you with a Changelog Dominique, Do you have a version of gfortran where this does not give an ICE??? I have just one other thing to check

[Bug fortran/66461] [4.9/5/6/7 Regression] ICE on missing end program in fixed source

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66461 --- Comment #14 from Jerry DeLisle --- (In reply to Dominique d'Humieres from comment #13) --- snip --- > > Although I partially agree with that, I don't understand why > > if ( x(1) < 0 .or. & > x(2) < 0 ) print

[Bug libfortran/71123] Namelist read failure on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71123 --- Comment #3 from Jerry DeLisle --- This patch regression tests OK and fixes the namelist read. diff --git a/libgfortran/io/list_read.c b/libgfortran/io/list_read.c index b8e174c5..6ea6007a 100644 --- a/libgfortran/io/list_read.c +++

[Bug fortran/66461] [4.9/5/6/7 Regression] ICE on missing end program in fixed source

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66461 --- Comment #12 from Jerry DeLisle --- I have a patch testing for this. I am not sure this is a regression. I see it as far back as 4.5. I don't have any earlier builds. My thinking is that since this is an ICE on invalid code, I don't want

[Bug libfortran/71123] Namelist read failure on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71123 Jerry DeLisle changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |jvdelisle at gcc dot gnu.org

[Bug libfortran/71123] New: Namelist read failure on Windows

Assignee: unassigned at gcc dot gnu.org Reporter: jvdelisle at gcc dot gnu.org Target Milestone: --- Posted on the gfortran list. The following program works fine under Linux but fails under Windows. IMPLICIT REAL*8(A-H,O-Z) DIMENSION SENID(30) NAMELIST /FITH

[Bug fortran/70959] [6/7 Regression] Invalid type determination due to expression in a type declaration statement

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70959 --- Comment #3 from Jerry DeLisle --- I have tried changing the matching order so that integer constants are matched before real or complex. It fixes the reported problem but results in numerous test suite failures. I wonder. If we just change

[Bug fortran/66461] [4.9/5/6/7 Regression] ICE on missing end program in fixed source

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66461 --- Comment #10 from Jerry DeLisle --- This is a bandaid, but it works. diff --git a/gcc/fortran/match.c b/gcc/fortran/match.c index 2490f856..726973a6 100644 --- a/gcc/fortran/match.c +++ b/gcc/fortran/match.c @@ -1438,7 +1438,16 @@

[Bug fortran/71087] scipy amos crash

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71087 --- Comment #9 from Jerry DeLisle --- (In reply to Nick from comment #0) > Created attachment 38475 [details] > Source code trigging bug > > - Compiling amos/zunhj.f in scipy package crashes with: > > zunhj.f:1:0: > >SUBROUTINE

[Bug libfortran/70684] [4.9/5/6/7 Regression] incorrect reading of values from file on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70684 Jerry DeLisle changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug libfortran/70684] [4.9/5/6/7 Regression] incorrect reading of values from file on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70684 --- Comment #19 from Jerry DeLisle --- Fixed on 7, 6, 5, and 4.9. and closing. Please let me know if further problems arise.

[Bug libfortran/70684] [4.9/5/6/7 Regression] incorrect reading of values from file on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70684 --- Comment #18 from Jerry DeLisle --- Author: jvdelisle Date: Fri May 6 01:18:59 2016 New Revision: 235941 URL: https://gcc.gnu.org/viewcvs?rev=235941=gcc=rev Log: 2016-05-05 Jerry DeLisle Backport from

[Bug fortran/70959] Invalid type determination due to expression in a type declaration statement

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70959 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at gcc dot gnu.org

[Bug libfortran/70684] [4.9/5/6/7 Regression] incorrect reading of values from file on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70684 --- Comment #17 from Jerry DeLisle --- Author: jvdelisle Date: Tue May 3 00:51:30 2016 New Revision: 235801 URL: https://gcc.gnu.org/viewcvs?rev=235801=gcc=rev Log: 2016-05-02 Jerry DeLisle Backport from

[Bug libfortran/70684] [4.9/5/6/7 Regression] incorrect reading of values from file on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70684 --- Comment #16 from Jerry DeLisle --- Author: jvdelisle Date: Sun Apr 24 05:07:21 2016 New Revision: 235391 URL: https://gcc.gnu.org/viewcvs?rev=235391=gcc=rev Log: 2016-04-23 Jerry DeLisle PR

[Bug libfortran/70684] [4.9/5/6/7 Regression] incorrect reading of values from file on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70684 --- Comment #15 from Jerry DeLisle --- (In reply to Andy May from comment #14) --- snip --- > > Of course, I really appreciate the work that goes into this. I've already > made a local patch file with your fix so that the mxe.cc gcc builds with

[Bug libfortran/70684] [4.9/5/6/7 Regression] incorrect reading of values from file on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70684 --- Comment #13 from Jerry DeLisle --- (In reply to Andy May from comment #12) > I don't know that it's necessary or desired to support both '\n' and '\r' as > eol, but instead the native eol just needs to be used consistently > everywhere, for

[Bug libfortran/70684] [4.9/5/6/7 Regression] incorrect reading of values from file on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70684 --- Comment #10 from Jerry DeLisle --- (In reply to Ray Donnelly from comment #9) > Should the other two places - next_char_default () and next_char_internal () > -that also do: > > dtp->u.p.at_eol = (c == '\n' || c == EOF); > > not check for

[Bug libfortran/70684] [4.9/5/6/7 Regression] incorrect reading of values from file on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70684 --- Comment #8 from Jerry DeLisle --- Author: jvdelisle Date: Tue Apr 19 19:24:28 2016 New Revision: 235220 URL: https://gcc.gnu.org/viewcvs?rev=235220=gcc=rev Log: 2016-04-19 Jerry DeLisle PR

[Bug libfortran/70684] [4.9/5/6/7 Regression] incorrect reading of values from file on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70684 --- Comment #7 from Jerry DeLisle --- The following patch fixes the issue. diff --git a/libgfortran/io/list_read.c b/libgfortran/io/list_read.c index e24b3922..b8e174c5 100644 --- a/libgfortran/io/list_read.c +++ b/libgfortran/io/list_read.c @@

[Bug libfortran/70684] [4.9/5/6/7 Regression] incorrect reading of values from file on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70684 --- Comment #6 from Jerry DeLisle --- The regression occurred at r200238, which was a fix for PR57633. I am working on a fix.

[Bug libfortran/70684] [Regression 5.3, 6] incorrect reading of values from file on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70684 --- Comment #3 from Jerry DeLisle --- This slightly modified version of the testcase shows the bug with Linux: program test implicit none integer,parameter :: isize=12 integer,parameter :: funit=12 integer :: i character(1), parameter ::

[Bug libfortran/70684] [Regression 5.3, 6] incorrect reading of values from file on Windows

||2016-04-15 Assignee|unassigned at gcc dot gnu.org |jvdelisle at gcc dot gnu.org Summary|incorrect reading of values |[Regression 5.3, 6] |from file on Windows|incorrect reading of values

[Bug libfortran/70684] incorrect reading of values from file on Windows

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70684 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at gcc dot gnu.org

[Bug fortran/68600] Inlined MATMUL is too slow.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68600 --- Comment #13 from Jerry DeLisle --- (In reply to Thomas Koenig from comment #12) > (In reply to Jerry DeLisle from comment #11) ---snip-- > > May I suggest reading the docs? ;-) > --- snip --- > The default value for N is the value

[Bug fortran/52884] double precision constants promoted to 16 byte by -fdefault-real-8

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52884 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at gcc dot gnu.org

[Bug fortran/67039] Documentation of pseudorandom number intrinsics is incorrect

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67039 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at gcc dot gnu.org

[Bug fortran/60751] Extra comma in WRITE statement not diagnosed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60751 --- Comment #18 from Jerry DeLisle --- (In reply to Dominique d'Humieres from comment #17) > Note that the extra comma is used in the following tests: > > gfortran.dg/array_constructor_49.f90 > gfortran.dg/integer_exponentiation_6.F90 >

[Bug fortran/51820] [doc] underscoring documentation incorrect

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51820 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at gcc dot gnu.org

[Bug fortran/58000] Accept OPEN( ... NAME=) with -std=legacy

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58000 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at gcc dot gnu.org

[Bug fortran/68566] ICE on using unusable array in reshape (double free or corruption)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68566 --- Comment #10 from Jerry DeLisle --- Author: jvdelisle Date: Sat Apr 9 19:09:02 2016 New Revision: 234864 URL: https://gcc.gnu.org/viewcvs?rev=234864=gcc=rev Log: 2016-04-09 Jerry DeLisle PR fortran/68566

[Bug fortran/68600] Inlined MATMUL is too slow.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68600 --- Comment #11 from Jerry DeLisle --- (In reply to Jerry DeLisle from comment #8) > Created attachment 36887 [details] > A faster version > > I took the example code found in > http://wiki.cs.utexas.edu/rvdg/HowToOptimizeGemm/ where the

[Bug fortran/52393] I/O: "READ format" statement with parenthesed default-char-expr

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52393 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at gcc dot gnu.org

[Bug fortran/68566] ICE on using unusable array in reshape (double free or corruption)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68566 --- Comment #9 from Jerry DeLisle --- The following additional patchlet does the trick. Still need to regression test. diff --git a/gcc/fortran/array.c b/gcc/fortran/array.c index 2fc9dfaf..8fef30ce 100644 --- a/gcc/fortran/array.c +++

[Bug fortran/68566] ICE on using unusable array in reshape (double free or corruption)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68566 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at gcc dot gnu.org

[Bug fortran/70235] [4.9/5/6 Regression] Incorrect output with PF format

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70235 --- Comment #24 from Jerry DeLisle --- Dominiq, I have tested as much as I can with several variations of values of the float and all looks good. I am ready to approve your patch when you are.

[Bug fortran/70235] [4.9/5/6 Regression] Incorrect output with PF format

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70235 --- Comment #23 from Jerry DeLisle --- (In reply to Dominique d'Humieres from comment #22) > Created attachment 38107 [details] > New patch with test. > > With the patch we now get for y=6431.25 > > ru,-8pf18.2 y= 0.01 > > IMO

[Bug fortran/69043] Trying to include a directory causes an infinite loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69043 Jerry DeLisle changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[Bug fortran/70235] [4.9/5/6 Regression] Incorrect output with PF format

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70235 --- Comment #20 from Jerry DeLisle --- (In reply to Dominique d'Humieres from comment #19) > Created attachment 38100 [details] > Another patch with correct rounding > > > While I think the handling of nafter < 0 is correct, it is probably > >

[Bug fortran/70235] [4.9/5/6 Regression] Incorrect output with PF format

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70235 --- Comment #15 from Jerry DeLisle --- Created attachment 38091 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38091=edit A more exhaustive testing program This test allows at least visual inspection of the patterns. The test omits the

[Bug fortran/70235] [4.9/5/6 Regression] Incorrect output with PF format

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70235 --- Comment #14 from Jerry DeLisle --- Created attachment 38090 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38090=edit Updated patch correcting problem found by Dominique This is what I came up with independent of Dominiques patch.

[Bug fortran/70235] [4.9/5/6 Regression] Incorrect output with PF format

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70235 --- Comment #12 from Jerry DeLisle --- (In reply to Dominique d'Humieres from comment #11) > > Created attachment 38075 [details] > > A patch for testing > > With the patch and using the test attached to comment 5 with y = 1.0 and > d=8, I get

[Bug fortran/70235] [4.9/5/6 Regression] Incorrect output with PF format

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70235 --- Comment #10 from Jerry DeLisle --- Created attachment 38075 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38075=edit A patch for testing Please test this patch as much as possible. I think I have it right, but one can never tell so

[Bug fortran/70233] Missing diagnostic in array constructor, different size strings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70233 --- Comment #9 from Jerry DeLisle --- Dominique, thanks for finding this. It even makes sense; if the typespec is given one knows what the size of the string is. If not given, how does one decide which is the right size, so require that they

[Bug fortran/70235] [4.9/5/6 Regression] Incorrect output with PF format

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70235 --- Comment #8 from Jerry DeLisle --- (In reply to Tobias Burnus from comment #7) ... snip ... > > My gut feeling is that it has something to do with having "precision" == 17 > in that function. In any case, the nafter is too large when nblanks

[Bug fortran/70235] [4.9/5/6 Regression] Incorrect output with PF format

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70235 --- Comment #5 from Jerry DeLisle --- Created attachment 37990 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37990=edit A useful test program I get correct results using the attached with gcc version 4.6.4 (GCC) Broken in 4.9, 5, and 6.

[Bug fortran/69043] Trying to include a directory causes an infinite loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69043 --- Comment #8 from Jerry DeLisle --- Author: jvdelisle Date: Sat Mar 19 20:28:38 2016 New Revision: 234352 URL: https://gcc.gnu.org/viewcvs?rev=234352=gcc=rev Log: 2016-03-19 Jerry DeLisle PR fortran/69043

[Bug fortran/70235] [4.9/5/6 Regression] Incorrect output with PF format

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70235 --- Comment #6 from Jerry DeLisle --- *** Bug 70237 has been marked as a duplicate of this bug. ***

[Bug fortran/70237] [4.9/5/6 Regression] Incorrect 0.0 output with PF format

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70237 Jerry DeLisle changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/70233] Missing diagnostic in array constructor, different size strings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70233 --- Comment #6 from Jerry DeLisle --- The failures I looked at were becasue the constructors were using strings of different sizes. So my question was going to be what are the rules. Are the strings suppose to get padded to the length of the

[Bug fortran/69043] Trying to include a directory causes an infinite loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69043 Jerry DeLisle changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

[Bug fortran/70235] [4.9/5/6 Regression] Incorrect output with PF format

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70235 --- Comment #9 from Jerry DeLisle --- I have isolated to a block of code which is dead relative to our current testsuite. Now to work on the solution.

[Bug fortran/70233] Missing diagnostic in array constructor, different size strings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70233 --- Comment #3 from Jerry DeLisle --- Harold, Thanks for the help and I will test

[Bug fortran/70235] [4.9/5/6 Regression] Incorrect output with PF format

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70235 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at gcc dot gnu.org

[Bug fortran/70237] [4.9/5/6 Regression] Incorrect 0.0 output with PF format

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70237 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at gcc dot gnu.org

[Bug fortran/70233] New: Missing diagnostic in array constructor, different size strings

Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: jvdelisle at gcc dot gnu.org Target Milestone: --- In the following code, one case of the constructor gives an error and one does not. integer, parameter :: char_len = 32 character

[Bug fortran/70231] Runtime error: Different CHARACTER lengths in array constructor with allocatable array and -O0

||2016-03-15 CC||jvdelisle at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Jerry DeLisle --- Interesting: -fdump-tree-original snippets snip ch_array.dim[0].lbound = 1

[Bug fortran/69043] Trying to include a directory causes an infinite loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69043 Jerry DeLisle changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/69043] Trying to include a directory causes an infinite loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69043 --- Comment #4 from Jerry DeLisle --- Author: jvdelisle Date: Sun Mar 13 17:38:07 2016 New Revision: 234169 URL: https://gcc.gnu.org/viewcvs?rev=234169=gcc=rev Log: 2016-03-13 Jerry DeLisle Jim MacArthur

[Bug fortran/69520] Implement reversal of -fcheck options

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69520 Jerry DeLisle changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/70215] segmentation fault with allocate on assign; 32 bit version, not 64 bit

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70215 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at gcc dot gnu.org

[Bug fortran/69520] Implement reversal of -fcheck options

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69520 --- Comment #8 from Jerry DeLisle --- Author: jvdelisle Date: Sun Mar 13 00:19:08 2016 New Revision: 234167 URL: https://gcc.gnu.org/viewcvs?rev=234167=gcc=rev Log: 2016-03-12 Jerry DeLisle Harold Anlauf

[Bug fortran/69520] Implement reversal of -fcheck options

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69520 --- Comment #7 from Jerry DeLisle --- (In reply to Harald Anlauf from comment #6) > Hi Jerry, > > do you think my suggested patch could be applied before the 6 release? > > Thanks, > Harald This is my plan. Just out of town for a few days.

[Bug fortran/70058] Segmentation fault when open file with existing file and status = "UNKNOWN"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70058 Jerry DeLisle changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/70058] Segmentation fault when open file with existing file and status = "UNKNOWN"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70058 --- Comment #6 from Jerry DeLisle --- (In reply to kargl from comment #5) > (In reply to Jerry DeLisle from comment #4) > > The problem does not exist on Linux for sure. Not sure if this is a TDM > > distribution problem, a Windows problem, a

[Bug fortran/70058] Segmentation fault when open file with existing file and status = "UNKNOWN"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70058 --- Comment #4 from Jerry DeLisle --- The problem does not exist on Linux for sure. Not sure if this is a TDM distribution problem, a Windows problem, a MingW problem, or gfortran. I am going to have to get set up on Windows so this may take a

[Bug fortran/70068] ICE: out of memory on involving empty substring

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70068 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at gcc dot gnu.org

[Bug fortran/70058] Segmentation fault when open file with existing file and status = "UNKNOWN"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70058 --- Comment #2 from Jerry DeLisle --- Paul, could you please post the terminal output that gives the error message please.

[Bug fortran/70058] Segmentation fault when open file with existing file and status = "UNKNOWN"

||2016-03-03 CC||jvdelisle at gcc dot gnu.org Assignee|unassigned at gcc dot gnu.org |jvdelisle at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Jerry DeLisle --- Thanks for report

[Bug fortran/45179] Support UTF-8 (and other encodings) in the source file (.f90) for CHARACTER(kind=4)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45179 Jerry DeLisle changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |jvdelisle at gcc dot gnu.org

[Bug fortran/66709] ICE on formatted io with parameter array specifier fmt

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66709 Jerry DeLisle changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |jvdelisle at gcc dot gnu.org

[Bug fortran/56226] Add support for DEC UNION and MAP extensions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56226 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at gcc dot gnu.org

[Bug fortran/56007] Remarkably bad error message with DO array=1,2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56007 Jerry DeLisle changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/56007] Remarkably bad error message with DO array=1,2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56007 --- Comment #10 from Jerry DeLisle --- Author: jvdelisle Date: Sun Feb 28 19:07:42 2016 New Revision: 233795 URL: https://gcc.gnu.org/viewcvs?rev=233795=gcc=rev Log: 2016-02-28 Harald Anlauf Jerry DeLisle

[Bug fortran/66310] Problems with intrinsic repeat for large number of copies

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66310 --- Comment #9 from Jerry DeLisle --- (In reply to Dominique d'Humieres from comment #8) ... snip ... > before the patch and with > > pr66310_1.f90:3:0: > >print *, repeat(z, huge(1_4)) > > internal compiler error: Segmentation

[Bug fortran/56007] Remarkably bad error message with DO array=1,2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56007 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at gcc dot gnu.org

[Bug fortran/61156] [4.9/5/6 Regression] Internal compiler error for Fortran files when specifying a file instead of an include directory with -I

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61156 Jerry DeLisle changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/61156] [4.9/5/6 Regression] Internal compiler error for Fortran files when specifying a file instead of an include directory with -I

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61156 --- Comment #12 from Jerry DeLisle --- Author: jvdelisle Date: Sun Feb 28 18:16:56 2016 New Revision: 233793 URL: https://gcc.gnu.org/viewcvs?rev=233793=gcc=rev Log: 2016-02-28 Jerry DeLisle Backported from

[Bug fortran/61156] [4.9/5/6 Regression] Internal compiler error for Fortran files when specifying a file instead of an include directory with -I

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61156 --- Comment #11 from Jerry DeLisle --- Author: jvdelisle Date: Sun Feb 28 06:50:27 2016 New Revision: 233789 URL: https://gcc.gnu.org/viewcvs?rev=233789=gcc=rev Log: 2016-02-27 Jerry DeLisle Backported from

[Bug fortran/69456] Namelist value with trailing sign is ignored without error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69456 Jerry DeLisle changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

<    6   7   8   9   10   11   12   13   14   15   >