Hi Marti,
I've build lcms v2.7 in my own make system without using the standard
configure options, and found a few warnings from gcc 4.8. The md5
warnings should just be squashed, but the others look like fair warnings
to me. Are you interested in things like this?
Regards
John
----------------
liblittlecms/src/cmsmd5.c: In function 'MD5finish':
liblittlecms/src/cmsmd5.c:244:5: warning: dereferencing type-punned
pointer will break strict-aliasing rules [-Wstrict-aliasing]
((cmsUInt32Number *) ctx->in)[14] = ctx->bits[0];
^
liblittlecms/src/cmsmd5.c:245:5: warning: dereferencing type-punned
pointer will break strict-aliasing rules [-Wstrict-aliasing]
((cmsUInt32Number *) ctx->in)[15] = ctx->bits[1];
^
liblittlecms/src/cmsopt.c: In function 'OptimizeByComputingLinearization':
liblittlecms/src/cmsopt.c:1030:26: warning: variable 'lIsLinear' set but
not used [-Wunused-but-set-variable]
cmsBool lIsSuitable, lIsLinear;
^
liblittlecms/src/cmsplugin.c: In function '_cmsReadFloat32Number':
liblittlecms/src/cmsplugin.c:181:9: warning: dereferencing type-punned
pointer will break strict-aliasing rules [-Wstrict-aliasing]
*n = *(cmsFloat32Number*) &tmp;
^
liblittlecms/src/cmsplugin.c: In function '_cmsWriteFloat32Number':
liblittlecms/src/cmsplugin.c:310:5: warning: dereferencing type-punned
pointer will break strict-aliasing rules [-Wstrict-aliasing]
tmp = *(cmsUInt32Number*) &n;
^
liblittlecms/src/cmssm.c: In function 'ClosestLineToLine':
liblittlecms/src/cmssm.c:221:22: warning: variable 'tc' set but not used
[-Wunused-but-set-variable]
cmsFloat64Number tc, tN, tD;
^
----------------
J
------------------------------------------------------------------------------
_______________________________________________
Lcms-user mailing list
Lcms-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lcms-user
