It seems that duplicating the check on the existence of MAYLOSEDATA3 in the other building .com files would be the way to go. As it stands now, this is only done in ssl/ssl-lib.com... At least in 1.0.2, where this seems to have proliferated further than in all other branches.
In message <20140612160341.47773p724okt5...@www.polarhome.com> on Thu, 12 Jun 2014 16:03:41 +0200, Zoltan Arpadffy <z...@polarhome.com> said: zoli> Hi Richard, zoli> zoli> I could not find much more information about either, but on IA64 zoli> platform HP C V7.3-020 on OpenVMS IA64 V8.4 produces such warnings. zoli> zoli> Please check the following logs zoli> http://www.polarhome.com/openssl/BUILD100.LOG for 1.0.0m zoli> zoli> Please, advice how to solve this issue. zoli> zoli> Thank you, zoli> Z zoli> zoli> Quoting Richard Levitte <rich...@levitte.org>: zoli> zoli> > I just stumbled on problems with MAYLOSEDATA3 while looking at other zoli> > stuff... and I wonder, what exactly is it? Sorry, I've been out of zoli> > it for quite a while, and I haven't dug through all talks there may zoli> > have been, so I may be missing something. zoli> > zoli> > Thing is, looking at the docs for the latest compiler (v7.3), there is zoli> > no such warning message. There is MAYLOSEDATA and MAYLOSEDATA2, but no zoli> > MAYLOSEDATA3. Is this a misunderstanding, a typo, or is there a zoli> > secret newer HP CC that I don't know about? zoli> > zoli> > http://h71000.www7.hp.com/commercial/c/docs/decc_alpha_help_4.html#Ref504 zoli> > zoli> > In message <002401cf52e5$5791b8f0$06b52ad0$@com> on Tue, 8 Apr 2014 06:45:18 +0200, "Zoltan Arpadffy" <z...@polarhome.com> said: zoli> > zoli> > zoli> Right approach Steven. zoli> > zoli> zoli> > zoli> Mea culpa :( zoli> > zoli> I am terribly sorry proposing ignorance of MAYLOSEDATA3 while not testing on zoli> > zoli> older compilers. zoli> > zoli> zoli> > zoli> Thank you. zoli> > zoli> Regards, zoli> > zoli> Z zoli> > zoli> zoli> > zoli> -----Original Message----- zoli> > zoli> From: owner-openssl-...@openssl.org [mailto:owner-openssl-...@openssl.org] zoli> > zoli> On Behalf Of Steven M. Schweda zoli> > zoli> Sent: den 8 april 2014 05:12 zoli> > zoli> To: openssl-dev@openssl.org zoli> > zoli> Subject: Re: OpenSSL version 1.0.1g v. VMS zoli> > zoli> zoli> > zoli> From: "Dr. Stephen Henson" <st...@openssl.org> zoli> > zoli> zoli> > zoli> > Patch applied. Let me know of any problems. zoli> > zoli> zoli> > zoli> Thanks. Sadly, I forgot one refinement, which would keep the warning zoli> > zoli> from the test out of the log. If I could talk you into smoothing over that zoli> > zoli> blunder, then I'd be able to rest easy (for a while). zoli> > zoli> zoli> > zoli> --- ssl/ssl-lib.com;-1 2014-04-07 15:18:26 -0500 zoli> > zoli> +++ ssl/ssl-lib.com 2014-04-07 18:26:49 -0500 zoli> > zoli> @@ -1024,6 +1024,8 @@ zoli> > zoli> $ THEN zoli> > zoli> $! Not all compiler versions support MAYLOSEDATA3. zoli> > zoli> $ OPT_TEST = "MAYLOSEDATA3" zoli> > zoli> +$ DEFINE /USER_MODE SYS$ERROR NL: zoli> > zoli> +$ DEFINE /USER_MODE SYS$OUTPUT NL: zoli> > zoli> $ 'CC' /NOCROSS_REFERENCE /NOLIST /NOOBJECT - zoli> > zoli> /WARNINGS = DISABLE = ('OPT_TEST', EMPTYFILE) NL: zoli> > zoli> $ IF ($SEVERITY) zoli> > zoli> zoli> > zoli> Sorry about the extra bother. zoli> > zoli> zoli> > zoli> zoli> > zoli> For the record (no action required (or even requested)), the only zoli> > zoli> remaining compiler warnings were: zoli> > zoli> zoli> > zoli> if (timeleft.tv_sec < 0) ....................^ zoli> > zoli> %CC-I-QUESTCOMPARE, In this statement, the unsigned expression zoli> > zoli> "timeleft.tv_sec" is being compared with a relational operator to a zoli> > zoli> constant whose value is not greater than zero. This might not be what you zoli> > zoli> intended. zoli> > zoli> at line number 310 in file zoli> > zoli> ALP$DKC100:[UTILITY.SOURCE.OPENSSL.openssl-1_0_1g.crypto.bio]bss_dgram.c;1 zoli> > zoli> zoli> > zoli> Around here, time_t tends to be unsigned. zoli> > zoli> zoli> > zoli> zoli> > zoli> if (*outlen <= 0) zoli> > zoli> ............^ zoli> > zoli> %CC-I-QUESTCOMPARE, In this statement, the unsigned expression "*outlen" zoli> > zoli> is being compared with a relational operator to a constant whose value is zoli> > zoli> not greater than zero. This might not be what you intended. zoli> > zoli> at line number 180 in file zoli> > zoli> ALP$DKC100:[UTILITY.SOURCE.OPENSSL.openssl-1_0_1g.engines.ccgost]gost94_keyx zoli> > zoli> .c;1 zoli> > zoli> zoli> > zoli> Around here, size_t tends to be unsigned. zoli> > zoli> zoli> > zoli> zoli> > zoli> if (size <= 0 || ((len = data[0])) != (size -1)) zoli> > zoli> ............................^ %CC-I-QUESTCOMPARE, In this statement, the zoli> > zoli> unsigned expression "size" is being compared with a relational operator to zoli> > zoli> a constant whose value is not greater than zero. This might not be what zoli> > zoli> you intended. zoli> > zoli> at line number 1128 in file zoli> > zoli> ALP$DKC100:[UTILITY.SOURCE.OPENSSL.openssl-1_0_1g.ssl]t1_lib.c;1 zoli> > zoli> zoli> > zoli> Here, "size" seems to be declared as unsigned: zoli> > zoli> unsigned short size; zoli> > zoli> making the "< 0" part of that test pointless everywhere. zoli> > zoli> zoli> > zoli> These are all Informational ("-I-") complaints, so they cause less zoli> > zoli> trouble than a real warning ("-W-"). zoli> > zoli> zoli> zoli> zoli> --- zoli> WebMail, polarhome.com zoli> zoli> ______________________________________________________________________ zoli> OpenSSL Project http://www.openssl.org zoli> Development Mailing List openssl-dev@openssl.org zoli> Automated List Manager majord...@openssl.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
