[Bug fortran/110081] New: Unhelpful error message: "(null):0: confused by earlier errors, bailing out"

Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: andrew at fluidgravity dot co.uk Target Milestone: --- The following code compiles with neither gfortran-11 nor gfortran-12, but does compile with g

[Bug fortran/89890] Memory leak from a function returning a subtype

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89890 Andrew Wood changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE

[Bug fortran/89890] Memory leak from a function returning a subtype

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89890 --- Comment #1 from Andrew Wood --- If I add the line "INTEGER, ALLOCATABLE :: i(:)" inside the definition of 'base', then valgrind reports the lost memory as having been allocated at the second ALLOCATE statement in the function 'new' instead

[Bug fortran/89890] New: Memory leak from a function returning a subtype

: fortran Assignee: unassigned at gcc dot gnu.org Reporter: andrew at fluidgravity dot co.uk Target Milestone: --- I get a memory leak from the code below. The leak does not occur with either the Intel or PGI Fortran compilers. The leak goes away if I change the return type

[Bug fortran/88143] New: gfortran crashes with an internal compiler error

: fortran Assignee: unassigned at gcc dot gnu.org Reporter: andrew at fluidgravity dot co.uk Target Milestone: --- I get an internal compiler error when compiling the code below: > gfortran -c code.f90 f951: internal compiler error: Segmentation fault: 11 libbacktrace co

[Bug fortran/88072] New: gfortran crashes with an internal compiler error

: fortran Assignee: unassigned at gcc dot gnu.org Reporter: andrew at fluidgravity dot co.uk Target Milestone: --- The code below contains an error or two, but instead of reporting a helpful error message, gfortran crashes with an internal compiler error and segfault

[Bug fortran/87270] New: "FINAL" subroutine is called when compiled with "gfortran -O1", but not "gfortran -O0"

Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: andrew at fluidgravity dot co.uk Target Milestone: --- Created attachment 44676 --> https://gcc.gnu.org/bugzilla/atta

[Bug fortran/87143] New: Uninitialized warnings when using automatic array allocation

Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: andrew at fluidgravity dot co.uk Target Milestone: --- I get the following warnings when compiling the code below: > gfortran -Wall -std=f2008 code.f90 code.f90:5:0: i = [0, 1

[Bug fortran/80524] [F03] Problematic behaviour with a finalization subroutine in gfortran

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80524 --- Comment #6 from Andrew Wood --- For info, the actual code I was developing did use the finalization subroutine to deallocate pointers, which resulted in seg faults when compiled with ifort. This was how I discovered the problem. I also

[Bug fortran/80524] Problematic behaviour with a finalization subroutine in gfortran

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80524 --- Comment #1 from Andrew Wood --- Intel's response: Hello Andrew, Our development team investigated the issue and determined the following: --- Finalization is a tricky thing - there are many different events that trigger

[Bug fortran/80524] New: Problematic behaviour with a finalization subroutine in gfortran

Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: andrew at fluidgravity dot co.uk Target Milestone: --- Created attachment 41268 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41268=edit Fortran code with a final

[Bug fortran/80121] New: Memory leak when allocating a component derived type in a recursive subroutine (gfortran)

Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: andrew at fluidgravity dot co.uk Target Milestone: --- Created attachment 41006 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41006=edit Fortran c

[Bug fortran/77385] New: "Unclassifiable statement" from gfortran

t: fortran Assignee: unassigned at gcc dot gnu.org Reporter: andrew at fluidgravity dot co.uk Target Milestone: --- Created attachment 39500 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39500=edit Fortran code that won't compile with gfortran I get the above