[Bug fortran/84387] Defined output does not work for a derived type that has no components

||2018-02-16 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 --- This does seem

[Bug libfortran/84156] [8 Regression] valgrind error with print *,1

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

[Bug libfortran/84156] [8 Regression] valgrind error with print *,1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84156 --- Comment #2 from Jerry DeLisle --- I think this is related to the front end initializing the dtp common structure and the runtime using it. This looking unititiaklzed and therefore a false error. I am not sure valgrind can detect this and I

[Bug fortran/82086] namelist read with repeat count fails when item is member of array of structures

at gcc dot gnu.org |jvdelisle at gcc dot gnu.org --- Comment #9 from Jerry DeLisle --- OK, will see what I can do.

[Bug fortran/82086] namelist read with repeat count fails when item is member of array of structures

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82086 --- Comment #6 from Jerry DeLisle --- (In reply to Harald Anlauf from comment #4) > (In reply to Jerry DeLisle from comment #3) > > I think this bug is invalid and gfortran is correct. > > > > If you do this: > > > > > > ta(1:8)%c = 'bogus'

[Bug fortran/82086] namelist read with repeat count fails when item is member of array of structures

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82086 --- Comment #3 from Jerry DeLisle --- I think this bug is invalid and gfortran is correct. If you do this: ta(1:8)%c = 'bogus' / You get what you expect. The way you have it, you can not put 8 strings called 'bogus' into one strng element

[Bug fortran/83152] Possible run time error in derived type i/o

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

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66310 --- Comment #18 from Jerry DeLisle --- Can this be closed.

[Bug fortran/82007] DTIO write format stored in a string leads to severe errors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82007 --- Comment #8 from Jerry DeLisle --- Should I backport this to 7?

[Bug libfortran/83811] fortran 'e' format broken for single digit exponents

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

[Bug libfortran/83811] fortran 'e' format broken for single digit exponents

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83811 --- Comment #5 from Jerry DeLisle --- Author: jvdelisle Date: Sun Jan 14 21:44:50 2018 New Revision: 256675 URL: https://gcc.gnu.org/viewcvs?rev=256675=gcc=rev Log: 2018-01-14 Jerry DeLisle Backport from trunk

[Bug libfortran/83811] fortran 'e' format broken for single digit exponents

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83811 --- Comment #4 from Jerry DeLisle --- Author: jvdelisle Date: Sun Jan 14 17:36:29 2018 New Revision: 256669 URL: https://gcc.gnu.org/viewcvs?rev=256669=gcc=rev Log: 2018-01-18 Jerry DeLisle PR

[Bug libfortran/83811] fortran 'e' format broken for single digit exponents

||2018-01-14 Assignee|unassigned at gcc dot gnu.org |jvdelisle at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #3 from Jerry DeLisle --- Further investigation is showing me that the buffer containing the float string is wrong

[Bug fortran/82007] DTIO write format stored in a string leads to severe errors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82007 --- Comment #7 from Jerry DeLisle --- Author: jvdelisle Date: Sat Jan 13 20:41:00 2018 New Revision: 256649 URL: https://gcc.gnu.org/viewcvs?rev=256649=gcc=rev Log: 2018-01-13 Jerry DeLisle PR fortran/82007

[Bug fortran/83829] New: Implement runtime checks for DT format specifier and allignment with effective items

Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: jvdelisle at gcc dot gnu.org Target Milestone: --- As discussed on the gfortran mailing list, we need to hadle the case where a User Defined Derived Type Procedure

[Bug fortran/83525] open(newunit=funit, status="scratch") fails if an internal file (characters) was read previously.

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

[Bug fortran/83525] open(newunit=funit, status="scratch") fails if an internal file (characters) was read previously.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83525 --- Comment #4 from Jerry DeLisle --- Author: jvdelisle Date: Fri Jan 12 20:01:47 2018 New Revision: 256595 URL: https://gcc.gnu.org/viewcvs?rev=256595=gcc=rev Log: 2018-01-12 Jerry DeLisle PR

[Bug libfortran/83811] fortran 'e' format broken for single digit exponents

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83811 --- Comment #2 from Jerry DeLisle --- The change has nothing to do with internl units. So it is related to the write float refctoring we did.

[Bug libfortran/83811] fortran 'e' format broken for single digit exponents

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

