public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47065] Replace trim(a) by a(1:len_trim(a))
Date: Fri, 31 Dec 2010 11:38:00 -0000	[thread overview]
Message-ID: <bug-47065-4-yJRkv1wFhq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47065-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47065

--- Comment #3 from Thomas Koenig <tkoenig at gcc dot gnu.org> 2010-12-31 11:38:03 UTC ---
The most common cases are handled now.

Still to do:

- Handle substring references, for example trim(a(3:5)). Here, we have
  to watch out for trim(a(function(x):5)), not to evaluate the function
  twice.

- Right now, the optimization is not applied in argument
  lists.  This can be relaxed for PURE functions and subroutines,
  or if dependency analysis shows that it cannot hurt. The latter point
  is probably not worth it.


  parent reply	other threads:[~2010-12-31 11:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-26 15:05 [Bug fortran/47065] New: " tkoenig at gcc dot gnu.org
2010-12-26 21:32 ` [Bug fortran/47065] " tkoenig at gcc dot gnu.org
2010-12-26 21:34 ` tkoenig at gcc dot gnu.org
2010-12-31 11:32 ` tkoenig at gcc dot gnu.org
2010-12-31 11:38 ` tkoenig at gcc dot gnu.org [this message]
2011-01-18 21:08 ` burnus at gcc dot gnu.org
2011-01-18 23:39 ` tkoenig at gcc dot gnu.org
2011-03-27 19:13 ` tkoenig at gcc dot gnu.org
2011-11-09 10:23 ` fxcoudert at gcc dot gnu.org
2013-03-17 15:26 ` tkoenig 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-47065-4-yJRkv1wFhq@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).