public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Li junsong <ljs.darkfish@gmail.com>
To: java@gcc.gnu.org
Subject: About compiling process in GCJ and garbage collection
Date: Sun, 11 Sep 2011 19:23:00 -0000	[thread overview]
Message-ID: <CA+kGxtN0jtDYRJjwBeifQ7amuqOdXN2JS+7HCt5mWT1K4YiT3g@mail.gmail.com> (raw)

Hi there,

I have asked some questions about the plugin loading problem ( refer
to Andrew's answer: http://gcc.gnu.org/ml/java/2011-09/msg00001.html
and Bryce's answer: http://gcc.gnu.org/ml/java/2011-09/msg00003.html )
And now I know ecj is the workhorse when compiling source code to
bytecode.

I still have a question about the compiling process:

if I use GCJ to compile the java source code to machine code directly,
 it will first use ecj to compile java source to bytecode, and then
compile the bytecode(or other information) to machine code.( right? )
BUT, I write a plugin, which removes a certain statement in gimple
tree, and the gcj dump the gimple tree into file. The plugin works.
That means that  GCJ does do something in the process  of compiling
the source code, otherwise the ecj MUST use the same tree
structure(GENERIC, GIMPLE) as gcc does to compile source code in order
to provide information to the compiler of GCJ to do the rest process(
in my case, to provide information for GCJ to remove a certain
statement), which is kind of impossible since ecj is not part of gcc
but GIMPLE is.
Can you help correct me, and explain this?

I have tried the usage of "gcj -v" to print the compiling information,
and I see there are a few files being produced in /tmp, I think that
it is the bytecode of java code, or the STRING type stuff( because I
didn't find any string in the dumped file. )


Thanks,
J. Li

             reply	other threads:[~2011-09-11 19:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-11 19:23 Li junsong [this message]
2011-09-12 10:08 ` Bryce McKinlay

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=CA+kGxtN0jtDYRJjwBeifQ7amuqOdXN2JS+7HCt5mWT1K4YiT3g@mail.gmail.com \
    --to=ljs.darkfish@gmail.com \
    --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).