[Bug fortran/83704] pr31243 revisited

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83704 --- Comment #9 from Jerry DeLisle --- (In reply to Janne Blomqvist from comment #8) > - for (i = 0; i < length; i++) > + for (size_t = 0; i < length; i++) typo above. Change to: + for (size_t i = 0; i < length; i++)

[Bug fortran/83704] pr31243 revisited

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83704 --- Comment #7 from Jerry DeLisle --- (In reply to Dominique d'Humieres from comment #6) > > However this does not fix the output of > > print *, "'", ch(1:2_8**32_8+3_8), "'" > > This is fixed by the following patch > > ---

[Bug fortran/83704] pr31243 revisited

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83704 --- Comment #4 from Jerry DeLisle --- I can compile it fine, but do not have enough memory to run it. So dominiq, how much RAM do you have, maybe I can find a machine of sufficient capacity. One has to be careful we dont take someones OS to its

[Bug fortran/83704] pr31243 revisited

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

[Bug fortran/50892] Internal compiler error: in gimplify_expr, at gimplify.c:7477

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

[Bug fortran/78534] Use a larger integer type for character lengths on 64-bit targets

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78534 --- Comment #21 from Jerry DeLisle --- Regrssion tested on x86_64-pc-freeBSD, no failures

[Bug fortran/83525] open(newunit=funit, status="scratch") fails if an internal file (characters) was read previously.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83525 --- Comment #3 from Jerry DeLisle --- (In reply to Thomas Koenig from comment #2) > This looks very much like a dup of PR83436. > > Close as duplicate? I am going to add the test case and then close this.

[Bug fortran/40196] [F03] [F08] Type parameter inquiry (str%len, a%kind) and Complex parts (z%re, z%im)

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

[Bug fortran/81499] internal compiler error when compiling gfortran code with user-defined derived type i/o

at gcc dot gnu.org |jvdelisle at gcc dot gnu.org --- Comment #3 from Jerry DeLisle --- I was looking at this last night. We are in an infinite loop in the recursive derived_inaccessible function. I will explore further.

[Bug libfortran/81939] valgrind error message in build_float_string and heap-buffer-overflow on address sanitized libgfortran.so

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81939 --- Comment #5 from Jerry DeLisle --- Did this get fixed or is it another issue from the buffer overflow by one I already fixed?

[Bug fortran/82007] DTIO write format stored in a string leads to severe errors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82007 --- Comment #6 from Jerry DeLisle --- Created attachment 42992 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42992=edit A peliminary patch The attached patch allows the test cases to compile and run. Remaining is to formulate what

[Bug fortran/83522] gfortran is sometimes confused between what is an element range and what is a character range

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83522 --- Comment #2 from Jerry DeLisle --- The expression strings(:)(:) is invalid fortran. F2008 R610. R610 parent-string is scalar-variable-name or array-element or scalar-structure-component

[Bug libfortran/83613] [8 Regression] Executing gfortran.dg/inquire_internal.f90 hangs on darwin after r255621

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83613 --- Comment #10 from Jerry DeLisle --- Author: jvdelisle Date: Sat Dec 30 02:14:34 2017 New Revision: 256041 URL: https://gcc.gnu.org/viewcvs?rev=256041=gcc=rev Log: 2017-12-29 Jerry DeLisle Backport from

[Bug libfortran/83613] [8 Regression] Executing gfortran.dg/inquire_internal.f90 hangs on darwin after r255621

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83613 --- Comment #9 from Jerry DeLisle --- I also have to commit to gcc7 as well, which has the same error in it. Thanks for the report Dominiq.

[Bug libfortran/83613] [8 Regression] Executing gfortran.dg/inquire_internal.f90 hangs on darwin after r255621

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83613 --- Comment #7 from Jerry DeLisle --- Author: jvdelisle Date: Fri Dec 29 22:36:25 2017 New Revision: 256035 URL: https://gcc.gnu.org/viewcvs?rev=256035=gcc=rev Log: 2017-12-29 Jerry DeLisle PR

[Bug fortran/83560] list-directed formatting of INTEGER is missing plus on output when output open with SIGN='PLUS'

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

