From: Eric Botcazou <ebotcazou@adacore.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Xinliang David Li <davidxl@google.com>,
Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [google]: initialize language field for clone function struct
Date: Wed, 04 May 2011 17:22:00 -0000 [thread overview]
Message-ID: <201105041914.14958.ebotcazou@adacore.com> (raw)
In-Reply-To: <BANLkTi=H_7u7ToqyVjSXZ4Av1FJ+WBtJqA@mail.gmail.com>
> Actually it turns out that it doesn't matter. If we arrive here with
> something that needs a SAVE_EXPR we have to be able to generate code
> for it somewhere, where there would be obviously the possibility to
> also generate code for a SAVE_EXPR.
The transformations done in fold are optimizations that duplicate things,
hence the need to protect them from multiple evaluations. If you cannot
easily do so (e.g. at global level), you just don't do the optimizations.
But, yes, there is something true. If you have variable sizes at the global
level, they need to be evaluated once for all (unless self-referential, but
this is another subject) so you need to do it somewhere. But you cannot do
it with SAVE_EXPRs since they would end up being shared across functions.
--
Eric Botcazou
next prev parent reply other threads:[~2011-05-04 17:14 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 1:34 Xinliang David Li
2011-05-02 22:13 ` Xinliang David Li
2011-05-03 10:55 ` Jan Hubicka
2011-05-03 16:15 ` Xinliang David Li
2011-05-03 16:46 ` Jan Hubicka
2011-05-03 18:55 ` Eric Botcazou
2011-05-03 19:07 ` Joseph S. Myers
2011-05-03 19:16 ` Nathan Froyd
2011-05-03 19:51 ` Joseph S. Myers
2011-05-03 20:05 ` Nathan Froyd
2011-05-03 19:52 ` Eric Botcazou
2011-05-03 20:09 ` Joseph S. Myers
2011-05-03 20:36 ` Eric Botcazou
2011-05-03 21:27 ` Joseph S. Myers
2011-05-04 8:53 ` Eric Botcazou
2011-05-04 17:27 ` Tom Tromey
2011-05-04 9:52 ` Richard Guenther
2011-05-04 10:02 ` Eric Botcazou
2011-05-04 10:30 ` Joseph S. Myers
2011-05-04 11:01 ` Eric Botcazou
2011-05-04 11:50 ` Richard Kenner
2011-05-04 12:23 ` Diego Novillo
2011-05-04 12:27 ` Richard Kenner
2011-05-04 12:31 ` Diego Novillo
2011-05-04 13:16 ` Michael Matz
2011-05-04 13:22 ` Nathan Froyd
2011-05-04 13:26 ` Diego Novillo
2011-05-04 13:39 ` Richard Kenner
2011-05-04 11:19 ` Richard Guenther
2011-05-04 12:00 ` Michael Matz
2011-05-04 12:08 ` Richard Guenther
2011-05-04 15:33 ` Eric Botcazou
2011-05-04 16:05 ` Richard Guenther
2011-05-04 17:22 ` Eric Botcazou [this message]
2011-05-05 9:07 ` Richard Guenther
2011-05-05 9:25 ` Eric Botcazou
2011-05-05 9:44 ` Richard Guenther
2011-05-05 10:22 ` Eric Botcazou
2011-05-05 11:03 ` Richard Guenther
2011-05-05 11:59 ` Eric Botcazou
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=201105041914.14958.ebotcazou@adacore.com \
--to=ebotcazou@adacore.com \
--cc=davidxl@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=richard.guenther@gmail.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).