[Bug fortran/68649] [6 Regression] note: code may be misoptimized unless -fno-strict-aliasing is used

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

[Bug fortran/30802] out of bounds error array I/O not picked up with -fbounds-check

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30802 --- Comment #6 from Jerry DeLisle --- Intentionally not in the library for efficiency. However we can build in some runtime checks with -fcheck=. This one is on my radar and I was just looking at it a few days ago. Not taking assignment yet.

[Bug fortran/31190] minimum field width list-directed output

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

[Bug fortran/20896] ambiguous interface not detected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20896 Jerry DeLisle changed: What|Removed |Added Resolution|FIXED |DUPLICATE --- Comment #17 from Jerry

[Bug fortran/52251] Nonadvancing I/O and the t edit descriptor

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

[Bug fortran/39290] Subroutine/function ambiguity in generics

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39290 Jerry DeLisle changed: What|Removed |Added CC||Joost.VandeVondele at mat dot ethz

[Bug fortran/29670] [meta-bug] fortran interfaces

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29670 Bug 29670 depends on bug 20896, which changed state. Bug 20896 Summary: ambiguous interface not detected https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20896 What|Removed |Added

[Bug fortran/20896] ambiguous interface not detected

||jvdelisle at gcc dot gnu.org Resolution|--- |FIXED --- Comment #16 from Jerry DeLisle --- Closing, probably a dupe of another wont fix. Also very stale by now.

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68600 --- Comment #8 from Jerry DeLisle --- Created attachment 36887 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36887=edit A faster version I took the example code found in http://wiki.cs.utexas.edu/rvdg/HowToOptimizeGemm/ where the

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

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

[Bug libfortran/51119] MATMUL slow for large matrices

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51119 --- Comment #30 from Jerry DeLisle --- (In reply to Joost VandeVondele from comment #29) > These slides show how to reach 90% of peak: > http://wiki.cs.utexas.edu/rvdg/HowToOptimizeGemm/ > the code actually is not too ugly, and I think there is

[Bug libfortran/51119] MATMUL slow for large matrices

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51119 --- Comment #28 from Jerry DeLisle --- (In reply to Janne Blomqvist from comment #25) > > But, that is not particularly impressive, is it? I don't know about current > low end graphics adapters, but at least the high end GPU cards (Tesla) are

[Bug fortran/52251] Nonadvancing I/O and the t edit descriptor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52251 --- Comment #8 from Jerry DeLisle --- Fixed on trunk. Should we backport to 5 branch?

[Bug libfortran/51119] MATMUL slow for large matrices

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51119 --- Comment #24 from Jerry DeLisle --- (In reply to Jerry DeLisle from comment #16) > For what its worth: > > $ gfc pr51119.f90 -lblas -fno-external-blas -Ofast -march=native > $ ./a.out > Time, MATMUL:21.2483196 21.25444964601

[Bug libfortran/51119] MATMUL slow for large matrices

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51119 --- Comment #23 from Jerry DeLisle --- (In reply to Thomas Koenig from comment #21) > > Hidden behind a -fexternal-blas-n switch might be an option. Including GPUs > > seems even a tad more tricky. We have a paper on GPU (small) matrix > >

[Bug libfortran/51119] MATMUL slow for large matrices

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51119 --- Comment #19 from Jerry DeLisle --- If I can get something working I am thinking something like -fexternal-blas-n, if -n not given then default to current libblas behaviour. This way users have some control. With GPUs, it is not unusual to

[Bug fortran/52251] Nonadvancing I/O and the t edit descriptor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52251 --- Comment #7 from Jerry DeLisle --- Author: jvdelisle Date: Mon Nov 23 00:40:51 2015 New Revision: 230734 URL: https://gcc.gnu.org/viewcvs?rev=230734=gcc=rev Log: 2015-11-22 Jerry DeLisle PR libfortran/52251

[Bug fortran/48298] [F03] User-Defined Derived-Type IO (DTIO)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48298 --- Comment #14 from Jerry DeLisle --- Created attachment 36805 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36805=edit Expanded test case Attached is an expanded test case. Could someone review and confirm this is valid. I need to

[Bug libfortran/51119] MATMUL slow for large matrices

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51119 --- Comment #17 from Jerry DeLisle --- I have done some experimenting. Since gcc supports OMP and I think to some extent ACC why not come up with a MATMUL that exploits these if present? On the darwin platform discussed in comment #12, the

[Bug fortran/68458] internal compiler error: Segmentation fault

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

