http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50174
Bug #: 50174
Summary: internal compiler error: derived type allocation
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
P
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50163
Bug #: 50163
Summary: Internal compiler error: initialization expression
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: minor
--- Comment #1 from pmason at ricardo dot com 2010-09-02 10:42 ---
Created an attachment (id=21654)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21654&action=view)
Small testcase that causes ICE.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45495
specifier
dependent on non-present arg.
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: critical
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: pmason at ricard
real, allocatable :: locks(:)
end module fred2
program fred
use fred1
use fred2
end program fred
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Compiled as:
gfortran -c test.f90
--
>>>>
Using version 4.3.0 20080117 (experimental) on x86-64 suse9.
--
Summary: Libgfortran.a (downloaded) is not PIC compiled...
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libfortr
rtran test.f90" on suse9 (64-bit) box
using 4.3.0 20070706 (experimental). I can understand INQUIRE
by FILE can be difficult to determine, but not by UNIT.
--
Summary: INQUIRE (by UNIT) for (un)formatted always returns
YES...
Product: gcc
Version:
--- Comment #5 from pmason at ricardo dot com 2007-02-22 12:40 ---
Get same problem with equivalent P/E format:
write(6,'(1pe6.0)') 1.0e-1
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30910
normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: pmason at ricardo dot com
GCC build triplet: 4.3.0 20070221 (experimental)
GCC host triplet: suse9 x86_64
GCC target triplet: x86_64-unknown-linux-gnu
http://gcc.gn
--- Comment #2 from pmason at ricardo dot com 2006-12-11 13:05 ---
Write statement (fortran90) fails to ignore zero-sized array when
bounds on array are variable. Please see zeros.f90 file attached.
This was compiled as "gfortran zeros.f90" on suse9 (x86_64) box
using ver
--- Comment #1 from pmason at ricardo dot com 2006-12-11 12:58 ---
Created an attachment (id=12780)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12780&action=view)
Fortran 90 testcase for zero-sized array printing.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30145
--
Summary: Print/write
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: pmason at ricardo dot com
;<<<<<<<<<<<<<
Compiled on suse 9 box as "gfortran test.f90" using
version 4.2.0 20061015 (experimental).
--
Summary: internal compiler error: in fold_binary, at fold-
const.c:8239
Product: gcc
Version: 4.2.0
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: pmason at ricardo dot com
GCC build triplet: gcc version 4.2.0 20061012 (experimental)
GCC host triplet: suse 9
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29451
14 matches
Mail list logo
