From: Thomas Koenig <tkoenig@netcologne.de>
To: jerry DeLisle <jvdelisle@charter.net>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, fortran] Some more TRIM optimizations
Date: Sat, 11 Jun 2011 10:06:00 -0000 [thread overview]
Message-ID: <4DF3260D.2070304@netcologne.de> (raw)
In-Reply-To: <4DF256E0.3030706@charter.net>
Hi Jerry,
>
>> Ping ** 0.5714
>>
>> Full patch can be found at
>>
>> http://gcc.gnu.org/ml/fortran/2011-06/msg00053.html
>
> OK and thanks for patch.
Sending fortran/ChangeLog
Sending fortran/frontend-passes.c
Sending testsuite/ChangeLog
Adding testsuite/gfortran.dg/trim_optimize_7.f90
Transmitting file data ....
Committed revision 174944.
Thanks for the review!
Thomas
prev parent reply other threads:[~2011-06-11 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-05 21:00 [patch, fortran] Thomas Koenig
2011-06-06 19:25 ` [patch, fortran] Some more TRIM optimizations Thomas Koenig
2011-06-10 17:27 ` Thomas Koenig
2011-06-10 17:52 ` jerry DeLisle
2011-06-11 10:06 ` Thomas Koenig [this message]
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=4DF3260D.2070304@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jvdelisle@charter.net \
/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).