[Bug libfortran/51119] MATMUL slow for large matrices

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

[Bug fortran/65089] FAIL: gfortran.dg/io_real_boz(2|_[45]).f90 when tested with -fsanitize=address

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

[Bug fortran/65089] FAIL: gfortran.dg/io_real_boz(2|_[45]).f90 when tested with -fsanitize=address

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65089 --- Comment #17 from Jerry DeLisle --- Author: jvdelisle Date: Sat Nov 7 18:13:17 2015 New Revision: 229935 URL: https://gcc.gnu.org/viewcvs?rev=229935=gcc=rev Log: 2015-11-07 Jerry DeLisle Backport from trunk

[Bug fortran/42568] [Cygwin] BLOCKDATA referenced in EXTERNAL not loading from library

||jvdelisle at gcc dot gnu.org Resolution|FIXED |--- --- Comment #29 from Jerry DeLisle --- I happened to just get Cygwin installed and running on my Windows box. Let me run some tests and see if I can understand this.

[Bug fortran/48298] [F03] User-Defined Derived-Type IO (DTIO)

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

[Bug fortran/67367] Program crashes on READ(IOSTAT=IOS, ...) on directory OPEN()ed without error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67367 Jerry DeLisle jvdelisle at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug fortran/37355] Request runtime preconnected buffer option for gfortran

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37355 Jerry DeLisle jvdelisle at gcc dot gnu.org changed: What|Removed |Added Status|WAITING |RESOLVED

[Bug fortran/67367] Program crashes on READ(IOSTAT=IOS, ...) on directory OPEN()ed without error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67367 --- Comment #7 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Author: jvdelisle Date: Sat Aug 29 15:38:39 2015 New Revision: 227320 URL: https://gcc.gnu.org/viewcvs?rev=227320root=gccview=rev Log: 2015-08-29 Jerry DeLisle jvdeli

[Bug fortran/67367] Program crashes on READ(IOSTAT=IOS, ...) on directory OPEN()ed without error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67367 --- Comment #8 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Author: jvdelisle Date: Sat Aug 29 15:52:43 2015 New Revision: 227321 URL: https://gcc.gnu.org/viewcvs?rev=227321root=gccview=rev Log: 2015-08-29 Jerry DeLisle jvdeli

[Bug fortran/67367] Program crashes on READ(IOSTAT=IOS, ...) on directory OPEN()ed without error

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

[Bug fortran/67367] Program crashes on READ(IOSTAT=IOS, ...) on directory OPEN()ed without error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67367 --- Comment #5 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Created attachment 36265 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=36265action=edit A preliminary patch - not final This patch catches the segfault and we end up

[Bug fortran/67367] Program crashes on READ(IOSTAT=IOS, ...) on directory OPEN()ed without error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67367 --- Comment #6 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Created attachment 36266 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=36266action=edit Better than preliminary This patch returns the correct code from raw_read and we get

[Bug fortran/67367] Program crashes on READ(IOSTAT=IOS, ...) on directory OPEN()ed without error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67367 Jerry DeLisle jvdelisle at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Last

[Bug fortran/52251] Nonadvancing I/O and the t edit descriptor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52251 --- Comment #6 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Created attachment 35911 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=35911action=edit A patch to fix this. This patch issues the tab spacing based on spaces previously

[Bug fortran/66643] Missing compilation error for formatted data transfer without format

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

[Bug fortran/66499] Letters with accents change format behavior for X and T descriptors.

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

[Bug fortran/66331] gfortran.dg/continuation_13.f90 execution failure

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66331 Jerry DeLisle jvdelisle at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66310 --- Comment #4 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- (In reply to Gerhard Steinmetz from comment #3) I do agree, that some extra temporary data is necessary and there should be a practical (high) limit for something like

[Bug fortran/66331] gfortran.dg/continuation_13.f90 execution failure

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66331 --- Comment #2 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- See PR 65903

[Bug fortran/66331] gfortran.dg/continuation_13.f90 execution failure

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

[Bug fortran/66311] [5 Regression] Problems with some integer(16) values

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66311 Jerry DeLisle jvdelisle at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Last

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

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

[Bug fortran/65903] [5/6 Regression] Line continuation followed by comment character in string fails to compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65903 Jerry DeLisle jvdelisle at gcc dot gnu.org changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug fortran/65903] [5/6 Regression] Line continuation followed by comment character in string fails to compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65903 --- Comment #8 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Author: jvdelisle Date: Wed May 20 01:50:34 2015 New Revision: 223428 URL: https://gcc.gnu.org/viewcvs?rev=223428root=gccview=rev Log: 2015-05-19 Jerry DeLisle jvdeli

