[Bug libfortran/56737] New: Bizarre Hollerith edit descriptor errors (valgrind shows uninitialized value in libgfortran)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56737 Bug #: 56737 Summary: Bizarre Hollerith edit descriptor errors (valgrind shows uninitialized value in libgfortran) Classification: Unclassified Product: gcc Version:

[Bug libfortran/56810] New: record-repeat fails kind check on complex read

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56810 Bug #: 56810 Summary: record-repeat fails kind check on complex read Classification: Unclassified Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal

[Bug libfortran/56737] [4.6/4.7/4.8/4.9 Regression] Wrong I/O result with format cache for Hollerith strings

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56737 --- Comment #12 from Jonathan Hogg jonathan.hogg at stfc dot ac.uk 2013-04-04 10:43:02 UTC --- Thanks for fixing this. The code in question has been moved to use 'strings' rather than Hollerith i/o - we aim for it to be F95 compliant anyway

[Bug fortran/54159] New: Fortran quad precision rounding seemingly nonsensical

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54159 Bug #: 54159 Summary: Fortran quad precision rounding seemingly nonsensical Classification: Unclassified Product: gcc Version: 4.6.3 Status: UNCONFIRMED Severity: normal

[Bug fortran/54159] Fortran quad precision rounding seemingly nonsensical

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54159 --- Comment #4 from Jonathan Hogg jonathan.hogg at stfc dot ac.uk 2012-08-02 11:37:17 UTC --- I can confirm that if we fiddle the fp rounding mode using a bit of C (very similar to the one you just suggested) then the problem goes away

[Bug c++/63489] New: stack allocated array pointer corrupted

++ Assignee: unassigned at gcc dot gnu.org Reporter: jonathan.hogg at stfc dot ac.uk Created attachment 33667 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=33667action=edit test case The attached code, when compiled as g++ -g -O2 testcase.cxx -o testcase ./testcase and run

[Bug c++/63489] stack allocated array pointer corrupted

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63489 --- Comment #3 from Jonathan Hogg jonathan.hogg at stfc dot ac.uk --- Confirmed, this is the cause is the larger example as well. I had missed the introduction of -fsanitize=address, useful feature. I'd assumed something like that valgrind would

[Bug fortran/60500] New: Spurious warning on derived type initialization

: fortran Assignee: unassigned at gcc dot gnu.org Reporter: jonathan.hogg at stfc dot ac.uk The following code: module spurious_warning implicit none type :: ntype integer :: level = 1 end type ntype contains subroutine sub1(n1, n2, st) integer, intent

[Bug fortran/51639] New: Nested type pointer null initialisation fails

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51639 Bug #: 51639 Summary: Nested type pointer null initialisation fails Classification: Unclassified Product: gcc Version: 4.6.1 Status: UNCONFIRMED Severity: normal

[Bug fortran/50790] New: ICE in copy_constant on divide by expression that evaluates to zero

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50790 Bug #: 50790 Summary: ICE in copy_constant on divide by expression that evaluates to zero Classification: Unclassified Product: gcc Version: 4.6.1 Status:

[Bug fortran/71798] New: failure to finalise fortran temporary

Assignee: unassigned at gcc dot gnu.org Reporter: jonathan.hogg at stfc dot ac.uk Target Milestone: --- Created attachment 38855 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38855=edit test case Compiling and running the attached code we get: $ gfortran-6