Java HotSpot(TM) Server VM warning: increase O_BUFLEN in ostream.hpp -- output truncated
Ulf Zibis
Ulf.Zibis at gmx.de
Thu Jan 14 08:22:12 PST 2010
Thanks for looking at 6916395.
All 4 "guys" of db(), qb() have been inlined in the 2 encode() methods,
but only three of them were printed separately. So I'm confused, why
only 1 of them is missing.
Can you give me a hint about -XX:PrintAssemblyOptions=hsdis-print-bytes ?
What is the purpose of it,
and if/why it is mandatory to get a correct PrintCompilation output?
-Ulf
Am 14.01.2010 16:53, John Rose schrieb:
> If there's a missing PrintCompilation output (and you're getting output for other methods) it is highly likely that the "missing" guy is getting inlined in some other method.
>
> Check the <task> and <parse> elements in the log file, with -XX:+LogCompilation turned on. You'll probably see your method being parsed as part of another method's compilation task.
>
> -- John
>
> On Jan 14, 2010, at 7:38 AM, Ulf Zibis wrote:
>
>
>> Thanks for your fast answer John.
>>
>> The build, I used, was the fastdebug build b78.
>> I didn't set -XX:PrintAssemblyOptions=hsdis-print-bytes. Do you think, this could be the reason for the bad output?
>>
>> BTW, is bug 6916395 treated with 6912062 ?
>>
>> -Ulf
>>
>>
>> Am 14.01.2010 03:36, John Rose schrieb:
>>
>>> Your best bet is to wait for 6912062 to integrate to jdk7/hotspot and become part of the periodic builds. It's in hotspot/hotspot right now:
>>> http://hg.openjdk.java.net/jdk7/hotspot/hotspot/rev/4e6abf09f540
>>>
>>> That garbage output looks like it might be from a product build; try using a debug build if you can find one.
>>>
>>> -- John
>>>
>>>
>>>
>>>
>
>
>
More information about the hotspot-compiler-dev
mailing list