[Bug fortran/65903] [5/6 Regression] Line continuation followed by comment character in string fails to compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65903 --- Comment #9 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Author: jvdelisle Date: Wed May 20 01:51:50 2015 New Revision: 223429 URL: https://gcc.gnu.org/viewcvs?rev=223429root=gccview=rev Log: 2015-05-19 Jerry DeLisle jvdeli

[Bug fortran/65903] [5/6 Regression] Line continuation followed by comment character in string fails to compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65903 --- Comment #7 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Author: jvdelisle Date: Sat May 16 17:51:41 2015 New Revision: 223249 URL: https://gcc.gnu.org/viewcvs?rev=223249root=gccview=rev Log: 2015-05-16 Jerry DeLisle jvdeli

[Bug fortran/65903] [5/6 Regression] Line continuation followed by comment character in string fails to compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65903 --- Comment #6 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Author: jvdelisle Date: Sat May 16 17:44:15 2015 New Revision: 223248 URL: https://gcc.gnu.org/viewcvs?rev=223248root=gccview=rev Log: 2015-05-16 Jerry DeLisle jvdeli

[Bug fortran/65903] [5/6 Regression] Line continuation followed by comment character in string fails to compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65903 --- Comment #5 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- (In reply to Laurent Chardon from comment #4) Thanks for the fix. If I may suggest a modification of the testcase in order to check also when there are no blanks between

[Bug fortran/65903] [5/6 Regression] Line continuation followed by comment character in string fails to compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65903 --- Comment #3 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Possible path here: https://gcc.gnu.org/ml/fortran/2015-05/msg00071.html

[Bug fortran/65903] [5/6 Regression] Line continuation followed by comment character in string fails to compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65903 Jerry DeLisle jvdelisle at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED

[Bug libfortran/48852] Invalid spaces in list-directed output of complex constants

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48852 --- Comment #14 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- I have decided that to do this right I need to revamp how write_float.def and associated functions are organized. We have discussed doing this quite a while ago, so now

[Bug fortran/65903] Line continuation followed by comment character in string fails to compile

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

[Bug libfortran/48852] Invalid spaces in list-directed output of complex constants

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48852 --- Comment #13 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- (In reply to Thomas Henlich from comment #12) --- snip --- There is also case C (right-flush in 2*w+3): --- snip --- Oh yes, Thanks Thomas. I now see you mentioned

[Bug libfortran/48852] Invalid spaces in list-directed output of complex constants

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48852 --- Comment #10 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- gfortran currently does this with default formatting, list directed outout: - ( 1., 0.) ( -1.0002E-25, 0.

[Bug libfortran/48852] Invalid spaces in list-directed output of complex constants

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48852 --- Comment #11 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- IFORT does this: - (1.00,0.000E+00) (-1.000E-25,0.000E+00) (-1.000E-25,0.000E+00) (1.00,0.000E+00

[Bug fortran/52251] Nonadvancing I/O and the t edit descriptor

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

[Bug libquadmath/65757] gfortran gives incorrect result for anint with real*16 argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65757 --- Comment #6 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- I am thinking its not working, but maybe I do not understand the function. I created a loop like this (with the patch): q1 = 233181505644407.q0 q2 = anint

[Bug libquadmath/65757] gfortran gives incorrect result for anint with real*16 argument

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

[Bug libfortran/65234] Output descriptor (*(1E15.7)) not accepted

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65234 --- Comment #7 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Author: jvdelisle Date: Tue Apr 21 18:28:39 2015 New Revision: 76 URL: https://gcc.gnu.org/viewcvs?rev=76root=gccview=rev Log: 2015-04-21 Jerry DeLisle jvdeli

[Bug libfortran/65234] Output descriptor (*(1E15.7)) not accepted

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65234 Jerry DeLisle jvdelisle at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug libfortran/65234] Output descriptor (*(1E15.7)) not accepted

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65234 --- Comment #6 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Author: jvdelisle Date: Tue Apr 21 18:23:20 2015 New Revision: 74 URL: https://gcc.gnu.org/viewcvs?rev=74root=gccview=rev Log: 2015-04-21 Jerry DeLisle jvdeli

