public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mikael Morin <mikael.morin@sfr.fr>
To: Andre Vehreschild <vehre@gmx.de>,
	GCC-Fortran-ML <fortran@gcc.gnu.org>,
	GCC-Patches-ML <gcc-patches@gcc.gnu.org>,
	Antony Lewis	<antony@cosmologist.info>
Subject: Re: [Patch 1/2, Fortran, pr60322]  [OOP] Incorrect bounds on polymorphic dummy array
Date: Mon, 23 Mar 2015 12:29:00 -0000	[thread overview]
Message-ID: <551006FF.1080704@sfr.fr> (raw)
In-Reply-To: <20150226181717.480e282c@vepi2>

 26/02/2015 18:17, Andre Vehreschild a écrit :
> This first patch is only preparatory and does not change any of the semantics of
> gfortran at all.
Sure?

> diff --git a/gcc/fortran/expr.c b/gcc/fortran/expr.c
> index ab6f7a5..d28cf77 100644
> --- a/gcc/fortran/expr.c
> +++ b/gcc/fortran/expr.c
> @@ -4059,10 +4060,10 @@ gfc_lval_expr_from_sym (gfc_symbol *sym)
>    lval->symtree = gfc_find_symtree (sym->ns->sym_root, sym->name);
>  
>    /* It will always be a full array.  */
> -  lval->rank = sym->as ? sym->as->rank : 0;
> +  as = sym->as;
> +  lval->rank = as ? as->rank : 0;
>    if (lval->rank)
> -    gfc_add_full_array_ref (lval, sym->ts.type == BT_CLASS ?
> -			    CLASS_DATA (sym)->as : sym->as);
> +    gfc_add_full_array_ref (lval, as);

This is a change of semantics.  Or do you know that sym->ts.type !=
BT_CLASS?


> diff --git a/gcc/fortran/trans-decl.c b/gcc/fortran/trans-decl.c
> index 3664824..e571a17 100644
> --- a/gcc/fortran/trans-decl.c
> +++ b/gcc/fortran/trans-decl.c
> @@ -1013,16 +1017,24 @@ gfc_build_dummy_array_decl (gfc_symbol * sym, tree dummy)
>    tree decl;
>    tree type;
>    gfc_array_spec *as;
> +  symbol_attribute *array_attr;
>    char *name;
>    gfc_packed packed;
>    int n;
>    bool known_size;
>  
> -  if (sym->attr.pointer || sym->attr.allocatable
> -      || (sym->as && sym->as->type == AS_ASSUMED_RANK))
> +  /* Use the array as and attr.  */
> +  as = sym->as;
> +  array_attr = &sym->attr;
> +
> +  /* The pointer attribute is always set on a _data component, therefore check
> +     the sym's attribute only.  */
> +  if (sym->attr.pointer || array_attr->allocatable
> +      || (as && as->type == AS_ASSUMED_RANK))
>      return dummy;
>  
Any reason to sometimes use array_attr, sometimes not, like here?
By the way, the comment is misleading: for classes, there is the
class_pointer attribute (and it is a pain, I know).

Mikael

  reply	other threads:[~2015-03-23 12:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26 17:19 Andre Vehreschild
2015-03-23 12:29 ` Mikael Morin [this message]
2015-03-23 12:44   ` Andre Vehreschild
2015-03-23 14:58     ` Mikael Morin
2015-03-23 15:49       ` Andre Vehreschild
2015-03-23 19:28         ` Mikael Morin
2015-03-24 10:13     ` Paul Richard Thomas
2015-03-24 17:06       ` [Patch, Fortran, pr60322] was: " Andre Vehreschild
2015-03-25  9:43         ` Dominique d'Humières
2015-03-25 16:57           ` Andre Vehreschild
2015-03-26  9:27             ` Dominique d'Humières
2015-03-27 12:48         ` Paul Richard Thomas
2015-04-05  9:13           ` Paul Richard Thomas
2015-04-09 12:37             ` Andre Vehreschild
2015-04-14 17:01               ` [Patch, Fortran, pr60322, addendum] " Andre Vehreschild
2015-04-16 19:13                 ` Paul Richard Thomas
2015-04-23 11:34                   ` [commited, Patch, " Andre Vehreschild
2015-04-27 17:43                     ` Andre Vehreschild

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=551006FF.1080704@sfr.fr \
    --to=mikael.morin@sfr.fr \
    --cc=antony@cosmologist.info \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=vehre@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).