public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/56730] New: [Fortran 4.6, 4.7] ICE on (wrongly) referencing polymorphic array in allocate
@ 2013-03-25 21:23 tiloschwarz at gcc dot gnu.org
2013-03-26 9:43 ` [Bug fortran/56730] " janus at gcc dot gnu.org
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: tiloschwarz at gcc dot gnu.org @ 2013-03-25 21:23 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56730
Bug #: 56730
Summary: [Fortran 4.6, 4.7] ICE on (wrongly) referencing
polymorphic array in allocate
Classification: Unclassified
Product: gcc
Version: 4.7.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: tiloschwarz@gcc.gnu.org
Current 4.8-branch and 4.9-trunk do not ICE.
% cat polymorph1.f08
program polymorph1
type ta
integer i
end type ta
type, extends(ta) :: tb
integer j
end type tb
type ca
class(ta), allocatable :: c
end type ca
type(tb), target :: b, c
type(ca) carr(2)
allocate(carr%c, source = b)
end program polymorph1
% gfortran-4.6 -v polymorph1.f08
Driving: gfortran-4.6 -v polymorph1.f08 -l gfortran -l m -shared-libgcc
Using built-in specs.
COLLECT_GCC=gfortran-4.6
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i486-linux-gnu/4.6/lto-wrapper
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.6.3-14'
--with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-4.6 --enable-shared --enable-linker-build-id
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object
--enable-plugin --enable-objc-gc --enable-targets=all --with-arch-32=i586
--with-tune=generic --enable-checking=release --build=i486-linux-gnu
--host=i486-linux-gnu --target=i486-linux-gnu
Thread model: posix
gcc version 4.6.3 (Debian 4.6.3-14)
COLLECT_GCC_OPTIONS='-v' '-shared-libgcc' '-mtune=generic' '-march=i586'
/usr/lib/gcc/i486-linux-gnu/4.6/f951 polymorph1.f08 -quiet -dumpbase
polymorph1.f08 -mtune=generic -march=i586 -auxbase polymorph1 -version
-fintrinsic-modules-path /usr/lib/gcc/i486-linux-gnu/4.6/finclude -o
/tmp/cc0KCbXA.s
GNU Fortran (Debian 4.6.3-14) version 4.6.3 (i486-linux-gnu)
compiled by GNU C version 4.6.3, GMP version 5.0.5, MPFR version
3.1.0-p10, MPC version 0.9
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
GNU Fortran (Debian 4.6.3-14) version 4.6.3 (i486-linux-gnu)
compiled by GNU C version 4.6.3, GMP version 5.0.5, MPFR version
3.1.0-p10, MPC version 0.9
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
polymorph1.f08: In function 'polymorph1':
polymorph1.f08:18:0: internal compiler error: in gfc_array_allocate, at
fortran/trans-array.c:4332
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.6/README.Bugs> for instructions.
% gfortran-4.7 -v polymorph1.f08
Driving: gfortran-4.7 -v polymorph1.f08 -l gfortran -l m -shared-libgcc
Using built-in specs.
COLLECT_GCC=gfortran-4.7
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i486-linux-gnu/4.7/lto-wrapper
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.7.2-5'
--with-bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs
--enable-languages=c,c++,go,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-4.7 --enable-shared --enable-linker-build-id
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.7
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object
--enable-plugin --enable-objc-gc --enable-targets=all --with-arch-32=i586
--with-tune=generic --enable-checking=release --build=i486-linux-gnu
--host=i486-linux-gnu --target=i486-linux-gnu
Thread model: posix
gcc version 4.7.2 (Debian 4.7.2-5)
COLLECT_GCC_OPTIONS='-v' '-shared-libgcc' '-mtune=generic' '-march=i586'
/usr/lib/gcc/i486-linux-gnu/4.7/f951 polymorph1.f08 -quiet -dumpbase
polymorph1.f08 -mtune=generic -march=i586 -auxbase polymorph1 -version
-fintrinsic-modules-path /usr/lib/gcc/i486-linux-gnu/4.7/finclude -o
/tmp/ccfgx7Zz.s
GNU Fortran (Debian 4.7.2-5) version 4.7.2 (i486-linux-gnu)
compiled by GNU C version 4.7.2, GMP version 5.0.5, MPFR version
3.1.0-p10, MPC version 0.9
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
GNU Fortran (Debian 4.7.2-5) version 4.7.2 (i486-linux-gnu)
compiled by GNU C version 4.7.2, GMP version 5.0.5, MPFR version
3.1.0-p10, MPC version 0.9
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
polymorph1.f08: In function 'polymorph1':
polymorph1.f08:18:0: internal compiler error: in gfc_array_allocate, at
fortran/trans-array.c:4994
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.7/README.Bugs> for instructions.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug fortran/56730] [Fortran 4.6, 4.7] ICE on (wrongly) referencing polymorphic array in allocate
2013-03-25 21:23 [Bug fortran/56730] New: [Fortran 4.6, 4.7] ICE on (wrongly) referencing polymorphic array in allocate tiloschwarz at gcc dot gnu.org
@ 2013-03-26 9:43 ` janus at gcc dot gnu.org
2013-03-26 19:15 ` dominiq at lps dot ens.fr
2015-08-07 20:51 ` mikael at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: janus at gcc dot gnu.org @ 2013-03-26 9:43 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56730
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |janus at gcc dot gnu.org
--- Comment #1 from janus at gcc dot gnu.org 2013-03-26 09:43:20 UTC ---
(In reply to comment #0)
> Current 4.8-branch and 4.9-trunk do not ICE.
Unless it is a regression in 4.6/4.7, it will probably not be fixed on those
branches.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug fortran/56730] [Fortran 4.6, 4.7] ICE on (wrongly) referencing polymorphic array in allocate
2013-03-25 21:23 [Bug fortran/56730] New: [Fortran 4.6, 4.7] ICE on (wrongly) referencing polymorphic array in allocate tiloschwarz at gcc dot gnu.org
2013-03-26 9:43 ` [Bug fortran/56730] " janus at gcc dot gnu.org
@ 2013-03-26 19:15 ` dominiq at lps dot ens.fr
2015-08-07 20:51 ` mikael at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: dominiq at lps dot ens.fr @ 2013-03-26 19:15 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56730
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2013-03-26
Ever Confirmed|0 |1
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2013-03-26 19:14:56 UTC ---
The following comment has been mistakenly posted in pr56731#c3:
AFAICT this has been fixed by revision 187192 (pr41600). I don't think this is
a regression: I get the ICE for 4.5.3, 4.6.3, and 4.7.2 (CLASS is not part of
4.4).
I don't know the best way to resolve this PR: WONTFIX or FIXED?
Note that while r187192 contains many changes and does not look suitable for
backporting, the following patch
--- trunk/gcc/fortran/resolve.c 2012/05/05 07:59:22 187191
+++ trunk/gcc/fortran/resolve.c 2012/05/05 08:49:43 187192
@@ -4904,14 +4904,19 @@
{
/* F03:C614. */
if (ref->u.c.component->attr.pointer
- || ref->u.c.component->attr.proc_pointer)
+ || ref->u.c.component->attr.proc_pointer
+ || (ref->u.c.component->ts.type == BT_CLASS
+ && CLASS_DATA (ref->u.c.component)->attr.pointer))
{
gfc_error ("Component to the right of a part reference "
"with nonzero rank must not have the POINTER "
"attribute at %L", &expr->where);
return FAILURE;
}
- else if (ref->u.c.component->attr.allocatable)
+ else if (ref->u.c.component->attr.allocatable
+ || (ref->u.c.component->ts.type == BT_CLASS
+ && CLASS_DATA (ref->u.c.component)->attr.allocatable))
+
{
gfc_error ("Component to the right of a part reference "
"with nonzero rank must not have the ALLOCATABLE "
could cure the ICE for 4.7 (to be tested;-).
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug fortran/56730] [Fortran 4.6, 4.7] ICE on (wrongly) referencing polymorphic array in allocate
2013-03-25 21:23 [Bug fortran/56730] New: [Fortran 4.6, 4.7] ICE on (wrongly) referencing polymorphic array in allocate tiloschwarz at gcc dot gnu.org
2013-03-26 9:43 ` [Bug fortran/56730] " janus at gcc dot gnu.org
2013-03-26 19:15 ` dominiq at lps dot ens.fr
@ 2015-08-07 20:51 ` mikael at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: mikael at gcc dot gnu.org @ 2015-08-07 20:51 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56730
Mikael Morin <mikael at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |mikael at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #3 from Mikael Morin <mikael at gcc dot gnu.org> ---
All open branches (4.9, 5, and trunk(6)) reject comment #0 with:
comment_0.f90:18.13:
allocate(carr%c, source = b)
1
Error: Component to the right of a part reference with nonzero rank must not
have the ALLOCATABLE attribute at (1)
Closing as FIXED.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-08-07 20:51 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-03-25 21:23 [Bug fortran/56730] New: [Fortran 4.6, 4.7] ICE on (wrongly) referencing polymorphic array in allocate tiloschwarz at gcc dot gnu.org
2013-03-26 9:43 ` [Bug fortran/56730] " janus at gcc dot gnu.org
2013-03-26 19:15 ` dominiq at lps dot ens.fr
2015-08-07 20:51 ` mikael at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).