[Bug fortran/65684] Wrong error message when writing to a string

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65684 Jerry DeLisle jvdelisle at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug libfortran/48852] Invalid spaces in list-directed output of complex constants

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

[Bug fortran/56743] Namelist bug with comment and no blank

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56743 --- Comment #8 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Author: jvdelisle Date: Tue Apr 21 16:13:54 2015 New Revision: 71 URL: https://gcc.gnu.org/viewcvs?rev=71root=gccview=rev Log: 2015-04-21 Jerry DeLisle jvdeli

[Bug fortran/56743] Namelist bug with comment and no blank

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56743 --- Comment #9 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Author: jvdelisle Date: Tue Apr 21 16:33:27 2015 New Revision: 72 URL: https://gcc.gnu.org/viewcvs?rev=72root=gccview=rev Log: 2015-04-21 Jerry DeLisle jvdeli

[Bug fortran/56743] Namelist bug with comment and no blank

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56743 Jerry DeLisle jvdelisle at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug fortran/56744] [meta-bug] Namelist bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56744 Bug 56744 depends on bug 56743, which changed state. Bug 56743 Summary: Namelist bug with comment and no blank https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56743 What|Removed |Added

[Bug target/65810] powerpc64 libgfortran alignment issue?

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

[Bug fortran/64921] [4.9/5/6 Regression] FAIL: gfortran.dg/class_allocate_18.f90

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

[Bug fortran/56743] Namelist bug with comment and no blank

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56743 --- Comment #7 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Potential simple patch. Index: io/list_read.c === --- io/list_read.c(revision 222110) +++ io/list_read.c

[Bug fortran/65766] gFortran Compiler SEGFAULTING on compiling simple program

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65766 Jerry DeLisle jvdelisle at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Last

[Bug fortran/65089] FAIL: gfortran.dg/io_real_boz(2|_[45]).f90 when tested with -fsanitize=address

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65089 --- Comment #15 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Fixed on trunk. It would be good to backport to 5.2 and probably 4.9.x

[Bug fortran/65089] FAIL: gfortran.dg/io_real_boz(2|_[45]).f90 when tested with -fsanitize=address

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65089 --- Comment #14 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Author: jvdelisle Date: Wed Apr 15 01:27:03 2015 New Revision: 222111 URL: https://gcc.gnu.org/viewcvs?rev=222111root=gccview=rev Log: 2015-04-14 Jerry DeLisle jvdeli

[Bug fortran/65089] FAIL: gfortran.dg/io_real_boz(2|_[45]).f90 when tested with -fsanitize=address

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65089 --- Comment #12 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Created attachment 35302 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=35302action=edit Preliminary patch - needs testing This patch resolves the -fsanitize=address issue

[Bug fortran/65684] Wrong error message when writing to a string

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65684 --- Comment #12 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- I have another idea in mind, however I see what your aiming for. I sense some frustration over personal preferences and wording and such. There is no rush here, since we have

[Bug fortran/65089] FAIL: gfortran.dg/io_real_boz(2|_[45]).f90 when tested with -fsanitize=address

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65089 --- Comment #11 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- (In reply to Jakub Jelinek from comment #9) (In reply to Jerry DeLisle from comment #8) True, fortran strings are not generally NULL terminated. However, for internal

[Bug fortran/65089] FAIL: gfortran.dg/io_real_boz(2|_[45]).f90 when tested with -fsanitize=address

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65089 --- Comment #8 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- True, fortran strings are not generally NULL terminated. However, for internal representation between Frontend and library we try to do so for safety. Evidently missed one

[Bug fortran/59016] f951: internal compiler error: Segmentation fault

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

[Bug fortran/65684] Wrong error message when writing to a string

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

[Bug fortran/56743] Namelist bug with comment and no blank

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

[Bug fortran/65089] FAIL: gfortran.dg/io_real_boz(2|_[45]).f90 when tested with -fsanitize=address

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

[Bug fortran/65089] FAIL: gfortran.dg/io_real_boz(2|_[45]).f90 when tested with -fsanitize=address

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65089 --- Comment #4 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- The patch eliminates the issue for all three of the BOZ cases. What I do not understand is why passing the pointer p to strlen causes a problem.

[Bug fortran/65541] [5 Regression] namelist regression

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65541 --- Comment #9 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- (In reply to John from comment #8) Hi, It seems that some testing was required after all. With the latest gcc snapshot from Debian (20150329-1) I still get the same output

