From: "Joseph S. Myers" <jsm@polyomino.org.uk>
To: Nathan Sidwell <nathan@codesourcery.com>
Cc: Jie Zhang <zhangjie@magima.com.cn>, gcc@gcc.gnu.org
Subject: Re: A question about integer promotion in GCC
Date: Mon, 06 Sep 2004 09:01:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0409060854230.18615@digraph.polyomino.org.uk> (raw)
In-Reply-To: <413C2552.1060208@codesourcery.com>
On Mon, 6 Sep 2004, Nathan Sidwell wrote:
> > flags from constants.) Splitting fold that way, with the subsequent pass
> > running just before gimplification, should be straightforward. (I don't
> I'd suspect we don't want it to run once just there. It should be cheap
> enough to run multiple times on gimple form.
>
> > know what performance impact there might be, though gains from smaller
> > footprint while parsing the whole file before optimising any of it are
> > possible.) The hard bit would be creating a fold parse for GIMPLE that does
> > everything fold currently does.
> sure, but that's a goal that can be incrementally acheived.
I agree we want to run it multiple times on GIMPLE. Putting the existing
fold just before gimplification is to avoid regressions. Because folding
of subexpressions feeds back into optimisations on the full expression,
things can't be removed from the existing fold without potential for
regressions until all the optimisations have been implemented to work on
GIMPLE; just as it's taking a while to eliminate cases some RTL passes get
which tree-ssa doesn't so that those RTL passes can be removed. While the
implementation of everything for GIMPLE is something that can and so must
be done incrementally, each optimisation placed there improving the
optimisation of programs that use explicit temporaries rather than
complicated expressions.
--
Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/
http://www.srcf.ucam.org/~jsm28/gcc/#c90status - status of C90 for GCC 3.5
jsm@polyomino.org.uk (personal mail)
jsm28@gcc.gnu.org (Bugzilla assignments and CCs)
next prev parent reply other threads:[~2004-09-06 9:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 7:56 Jie Zhang
2004-09-02 8:09 ` Jie Zhang
2004-09-02 8:19 ` Joseph S. Myers
2004-09-03 8:33 ` Jie Zhang
2004-09-06 8:01 ` Nathan Sidwell
2004-09-06 8:43 ` Joseph S. Myers
2004-09-06 8:52 ` Nathan Sidwell
2004-09-06 9:01 ` Joseph S. Myers [this message]
2004-09-06 9:54 ` Nathan Sidwell
2004-09-06 11:59 ` Joseph S. Myers
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=Pine.LNX.4.61.0409060854230.18615@digraph.polyomino.org.uk \
--to=jsm@polyomino.org.uk \
--cc=gcc@gcc.gnu.org \
--cc=nathan@codesourcery.com \
--cc=zhangjie@magima.com.cn \
/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).