procyberian/gcc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

re PR fortran/65751 (Bogus &L in error message)

Browse source 
2015-11-17  Dominique d'Humieres <dominiq@lps.ens.fr>

	PR fortran/65751
	* expr.c (gfc_check_pointer_assign): Fix error message.

	* gfortran.dg/unlimited_polymorphic_2.f03: Update test.

From-SVN: r230465
This commit is contained in:
Dominique d'Humieres 2015-11-17 17:29:45 +01:00 • committed by Dominique d'Humieres
parent df94599f0b
commit 83be3fe57d
4 changed files with 15 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
gcc/fortran/ChangeLog
View file

@ -1,3 +1,8 @@
2015-11-17 Dominique d'Humieres <dominiq@lps.ens.fr>
PR fortran/65751
* expr.c (gfc_check_pointer_assign): Fix error message.
2015-11-16 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/58027

9
gcc/fortran/expr.c
View file

@ -3632,11 +3632,10 @@ gfc_check_pointer_assign (gfc_expr *lvalue, gfc_expr *rvalue)
|| (lvalue->ts.type == BT_DERIVED
&& (lvalue->ts.u.derived->attr.is_bind_c
|| lvalue->ts.u.derived->attr.sequence))))
gfc_error ("Data-pointer-object &L must be unlimited "
"polymorphic, a sequence derived type or of a "
"type with the BIND attribute assignment at %L "
"to be compatible with an unlimited polymorphic "
"target", &lvalue->where);
gfc_error ("Data-pointer-object at %L must be unlimited "
"polymorphic, or of a type with the BIND or SEQUENCE "
"attribute, to be compatible with an unlimited "
"polymorphic target", &lvalue->where);
else
gfc_error ("Different types in pointer assignment at %L; "
"attempted assignment of %s to %s", &lvalue->where,

5
gcc/testsuite/ChangeLog
View file

@ -1,3 +1,8 @@
2015-11-17 Dominique d'Humieres <dominiq@lps.ens.fr>
PR fortran/65751
* gfortran.dg/unlimited_polymorphic_2.f03: Update test.
2015-11-17 Ilya Enkovich <enkovich.gnu@gmail.com>
PR middle-end/68134

2
gcc/testsuite/gfortran.dg/unlimited_polymorphic_2.f03
View file

@ -48,7 +48,7 @@ contains
call foo (y)
y => tgt ! This is OK, of course.
tgt => y ! { dg-error "must be unlimited polymorphic" }
tgt => y ! { dg-error "Data-pointer-object at .1. must be unlimited polymorphic" }
select type (y) ! This is the correct way to accomplish the previous
type is (integer)