From: Daniel Berlin <dberlin@dberlin.org>
To: Andrew Haley <aph@cambridge.redhat.com>
Cc: Mark Mitchell <mark@codesourcery.com>,
Per Bothner <per@bothner.com>, Fergus Henderson <fjh@cs.mu.OZ.AU>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
"java@gcc.gnu.org" <java@gcc.gnu.org>
Subject: Re: RFC: Java inliner
Date: Mon, 01 Jul 2002 11:56:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0207011455550.20102-100000@dberlin.org> (raw)
In-Reply-To: <15648.40350.493795.623862@cuddles.cambridge.redhat.com>
On Mon, 1 Jul 2002, Andrew Haley wrote:
> Mark Mitchell writes:
> >
> > The current inliner already has mechanisms for language-specific
> > extensions. If those can be used, or it can be easily extended so that
> > they can be used, great.
>
> Well I tried, I really did. But the inliner we have at the moment
> uses C-private tree nodes to such an extent that I think it isn't
> possible without totally messing up the code. I could replace every
> occurrence of these nodes with macros or function pointers, but the
> result would not be pretty. The real answer in the long term is, of
> course, SIMPLE.
Is the java inliner usable in languages other than java (IE could we
replace the current c-inliner with your java inliner)?
Or did you do the same thing, and create java specific nodes?
>
> Andrew.
>
>
next prev parent reply other threads:[~2002-07-01 18:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 7:00 Andrew Haley
2002-06-11 7:25 ` Daniel Berlin
2002-06-11 7:26 ` Andrew Haley
2002-06-11 7:56 ` Fergus Henderson
2002-06-11 9:18 ` Andrew Haley
2002-06-11 9:49 ` Joe Buck
2002-06-11 10:59 ` Andrew Haley
2002-06-11 11:29 ` Diego Novillo
2002-06-11 22:36 ` Mark Mitchell
2002-06-12 2:24 ` Per Bothner
2002-06-12 4:47 ` Andrew Haley
2002-06-12 6:38 ` Mark Mitchell
2002-06-12 8:45 ` Andrew Haley
2002-06-12 9:13 ` Daniel Berlin
2002-06-12 9:28 ` Daniel Berlin
2002-07-01 11:21 ` Andrew Haley
2002-07-01 11:29 ` Andrew Haley
2002-07-01 11:56 ` Daniel Berlin [this message]
2002-07-01 11:58 ` RFC: " Andrew Haley
2002-07-10 5:16 ` Alexandre Oliva
2002-07-10 7:08 ` Andrew Haley
2002-07-10 7:10 ` Alexandre Oliva
2002-07-10 7:32 ` Andrew Haley
2002-07-10 13:41 ` Alexandre Oliva
2002-07-30 9:43 ` Andrew Haley
2002-08-12 10:37 ` Tom Tromey
2002-08-12 10:42 ` Andrew Haley
2002-07-10 9:00 ` Tom Tromey
2002-06-11 8:39 ` profiling shared libraries Taha Mannan Jiruwala
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.44.0207011455550.20102-100000@dberlin.org \
--to=dberlin@dberlin.org \
--cc=aph@cambridge.redhat.com \
--cc=fjh@cs.mu.OZ.AU \
--cc=gcc@gcc.gnu.org \
--cc=java@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=per@bothner.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).