Bug 691497

Summary: Various warnings with MSVC
Product: GhostPCL Reporter: Hin-Tak Leung <htl10>
Component: PCL interpreterAssignee: Henry Stiles <henry.stiles>
Status: RESOLVED WONTFIX    
Severity: normal    
Priority: P4    
Version: master   
Hardware: Other   
OS: All   
Customer: Word Size: ---
Attachments: The full log from building all 4 languages.

Description Hin-Tak Leung 2010-07-25 22:53:06 UTC
Created attachment 6549 [details]
The full log from building all 4 languages.

nmake -f *_msvc.mak default in each of the 4 languages.

Firs of all, there is a warning from mkdir "Missing Argument" because PSOBJDIR is not passed along to gs\base\msvclib.mak. The rest is the usual pointer casts and also various type casts from double to float, etc. Except these - some of them needs look at:

..\pxl\pximage.c(243) : warning C4146: unary minus operator applied to unsigned type, result still unsigned
..\pxl\pximage.c(284) : warning C4146: unary minus operator applied to unsigned type, result still unsigned
..\pxl\pxink.c(779) : warning C4146: unary minus operator applied to unsigned type, result still unsigned
..\pl\plchar.c(229) : warning C4146: unary minus operator applied to unsigned type, result still unsigned
..\pcl\pglfill.c(550) : warning C4146: unary minus operator applied to unsigned type, result still unsigned
..\pcl\pglfill.c(654) : warning C4146: unary minus operator applied to unsigned type, result still unsigned
.\obj\tif_warning.obj 
.\obj\gsargs.obj : warning LNK4042: object specified more than once; extras ignored
.\obj\gconfig.obj : warning LNK4042: object specified more than once; extras ignored
.\obj\gscdefs.obj : warning LNK4042: object specified more than once; extras ignored

( after removing the using pointer casts, etc with:

| grep -v "different 'const' qualifiers" |grep -v 'incompatible type'  | grep -v 'possible loss of data' | grep -v 'truncation from' | grep -v 'type cast' | grep -v 'function/data pointer conversion')
Comment 1 Henry Stiles 2010-07-29 15:23:27 UTC
The agreement we came to some time ago was to keep the warnings to 0 in gcc with -Wall and chasing down MSVC warnings was not a good use of time, we may change this policy in the future.  We are aware there are outstanding gcc warnings and those should be fixed.