[Bug fortran/65541] [5 Regression] namelist regression

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65541 --- Comment #10 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- For the record, my results with trunk: $ gfc pr65541.f90 $ ./a.out $ cat some.dat SOME A%T2%T1%I= 0, A%T2%J= 0, A%K= 0, /

[Bug libfortran/59513] [4.8/4.9/5 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513 --- Comment #32 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Author: jvdelisle Date: Mon Mar 30 16:51:37 2015 New Revision: 221772 URL: https://gcc.gnu.org/viewcvs?rev=221772root=gccview=rev Log: 2015-03-30 Jerry DeLisle jvdeli

[Bug libfortran/59513] [4.8/4.9/5 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513 Jerry DeLisle jvdelisle at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug libfortran/59513] [4.8/4.9/5 Regression] Fortran runtime error: Sequential READ or WRITE not allowed after EOF marker, possibly use REWIND or BACKSPACE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59513 --- Comment #33 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Author: jvdelisle Date: Mon Mar 30 20:47:40 2015 New Revision: 221778 URL: https://gcc.gnu.org/viewcvs?rev=221778root=gccview=rev Log: 2015-03-30 Jerry DeLisle jvdeli

[Bug fortran/65596] [4.9,5.0 Regression] NAMELIST bug with f2003: reads too far

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65596 --- Comment #5 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Author: jvdelisle Date: Sat Mar 28 13:27:58 2015 New Revision: 221753 URL: https://gcc.gnu.org/viewcvs?rev=221753root=gccview=rev Log: 2015-03-28 Jerry DeLisle jvdeli

[Bug fortran/65596] [4.9,5.0 Regression] NAMELIST bug with f2003: reads too far

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65596 --- Comment #6 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Author: jvdelisle Date: Sat Mar 28 14:08:18 2015 New Revision: 221754 URL: https://gcc.gnu.org/viewcvs?rev=221754root=gccview=rev Log: 2015-03-28 Jerry DeLisle jvdeli

[Bug fortran/65596] [4.9,5.0 Regression] NAMELIST bug with f2003: reads too far

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65596 --- Comment #7 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Author: jvdelisle Date: Sat Mar 28 14:22:53 2015 New Revision: 221755 URL: https://gcc.gnu.org/viewcvs?rev=221755root=gccview=rev Log: 2015-03-28 Jerry DeLisle jvdeli

[Bug fortran/65596] [4.9,5.0 Regression] NAMELIST bug with f2003: reads too far

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65596 --- Comment #8 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Author: jvdelisle Date: Sat Mar 28 14:25:29 2015 New Revision: 221756 URL: https://gcc.gnu.org/viewcvs?rev=221756root=gccview=rev Log: 2015-03-28 Jerry DeLisle jvdeli

[Bug fortran/65596] [4.9,5.0 Regression] NAMELIST bug with f2003: reads too far

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65596 Jerry DeLisle jvdelisle at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug libfortran/65563] Segfault on reopening fort.xxx file with explicit name

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

[Bug fortran/65596] [4.9 Regression] NAMELIST bug with f2003: reads too far

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

[Bug libfortran/65605] New: [4.9 Regression] Namelist mishandles delim

: libfortran Assignee: jvdelisle at gcc dot gnu.org Reporter: jvdelisle at gcc dot gnu.org Reported to me off list. This is related to pr60148. It is fixed on trunk by the fix to pr63460 which did get backported to 4.9. The fix to pr60148 probably needs to be backported to 4.9

[Bug fortran/65596] [4.9 Regression] NAMELIST bug with f2003: reads too far

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65596 --- Comment #2 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- *** Bug 65605 has been marked as a duplicate of this bug. ***

[Bug libfortran/65605] [4.9 Regression] Namelist mishandles delim

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65605 Jerry DeLisle jvdelisle at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug fortran/65596] [4.9,5.0 Regression] NAMELIST bug with f2003: reads too far

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65596 Jerry DeLisle jvdelisle at gcc dot gnu.org changed: What|Removed |Added Summary|[4.9 Regression] NAMELIST |[4.9,5.0

[Bug libfortran/65563] Segfault on reopening fort.xxx file with explicit name

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

[Bug fortran/65541] [5 Regression] namelist regression

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65541 --- Comment #6 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Author: jvdelisle Date: Thu Mar 26 02:44:34 2015 New Revision: 221682 URL: https://gcc.gnu.org/viewcvs?rev=221682root=gccview=rev Log: 2015-03-25 Jerry DeLisle jvdeli

<    8   9   10   11   12   13   14   15   16   17   >