[Bug libfortran/83613] [8 Regression] Executing gfortran.dg/inquire_internal.f90 hangs on darwin after r255621

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83613 --- Comment #6 from Jerry DeLisle --- Try this patch: diff --git a/libgfortran/io/unit.c b/libgfortran/io/unit.c index 2ca8525fbec..a655665aa8a 100644 --- a/libgfortran/io/unit.c +++ b/libgfortran/io/unit.c @@ -707,7 +707,9 @@ init_units (void)

[Bug fortran/83560] list-directed formatting of INTEGER is missing plus on output when output open with SIGN='PLUS'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83560 --- Comment #8 from Jerry DeLisle --- Author: jvdelisle Date: Fri Dec 29 19:25:31 2017 New Revision: 256034 URL: https://gcc.gnu.org/viewcvs?rev=256034=gcc=rev Log: 2017-12-29 Jerry DeLisle PR

[Bug libfortran/83613] [8 Regression] Executing gfortran.dg/inquire_internal.f90 hangs on darwin after r255621

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83613 --- Comment #5 from Jerry DeLisle --- (In reply to Jerry DeLisle from comment #4) --- snip --- > > I dont understand why you did not have those two lines in your source tree. > These were part of my previous patch committed. Oh I see, for some

[Bug libfortran/83613] [8 Regression] Executing gfortran.dg/inquire_internal.f90 hangs on darwin after r255621

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83613 --- Comment #4 from Jerry DeLisle --- (In reply to Dominique d'Humieres from comment #3) > > Can you try this and report: > > ... > > It does not work without the patch > > --- ../_clean/libgfortran/io/unit.c 2017-12-14 10:02:30.0

[Bug libfortran/83613] [8 Regression] Executing gfortran.dg/inquire_internal.f90 hangs on darwin after r255621

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83613 --- Comment #2 from Jerry DeLisle --- Can you try this and report: diff --git a/libgfortran/io/inquire.c b/libgfortran/io/inquire.c index 6ba1224d77c..fefe6e9a165 100644 --- a/libgfortran/io/inquire.c +++ b/libgfortran/io/inquire.c @@ -47,9

[Bug libfortran/83613] [8 Regression] Executing gfortran.dg/inquire_internal.f90 hangs on darwin after r255621

at gcc dot gnu.org |jvdelisle at gcc dot gnu.org --- Comment #1 from Jerry DeLisle --- I will take another look at this.

[Bug fortran/83560] list-directed formatting of INTEGER is missing plus on output when output open with SIGN='PLUS'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83560 --- Comment #7 from Jerry DeLisle --- Patch posted here: https://gcc.gnu.org/ml/fortran/2017-12/msg00089.html

[Bug fortran/83560] list-directed formatting of INTEGER is missing plus on output when output open with SIGN='PLUS'

at gcc dot gnu.org |jvdelisle at gcc dot gnu.org --- Comment #5 from Jerry DeLisle --- I simply never implemented it for listdirected output. Just an oversight. Working it now.

[Bug libfortran/35014] Libgfortran.a (downloaded) is not PIC compiled...

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

[Bug fortran/83522] gfortran is sometimes confused between what is an element range and what is a character range

||2017-12-22 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 --- Confirmed. I

[Bug fortran/83525] open(newunit=funit, status="scratch") fails if an internal file (characters) was read previously.

||2017-12-22 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 --- This is working

[Bug fortran/83458] F2008: inquire fails on units opened with newunit=

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

[Bug fortran/83458] F2008: inquire fails on units opened with newunit=

||2017-12-22 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 --- Confirmed and I

[Bug libfortran/81937] stack-buffer-overflow on memcpy in libgfortran/io/unix.c on character(kind=4)

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

[Bug libfortran/81937] stack-buffer-overflow on memcpy in libgfortran/io/unix.c on character(kind=4)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81937 --- Comment #6 from Jerry DeLisle --- Author: jvdelisle Date: Sat Dec 16 22:41:13 2017 New Revision: 255754 URL: https://gcc.gnu.org/viewcvs?rev=255754=gcc=rev Log: 2017-12-16 Jerry DeLisle Backport from trunk

[Bug libfortran/81937] stack-buffer-overflow on memcpy in libgfortran/io/unix.c on character(kind=4)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81937 --- Comment #5 from Jerry DeLisle --- Author: jvdelisle Date: Sat Dec 16 21:57:17 2017 New Revision: 255752 URL: https://gcc.gnu.org/viewcvs?rev=255752=gcc=rev Log: 2017-12-16 Jerry DeLisle Backport from trunk

