https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114535
--- Comment #3 from Andrew Benson ---
Thanks Paul. The workaround is very helpful and lets me continue making
progress in the rest of my work for now. Thanks again!
Assignee: unassigned at gcc dot gnu.org
Reporter: abensonca at gcc dot gnu.org
Target Milestone: ---
The following code (which must be in two files to trigger the error) causes an
ICE using the latest gfortran.
$ cat ice1.F90
module iv
type, public :: vs
contains
final
: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: abensonca at gcc dot gnu.org
Target Milestone: ---
The following shows a segfault at run time resulting from use of an optional
argument in a function with OpenMP tasks:
module taskerMod
type :: helper
end
: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: abensonca at gcc dot gnu.org
Target Milestone: ---
Here's an example code (highly simplified from the actual code I'm working
on) that causes seemingly wrong behavior resulting in calling a destructor when
it should
: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: abensonca at gcc dot gnu.org
Target Milestone: ---
The following code (compiled using current trunk), when run, causes a segfault,
and valgrind complains about an invalid read. The code appears correct to me,
and runs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105807
--- Comment #4 from Andrew Benson ---
A possibly related case:
module tm
type :: st
end type st
type :: resourceManager
class (*), pointer :: resource => null()
integer , pointer :: counter => null()
end type
: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: abensonca at gcc dot gnu.org
Target Milestone: ---
The following code seems to cause a memory leak when using nested OpenMP
parallelism when compiled and run with gfortran-12.
module nestedMod
type :: n
integer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93473
Andrew Benson changed:
What|Removed |Added
CC||abensonca at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96122
--- Comment #2 from Andrew Benson ---
(In reply to Dominique d'Humieres from comment #1)
> Confirmed. For me it segfaults from GCC7 up to GCC11.
Interesting. This started occurring for me when I updated from GCC10.1 to 11.
But, the code I
Assignee: unassigned at gcc dot gnu.org
Reporter: abensonca at gcc dot gnu.org
Target Milestone: ---
The following code segfaults with gfortran 11.0.0:
module a
type vs
character(len=1), dimension(:), allocatable :: ch
contains
final :: vsf
end type vs
type mtd
iority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: abensonca at gcc dot gnu.org
Target Milestone: ---
The following causes a bogus "type mismatch" error with the current trunk
(e899d4b71255b9ae096a7ecd31a61fc76f200019):
$ cat file1.F90
module
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93486
Andrew Benson changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
||abensonca at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #11 from Andrew Benson ---
Fixed by https://gcc.gnu.org/g:7848054c68bad6e2aa40cb59f77cc99bd8448d52
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89943
Bug 89943 depends on bug 83113, which changed state.
Bug 83113 Summary: Bogus "duplicate allocatable attribute" error for submodule
character function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83113
What|Removed
14 matches
Mail list logo
