public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47469] Check whether arrayfunc_assign_needs_temporary misses TBP/PPC attributes
Date: Wed, 14 Oct 2015 16:03:00 -0000	[thread overview]
Message-ID: <bug-47469-4-fkzOf88FiQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47469-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47469

--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Tobias' version is prettier! Does it apply without regressions?

Obviously the patch in comment 0 no longer applies.

Now finding 'gfc_expr_attr (expr2).pointer' prettier than
'expr2->symtree->n.sym->attr.pointer' is just a matter of taste (29 characters
compared to 35). For a newbie like the later is easier to understand than the
former.

BTW what should it be for 'value.function.esym'?


  parent reply	other threads:[~2015-10-14 16:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-26  9:58 [Bug fortran/47469] New: " burnus at gcc dot gnu.org
2015-10-13 13:45 ` [Bug fortran/47469] " dominiq at lps dot ens.fr
2015-10-14 11:57 ` pault at gcc dot gnu.org
2015-10-14 16:03 ` dominiq at lps dot ens.fr [this message]
2015-10-14 21:43 ` dominiq at lps dot ens.fr
2015-10-15  9:14 ` pault at gcc dot gnu.org
2020-10-05 13:25 ` dominiq at lps dot ens.fr
2020-10-06  6:03 ` pault at gcc dot gnu.org
2020-10-07 13:59 ` cvs-commit at gcc dot gnu.org
2020-10-07 14:02 ` pault at gcc dot gnu.org

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=bug-47469-4-fkzOf88FiQ@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).