[Bug libfortran/78549] Very slow formatted internal file output

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78549 --- Comment #32 from Jerry DeLisle --- Author: jvdelisle Date: Sat Dec 16 19:59:14 2017 New Revision: 255751 URL: https://gcc.gnu.org/viewcvs?rev=255751=gcc=rev Log: 2017-12-16 Jerry DeLisle Backport from

[Bug libfortran/81937] stack-buffer-overflow on memcpy in libgfortran/io/unix.c on character(kind=4)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81937 --- Comment #4 from Jerry DeLisle --- Author: jvdelisle Date: Sat Dec 16 19:50:42 2017 New Revision: 255750 URL: https://gcc.gnu.org/viewcvs?rev=255750=gcc=rev Log: 2017-12-16 Jerry DeLisle PR

[Bug fortran/83436] Internal file cannot be accessed by UNFORMATTED data transfer when reading from /dev/urandom

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83436 --- Comment #3 from Jerry DeLisle --- Daan, Works for me here. It could be that the compiler is trying to use a wrong library version. Did you build gfortran yourself? What system are you running on?

[Bug fortran/83436] Internal file cannot be accessed by UNFORMATTED data transfer when reading from /dev/urandom

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83436 --- Comment #2 from Jerry DeLisle --- (In reply to Thomas Koenig from comment #1) > I can not check this right. Jerry, van you take a look? Looking

[Bug libfortran/78549] Very slow formatted internal file output

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78549 --- Comment #31 from Jerry DeLisle --- Author: jvdelisle Date: Thu Dec 14 02:30:49 2017 New Revision: 255621 URL: https://gcc.gnu.org/viewcvs?rev=255621=gcc=rev Log: 2017-12-12 Jerry DeLisle PR

[Bug libfortran/78549] Very slow formatted internal file output

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78549 --- Comment #30 from Jerry DeLisle --- Not quite fixed yet. I have found: ==17070== 88 bytes in 1 blocks are definitely lost in loss record 3 of 9 ==17070==at 0x4C31B25: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)

[Bug fortran/83282] missing comma in format changes output

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

[Bug libfortran/83168] FAIL: gfortran.dg/fmt_f0_2.f90 with a sanitized libgfortran

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

[Bug libfortran/83168] FAIL: gfortran.dg/fmt_f0_2.f90 with a sanitized libgfortran

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83168 --- Comment #9 from Jerry DeLisle --- Author: jvdelisle Date: Mon Dec 4 03:51:28 2017 New Revision: 255373 URL: https://gcc.gnu.org/viewcvs?rev=255373=gcc=rev Log: 2017-12-03 Jerry DeLisle Backport from trunk

[Bug libfortran/83168] FAIL: gfortran.dg/fmt_f0_2.f90 with a sanitized libgfortran

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83168 --- Comment #7 from Jerry DeLisle --- Should this be backported?

[Bug fortran/83191] [7/8 Regression] Writing a namelist with repeated complex numbers

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

[Bug fortran/83191] [7/8 Regression] Writing a namelist with repeated complex numbers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83191 --- Comment #7 from Jerry DeLisle --- Author: jvdelisle Date: Sun Dec 3 20:43:59 2017 New Revision: 255368 URL: https://gcc.gnu.org/viewcvs?rev=255368=gcc=rev Log: 2017-12-03 Jerry DeLisle Dominique

[Bug fortran/83191] [7/8 Regression] Writing a namelist with repeated complex numbers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83191 --- Comment #6 from Jerry DeLisle --- Author: jvdelisle Date: Sun Dec 3 16:47:12 2017 New Revision: 255365 URL: https://gcc.gnu.org/viewcvs?rev=255365=gcc=rev Log: 2017-12-03 Jerry DeLisle Dominique

[Bug fortran/83225] [8.0 regression] runtime error in transfer.c

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

[Bug fortran/83225] [8.0 regression] runtime error in transfer.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83225 --- Comment #5 from Jerry DeLisle --- Fixed on trunk and 7. Will leave open for a short while in case any further issues arise.

[Bug fortran/83225] [8.0 regression] runtime error in transfer.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83225 --- Comment #4 from Jerry DeLisle --- Author: jvdelisle Date: Sun Dec 3 05:05:51 2017 New Revision: 255364 URL: https://gcc.gnu.org/viewcvs?rev=255364=gcc=rev Log: 2017-12-02 Jerry DeLisle Backport from trunk

