[Bug fortran/60356] New: Compiler segfault instead of error about module procedure / procedure with an explicit interface

2014-02-27 Thread mvondomaros at gmail dot com
Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: mvondomaros at gmail dot com Hi! The attached simple module causes a f951: internal compiler error: Segmentation fault. When I comment out the generic

[Bug fortran/60356] Compiler segfault instead of error about module procedure / procedure with an explicit interface

2014-02-27 Thread mvondomaros at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60356 --- Comment #1 from Mike mvondomaros at gmail dot com --- Created attachment 32223 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=32223action=edit example that causes the segfault

[Bug fortran/60289] allocating class(*) pointer as character gives type-spec requires the same character-length parameter

2014-02-27 Thread mvondomaros at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60289 Mike mvondomaros at gmail dot com changed: What|Removed |Added CC||mvondomaros at gmail

[Bug fortran/59700] New: Misleading/buggy runtime error message: Bad integer for item 0 in list input

2014-01-06 Thread mvondomaros at gmail dot com
: minor Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: mvondomaros at gmail dot com The following simple program yields: Fortran runtime error: Bad integer for item 0 in list input But unless my understanding of an item