From: Jack Howarth <howarth@bromo.msbb.uc.edu>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>
Cc: roger@eyesopen.com, fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [FORTRAN PATCH] Improved scalarization of constant array constructors
Date: Tue, 09 Jan 2007 01:01:00 -0000 [thread overview]
Message-ID: <20070109010058.GA4617@bromo.msbb.uc.edu> (raw)
In-Reply-To: <339c37f20701080123lc8c5d8ap37e3a4a5252b6d3e@mail.gmail.com>
Paul,
Is this patch well defined enough that it might be safe for gcc 4.2
branch as well? If it provides a significant performance improvement
that might merit the risk.
Jack
On Mon, Jan 08, 2007 at 10:23:50AM +0100, Paul Richard Thomas wrote:
> Roger,
>
> Thank you, as usual, for a nicely prepared and explained patch.
>
> >Ok for mainline?
>
> I regtested it on Cygwin_NT/PIV - OK
>
> Paul
next prev parent reply other threads:[~2007-01-09 1:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 9:23 Paul Richard Thomas
2007-01-09 1:01 ` Jack Howarth [this message]
2007-01-09 9:44 ` Paul Thomas
2007-01-09 15:11 ` Jack Howarth
2007-01-09 16:42 ` Paul Richard Thomas
-- strict thread matches above, loose matches on Subject: below --
2007-01-08 4:15 Roger Sayle
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=20070109010058.GA4617@bromo.msbb.uc.edu \
--to=howarth@bromo.msbb.uc.edu \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul.richard.thomas@gmail.com \
--cc=roger@eyesopen.com \
/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).