[Bug fortran/83225] [8.0 regression] runtime error in transfer.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83225 --- Comment #3 from Jerry DeLisle --- Author: jvdelisle Date: Sun Dec 3 03:26:09 2017 New Revision: 255362 URL: https://gcc.gnu.org/viewcvs?rev=255362=gcc=rev Log: 2017-12-02 Jerry DeLisle PR

[Bug fortran/83225] [8.0 regression] runtime error in transfer.c

at gcc dot gnu.org |jvdelisle at gcc dot gnu.org --- Comment #2 from Jerry DeLisle --- I will investigate.

[Bug libfortran/81937] stack-buffer-overflow on memcpy in libgfortran/io/unix.c on character(kind=4)

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

[Bug fortran/83191] [7/8 Regression] Writing a namelist with repeated complex numbers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83191 --- Comment #5 from Jerry DeLisle --- (In reply to Jerry DeLisle from comment #4) > Alternatively one could do this: > > @@ -1809,9 +1809,11 @@ write_complex (st_parameter_dt *dtp, const char > *source, int kind, size_t size) >

[Bug libfortran/83168] FAIL: gfortran.dg/fmt_f0_2.f90 with a sanitized libgfortran

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83168 --- Comment #6 from Jerry DeLisle --- Author: jvdelisle Date: Wed Nov 29 03:07:43 2017 New Revision: 255225 URL: https://gcc.gnu.org/viewcvs?rev=255225=gcc=rev Log: 2017-11-28 Jerry DeLisle PR

[Bug fortran/83191] [7/8 Regression] Writing a namelist with repeated complex numbers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83191 --- Comment #4 from Jerry DeLisle --- Alternatively one could do this: @@ -1809,9 +1809,11 @@ write_complex (st_parameter_dt *dtp, const char *source, int kind, size_t size) precision, buf_size, result1, _len1);

[Bug fortran/83191] [7/8 Regression] Writing a namelist with repeated complex numbers

at gcc dot gnu.org |jvdelisle at gcc dot gnu.org --- Comment #2 from Jerry DeLisle --- My bad. I will look into it.

[Bug libfortran/83168] FAIL: gfortran.dg/fmt_f0_2.f90 with a sanitized libgfortran

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83168 --- Comment #3 from Jerry DeLisle --- Thanks, Try this fix: diff --git a/libgfortran/io/write.c b/libgfortran/io/write.c index c9aad150..d26358c0 100644 --- a/libgfortran/io/write.c +++ b/libgfortran/io/write.c @@ -1552,7 +1552,7 @@

[Bug libfortran/83168] FAIL: gfortran.dg/fmt_f0_2.f90 with a sanitized libgfortran

||2017-11-26 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 --- I will look

[Bug fortran/83152] Possible run time error in derived type i/o

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

[Bug libfortran/78549] [8 Regression] Very slow formatted internal file output

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78549 --- Comment #27 from Jerry DeLisle --- This should be fixed now fairly well. At this point there are not a lot of major issues in our own libgfortran library. I will leave this bug report open for a while if any issues arise. Here is my latest

[Bug libfortran/78549] [8 Regression] Very slow formatted internal file output

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78549 --- Comment #26 from Jerry DeLisle --- Author: jvdelisle Date: Thu Nov 23 17:19:18 2017 New Revision: 255108 URL: https://gcc.gnu.org/viewcvs?rev=255108=gcc=rev Log: 2017-11-23 Jerry DeLisle Backport from

[Bug libfortran/78549] [8 Regression] Very slow formatted internal file output

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78549 --- Comment #25 from Jerry DeLisle --- Author: jvdelisle Date: Tue Nov 21 02:17:11 2017 New Revision: 254982 URL: https://gcc.gnu.org/viewcvs?rev=254982=gcc=rev Log: 2017-11-20 Jerry DeLisle PR

[Bug fortran/83057] OPEN(3f) without a filename and without STATUS='SCRATCH' does not produce a warning as being an extension on unassigned files

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

[Bug libfortran/78549] [8 Regression] Very slow formatted internal file output

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78549 --- Comment #24 from Jerry DeLisle --- After a minor test tweak. $ gfc -static pr78549.f $ time ./a.out real0m24.049s user0m22.941s sys 0m0.962s $ gfc6 -static pr78549.f $ time ./a.out real0m22.838s user0m22.718s sys

