[Bug fortran/70397] [5/6 Regression] ice while allocating ultimate polymorphic

2016-04-04 Thread vehre at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70397

vehre at gcc dot gnu.org changed:

   What|Removed |Added

 Status|WAITING |RESOLVED
 Resolution|--- |FIXED

--- Comment #6 from vehre at gcc dot gnu.org ---
No complaints so far, closing.

[Bug fortran/70397] [5/6 Regression] ice while allocating ultimate polymorphic

2016-03-29 Thread vehre at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70397

--- Comment #5 from vehre at gcc dot gnu.org ---
Waiting one week for any new regressions introduced by this patch.

[Bug fortran/70397] [5/6 Regression] ice while allocating ultimate polymorphic

2016-03-29 Thread vehre at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70397

--- Comment #4 from vehre at gcc dot gnu.org ---
Author: vehre
Date: Tue Mar 29 16:54:24 2016
New Revision: 234528

URL: https://gcc.gnu.org/viewcvs?rev=234528=gcc=rev
Log:
gcc/fortran/ChangeLog:

2016-03-29  Andre Vehreschild  

PR fortran/70397
* trans-expr.c (gfc_class_len_or_zero_get): Add function to return a
constant zero tree, when the class to get the _len component from is
not unlimited polymorphic.
(gfc_copy_class_to_class): Use the new function.
* trans.h: Added interface of new function gfc_class_len_or_zero_get.

gcc/testsuite/ChangeLog:

2016-03-29  Andre Vehreschild  

PR fortran/70397
* gfortran.dg/unlimited_polymorphic_25.f90: New test.
* gfortran.dg/unlimited_polymorphic_26.f90: New test.



Added:
trunk/gcc/testsuite/gfortran.dg/unlimited_polymorphic_25.f90
trunk/gcc/testsuite/gfortran.dg/unlimited_polymorphic_26.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-expr.c
trunk/gcc/fortran/trans.h
trunk/gcc/testsuite/ChangeLog

[Bug fortran/70397] [5/6 Regression] ice while allocating ultimate polymorphic

2016-03-29 Thread vehre at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70397

vehre at gcc dot gnu.org changed:

   What|Removed |Added

 Status|NEW |WAITING

--- Comment #3 from vehre at gcc dot gnu.org ---
Waiting for review of patch for trunk.

[Bug fortran/70397] [5/6 Regression] ice while allocating ultimate polymorphic

2016-03-28 Thread vehre at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70397

--- Comment #2 from vehre at gcc dot gnu.org ---
Author: vehre
Date: Mon Mar 28 16:29:14 2016
New Revision: 234507

URL: https://gcc.gnu.org/viewcvs?rev=234507=gcc=rev
Log:
gcc/fortran/ChangeLog:

2016-03-28  Andre Vehreschild  

PR fortran/70397
* trans-expr.c (gfc_class_len_or_zero_get): Add function to return a
constant zero tree, when the class to get the _len component from is
not unlimited polymorphic.
(gfc_copy_class_to_class): Use the new function.
* trans.h: Added interface of new function gfc_class_len_or_zero_get.

gcc/testsuite/ChangeLog:

2016-03-28  Andre Vehreschild  

PR fortran/70397
* gfortran.dg/unlimited_polymorphic_25.f90: New test.
* gfortran.dg/unlimited_polymorphic_26.f90: New test.



Added:
   
branches/gcc-5-branch/gcc/testsuite/gfortran.dg/unlimited_polymorphic_25.f90
   
branches/gcc-5-branch/gcc/testsuite/gfortran.dg/unlimited_polymorphic_26.f90
Modified:
branches/gcc-5-branch/gcc/fortran/ChangeLog
branches/gcc-5-branch/gcc/fortran/trans-expr.c
branches/gcc-5-branch/gcc/fortran/trans.h
branches/gcc-5-branch/gcc/testsuite/ChangeLog

[Bug fortran/70397] [5/6 Regression] ice while allocating ultimate polymorphic

2016-03-25 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70397

Dominique d'Humieres  changed:

   What|Removed |Added

   Priority|P3  |P4
 Status|UNCONFIRMED |NEW
   Last reconfirmed||2016-03-25
 CC||pault at gcc dot gnu.org,
   ||vehre at gcc dot gnu.org
  Known to work||4.9.3
Summary|ice while allocating|[5/6 Regression] ice while
   |ultimate polymorphic|allocating ultimate
   ||polymorphic
 Ever confirmed|0   |1
  Known to fail||5.3.0, 6.0

--- Comment #1 from Dominique d'Humieres  ---
The test compiles with 4.9.3 (it does not mean that the generated code is
correct;-).  The change occurred around revision r221495+patches (may be
r221621).