Warnings -- so close

[John Pampuch]

Jon-

Lest I be too skeptical... Did the build finish? :)

Otherwise that's quite an accomplishment!  Where should I nudge to  
finish it off?

-John

Sent from my location


On Mar 15, 2010, at 6:46 PM, Jonathan Gibbons  
<Jonathan.Gibbons at Sun.COM> wrote:

> In 2008, the JDK build was swamped with warnings:
>
>> Warning Message Counts:
>> ----------------------
>> 15790 ld warnings (contains 'ld:')
>> 6686 C warnings (contains '[.]c[":]')
>> 1616 C Include file warnings (contains '[.]h[":]')
>> 9700 C++ warnings (contains '[.]cpp[":]')
>>    0 C++ Include file warnings (contains '[.]hpp[":]')
>> 4432 Java warnings (contains '.java:' or 'Note:' )
>>    0 VM warnings (contains 'VM warning:' )
>>  600 Javadoc warnings (contains ': warning -')
>>  250 Compiler driver warnings (contains cc: or CC: or 'cl :')
>>   59 GNU make warnings (contains '.gmk:' or 'akefile:' or  
>> '(ignored)' or starts with 'gnumake')
>>  276 Shell warnings (contains ': not found' or 'awk:')
>>  187 Build warnings (contains WARNING:)
>>  312 Font warnings (contains 'entry is missing')
>> -----
>> 39908 Total of above warnings
>
> It looks like lots of folk have been doing heroic service, because  
> somewhat amazingly, it now looks like I can count the remaining  
> warnings on my fingers and toes without major surgery.
>
> area
>    #warnings
>    notes
> javaws
>    8
>    non-varargs call of varargs method with inexact argument type for  
> last parameter;
> javadoc (main API)
>    4
>
> javadoc (Taglet)
>    2
>
> jvmti
>    1
>    Generated jvmti file does not exist: /platform/jvmti/jvmti.html
> javadoc (management)
>    1
>
> Total
>    16
>
>
>
> Perhaps with one effort, we can fix even these few warnings.
>
> -- Jon