From: Richard Henderson <rth@redhat.com>
To: Jerry DeLisle <jvdelisle@verizon.net>
Cc: Daniel Kraft <d@domob.eu>, Thomas Koenig <tkoenig@netcologne.de>,
fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [patch, fortran] PR 40628, front-end optimization pass
Date: Mon, 19 Jul 2010 18:21:00 -0000 [thread overview]
Message-ID: <4C449796.5000802@redhat.com> (raw)
In-Reply-To: <4C43D07A.9050500@verizon.net>
On 07/18/2010 09:11 PM, Jerry DeLisle wrote:
> On 07/18/2010 01:46 AM, Daniel Kraft wrote:
>> Hi Thomas,
>>
>> Thomas Koenig wrote:
>>> finally, here's the first attempt at a front-end optimization pass.
>>> Right now, it fixes PR 40626 and optimizes comparisons between variables
>>> (which only really is relevant for character comparisons). Many more
>>> things could (and should) be added over time.
>>
>
> I like the idea as long as we do not duplicate middle-end work. If we
> can improve performance without sacrificing maintainability and
> correctness, I am all for it. The idea of general passes is good.
> Rather than optimize.c maybe call it early_pass.c or whatever.
>
> Do any middle-end maintainers have an opinion on adding this optimization?
As long as the optimizations here are fortran-specific (e.g. high-level
matrix, string, or loop pre-expansion optimizations), I don't mind.
r~
next prev parent reply other threads:[~2010-07-19 18:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-17 18:38 Thomas Koenig
2010-07-18 8:41 ` Daniel Kraft
2010-07-18 10:18 ` Thomas Koenig
2010-07-19 18:59 ` Toon Moene
2010-07-19 19:11 ` Thomas Koenig
2010-07-19 4:12 ` Jerry DeLisle
2010-07-19 18:21 ` Richard Henderson [this message]
2010-07-19 19:06 ` Jakub Jelinek
2010-07-19 22:31 ` Thomas Koenig
2010-07-20 1:19 ` Jerry DeLisle
2010-07-20 2:08 ` Steve Kargl
2010-07-20 2:39 ` Diego Novillo
2010-07-20 2:54 ` Jerry DeLisle
2010-07-20 8:05 ` Tobias Burnus
2010-07-20 8:21 ` Daniel Kraft
2010-07-20 9:44 ` Toon Moene
2010-07-20 9:58 ` Richard Guenther
2010-07-20 22:01 ` Thomas Koenig
2010-07-25 15:52 ` Tobias Burnus
2010-07-25 19:35 ` Thomas Koenig
2010-07-25 21:15 ` Paolo Bonzini
2010-07-26 19:24 ` Thomas Koenig
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=4C449796.5000802@redhat.com \
--to=rth@redhat.com \
--cc=d@domob.eu \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jvdelisle@verizon.net \
--cc=tkoenig@netcologne.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).