From: Bill Gatliff <bgat@billgatliff.com>
To: java@gcc.gnu.org
Subject: Presentation(s) related to using gcj-built applications on ARM at ESC?
Date: Mon, 18 Aug 2008 18:14:00 -0000 [thread overview]
Message-ID: <48A9BBC8.2070106@billgatliff.com> (raw)
Guys:
Would anyone in this community be interested in putting together a 90-minute
presentation or two about gcj at ESC '08 in Boston?
I'm thinking about things like:
* a tutorial on setting up and using gcj
* the various components of gcj, and how to adapt them for embedded use
* performance comparisons between equivalent C/C++ and Java programs
* hardware control from Java
I'd love presentation(s) on any or all of the above--- or feel free to suggest
something.
I would also really love examples, actual demonstrations, and/or measurement
results as part of the presentation. Ideally, the presentations would target an
embedded platform like the "beagleboard" (http://beagleboard.org). I would of
course provide that board if the speaker didn't have one already.
Reply to me directly or to the list, whichever works for you.
Kindest regards,
b.g.
--
Bill Gatliff
bgat@billgatliff.com
reply other threads:[~2008-08-18 18:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48A9BBC8.2070106@billgatliff.com \
--to=bgat@billgatliff.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).