From: Alexandre Oliva <aoliva@redhat.com>
To: Andrew Haley <aph@redhat.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
"java@gcc.gnu.org" <java@gcc.gnu.org>
Subject: Re: RFC: Java inliner
Date: Wed, 10 Jul 2002 13:41:00 -0000 [thread overview]
Message-ID: <or3cur37ee.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <15660.6835.58381.407065@cuddles.cambridge.redhat.com>
On Jul 10, 2002, Andrew Haley <aph@redhat.com> wrote:
>> Hmm, I hadn't got the impression you had relied on the preprocessor to
>> separate the C/C++-specific bits from the generic/Java ones.
> I had a try, but it was getting rather complex.
I was just thinking of running something like
diff --ifdef=INLINER_FOR_JAVA tree-inline.c java/java-inline.c
and then using the result as the new tree-inline.c
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2002-07-10 15:54 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 ` RFC: " Daniel Berlin
2002-07-01 11:58 ` 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 [this message]
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=or3cur37ee.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=aph@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=java@gcc.gnu.org \
/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).