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

[mvondomaros at gmail dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59700

Bug ID: 59700
   Summary: Misleading/buggy runtime error message: Bad integer
for item 0 in list input
   Product: gcc
   Version: 4.8.2
Status: UNCONFIRMED
  Severity: 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 in the list input is wrong, I would have
expected:
> Fortran runtime error: Bad integer for item 4 in list input

program foo

integer :: myunit
integer :: i1, i2, i3, i4

open(newunit=myunit, file="test.dat")
read(myunit, *) i1, i2, i3, i4
close(myunit)
end program foo

file test.dat:
1 2 3 4.0

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

[mvondomaros at gmail dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60356

Bug ID: 60356
   Summary: Compiler segfault instead of error about module
procedure / procedure with an explicit interface
   Product: gcc
   Version: 4.8.2
Status: UNCONFIRMED
  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 statement as indicated in the code, I get the
expected error message: "Error: 'my_method1_sub' must be a module procedure or
an external procedure with an explicit interface at (1)"

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

[mvondomaros at gmail dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60356

--- Comment #1 from Mike  ---
Created attachment 32223
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32223&action=edit
example that causes the segfault

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

[mvondomaros at gmail dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60289

Mike  changed:

   What|Removed |Added

 CC||mvondomaros at gmail dot com

--- Comment #3 from Mike  ---
Same problem in 4.8.2