>From Henri
So, I could disable fastdebug in build ?
To charles
Do we need the fastdebug to get the asm listing? And is it slower
to run or just start up?
It seems to run my benchmarks about 30% slower.
Since we have Stephen's with fast debug Henri's could be whatever gives
the
Hi Mark,
PrintOptoAssembly (for C2, and PrintLIR for C1) only works in a debug build
(which fastdebug is one), where as PrintAssembly works in all builds. If
you need more annotated asm listing then you might want PrintOptoAssembly,
but if you're just after the code instead of the comments then
Pr
> From Henri
>
> So, I could disable fastdebug in build ?
>
> To charles
> Do we need the fastdebug to get the asm listing? And is it slower to
> run or just start up?
> It seems to run my benchmarks about 30% slower.
>
> Since we have Stephen's with fast debug Henri's could be what
I personally like the PrintAssembly output a lot better...it also annotates
line of code, opcode, etc. I don't feel like PrintOptoAssembly is better.
- Charlie (mobile)
On Nov 7, 2011 3:59 AM, "Krystal Mok" wrote:
> Hi Mark,
>
> PrintOptoAssembly (for C2, and PrintLIR for C1) only works in a de
I agree...Stephen's build scripts can continue to give us debug builds, but
the value of the OS X package is that our end users can install it easily
and test things out.
- Charlie (mobile)
On Nov 7, 2011 3:52 AM, "Mark Roos" wrote:
> From Henri
>
> So, I could disable fastdebug in build ?
>
>
Exactly.
With Adopt-A-JSR and some of the other projects we're pushing, getting a
broader community trying out JDK 8 is a great complement.
There are a lot of Mac users in our community, and having simple installers
is a big help.
Thanks,
Ben
On Nov 7, 2011 12:09 PM, "Charles Oliver Nutter"
wr
