From: Caster <cast3r@seznam.cz>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] Re: How to predetermine if ebuilds will compile with 1.5?
Date: Tue, 06 Jun 2006 11:17:29 +0200 [thread overview]
Message-ID: <44854829.4000002@seznam.cz> (raw)
In-Reply-To: <4484ADDC.2010105@sun.com>
Greg Tassone wrote:
> I think this statement is a little too broad to be considered correct.
> The compiler can (and often does) make changes to the resulting binaries
> that may be VM-level specific (e.g., targeted for a 1.5 VM). Consider
> the "-target" argument for javac, for example, which "Allow[s] javac to
> use 1.5 specific features in the libraries and virtual
> machine" (http://java.sun.com/j2se/1.5.0/docs/relnotes/features.html ).
>
David Herron wrote:
>
> er... Caster, the bytecode does vary based on the compiler. And the
> class file format has varied a small amount from release to release with
> the 1.5 class file format being the most different.
>
> This is, as I understand it, the crux of the problem you guys are seeing
> with adopting 1.5 ... yes?
>
Sorry, I wasn't clear enough. I didn't mean the class file format which
is indeed different and causes problems. I was trying to ask if there
are any (the compiled bytecode performance?) gains of using 1.5 compiler
for 1.4 source (without specifying --source and --target 1.4). This
source won't use any 1.5 specific features, but you say the bytecode
still can somehow?
Caster
--
gentoo-java@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-06 9:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-04 10:44 [gentoo-java] How to predetermine if ebuilds will compile with 1.5? Peter
2006-06-04 20:16 ` Caster
2006-06-05 10:23 ` [gentoo-java] " Peter
2006-06-05 14:15 ` Joshua Nichols
2006-06-05 14:27 ` Caster
2006-06-05 22:19 ` David Herron
2006-06-05 22:35 ` Wiktor Wandachowicz
2006-06-06 9:17 ` Caster [this message]
2006-06-06 13:35 ` David Herron
2006-06-08 7:07 ` Calvin Austin
2006-06-05 23:54 ` Greg Tassone
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=44854829.4000002@seznam.cz \
--to=cast3r@seznam.cz \
--cc=gentoo-java@lists.gentoo.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