[Bug fortran/83021] [7 Regression] gfortran segfault

||jvdelisle at gcc dot gnu.org --- Comment #4 from Jerry DeLisle --- (In reply to Dominique d'Humieres from comment #3) > > > Could you please provide the file(s) needed to generate > > > local_field_module.mod? > > > > I suspect the sourc

[Bug fortran/25829] [F03] Asynchronous IO support

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25829 --- Comment #33 from Jerry DeLisle --- (In reply to Janne Blomqvist from comment #32) > Interestingly, Linux 4.14 contains a way to avoid a context switch to a > threadpool in case the data is already in the page cache: >

[Bug libfortran/78549] [8 Regression] Very slow formatted internal file output

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78549 --- Comment #23 from Jerry DeLisle --- Well, instrumenting a little bit I see that delete_root is getting called many many many times. So, every call to newunit_alloc is assigning a new unit number which is getting added to the treap and never

[Bug fortran/82865] Option -fdec collides with PDT

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82865 --- Comment #4 from Jerry DeLisle --- I would be OK with a hard error. If so, we need to think about any other similir situations with other modern fortran features. Then we get into a game of chasing more rabits. Perhaps best to document and

[Bug fortran/25829] [F03] Asynchronous IO support

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

[Bug fortran/82866] [PDT] ICE in resolve_fl_derived0, at fortran/resolve.c:14004

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

[Bug fortran/82865] Option -fdec collides with PDT

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

[Bug libfortran/80850] Sourced allocate() fails to allocate a pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80850 --- Comment #15 from Jerry DeLisle --- (In reply to Paul Thomas from comment #14) > PS If I remove the STAT= from the allocate, the code runs just fine in DEV > mode. > > Paul I have not looke at this one. Have you tried with valgrind or

[Bug libfortran/81938] valgrind error message and heap-buffer-overflow on address sanitized libgfortran.so

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81938 --- Comment #9 from Jerry DeLisle --- I think this can be closed now.

[Bug libfortran/81938] valgrind error message and heap-buffer-overflow on address sanitized libgfortran.so

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81938 --- Comment #8 from Jerry DeLisle --- Author: jvdelisle Date: Fri Oct 27 18:51:35 2017 New Revision: 254169 URL: https://gcc.gnu.org/viewcvs?rev=254169=gcc=rev Log: 2017-10-27 Jerry DeLisle Rimvydas (RJ)

[Bug libfortran/81938] valgrind error message and heap-buffer-overflow on address sanitized libgfortran.so

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81938 --- Comment #7 from Jerry DeLisle --- Author: jvdelisle Date: Fri Oct 27 17:50:22 2017 New Revision: 254163 URL: https://gcc.gnu.org/viewcvs?rev=254163=gcc=rev Log: 2017-10-27 Jerry DeLisle Rimvydas (RJ)

[Bug fortran/29600] [F03] MINLOC and MAXLOC take an optional KIND argument

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

[Bug libfortran/81938] valgrind error message and heap-buffer-overflow on address sanitized libgfortran.so

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

[Bug fortran/57096] Allocatable variable is not behaved as expected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57096 --- Comment #15 from Jerry DeLisle --- (In reply to Dominique d'Humieres from comment #6) > I get > > gA%next(): 2 > gA%next(): 4 > gA%next(): 6 > > gAp%next(): 2 > gAp%next(): 4 >

[Bug fortran/57096] Allocatable variable is not behaved as expected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57096 --- Comment #14 from Jerry DeLisle --- The reduced test case with gfortran 7.2.1 O get: $ ./test 1 1 0 1 and the original: $ ./test gA%next(): 0 gA%next(): 0 gA%next():

[Bug fortran/57096] Allocatable variable is not behaved as expected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57096 --- Comment #11 from Jerry DeLisle --- (In reply to janus from comment #8) > (In reply to Jerry DeLisle from comment #7) > > Let's close this one. > > Please don't. I still see the wrong output with gfortran 7.2. > > Dominique, did you

[Bug fortran/57096] Allocatable variable is not behaved as expected

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

[Bug libfortran/82233] [6/7/8 Regression] execute_command_line causes program to stop when command fails (or does not exist)

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

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