From: Andrew Pinski <pinskia@physics.uc.edu>
To: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
Cc: gcc@gcc.gnu.org, Andrew Pinski <pinskia@physics.uc.edu>
Subject: Re: What to remove after tree-ssa is merged?
Date: Wed, 04 Feb 2004 14:44:00 -0000 [thread overview]
Message-ID: <8D04DB6E-5720-11D8-AD61-000393A6D2F2@physics.uc.edu> (raw)
In-Reply-To: <10402041439.AA00150@vlsi1.ultra.nyu.edu>
On Feb 4, 2004, at 06:39, Richard Kenner wrote:
> Should really PLACEHOLDER_EXPR be done in the front-end
> and be expanded to what it really does in gimplify stage
> which every other language needs to do with its language
> specific trees.
>
> Read the documentation and explain what you propose expanding it *to*.
> There's no way to express the needed semantics without this or
> something
> very similar.
If you are playing this trick where is this documentation, I do not see
it in doc/*.texi at
all. There is only one reference to it in doc and that is the
documentation for c-trees
(which is a little lacking by the way but it was added the fact) and it
just says:
Normally these expressions will reference a field in the
outer object using a @code{PLACEHOLDER_EXPR}.
.
Thanks,
Andrew Pinski
next prev parent reply other threads:[~2004-02-04 14:44 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 14:36 Richard Kenner
2004-02-04 14:44 ` Andrew Pinski [this message]
2004-02-04 15:15 ` Michael Matz
-- strict thread matches above, loose matches on Subject: below --
2004-02-04 21:55 Richard Kenner
2004-02-04 21:25 Richard Kenner
2004-02-04 21:51 ` Paul Brook
2004-02-04 21:09 Richard Kenner
2004-02-05 5:32 ` Richard Henderson
2004-02-05 5:50 ` Geert Bosch
2004-02-04 20:55 Richard Kenner
2004-02-04 21:21 ` Paul Brook
2004-02-04 18:43 Richard Kenner
2004-02-04 19:49 ` Paul Brook
2004-02-04 20:15 ` Richard Henderson
2004-02-04 17:54 Richard Kenner
2004-02-04 18:39 ` Paul Brook
2004-02-04 16:14 Richard Kenner
2004-02-04 16:39 ` Michael Matz
2004-02-04 15:49 Richard Kenner
2004-02-04 16:10 ` Michael Matz
2004-02-04 17:25 ` Robert Dewar
2004-02-04 15:21 Richard Kenner
2004-02-04 15:19 Richard Kenner
2004-02-04 15:31 ` Michael Matz
2004-02-04 15:16 S. Bosscher
2004-02-04 14:48 Richard Kenner
2004-02-04 13:52 Richard Kenner
2004-02-04 13:29 S. Bosscher
2004-02-04 13:49 ` Paul Brook
2004-02-04 14:04 ` Michael Matz
2004-02-04 14:19 ` Robert Dewar
2004-02-04 14:31 ` Andrew Pinski
2004-02-04 14:53 ` Robert Dewar
2004-02-04 12:30 Richard Kenner
2004-02-03 16:20 "Documentation by paper" Richard Kenner
2004-02-03 16:54 ` Jan Hubicka
2004-02-03 16:58 ` What to remove after tree-ssa is merged? Paolo Bonzini
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=8D04DB6E-5720-11D8-AD61-000393A6D2F2@physics.uc.edu \
--to=pinskia@physics.uc.edu \
--cc=gcc@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
/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).