Building openssl-fips-2.0.6 for linux-x86_64, using gcc 4.8.2 and I am
seeing these same warnings on three files:
cbc128.c
ccm128.c
gcm128.c

This is first time I've built the FIPS module for this target. For other
targets I've built (using much older gcc cross-compilers, admittedly), I
have not seen such warnings.

I'm not clear which patch Andy is referring to that fixed them for openssl
itself in 2012, or if those fixes were applied to the openssl-fips (I would
think so..).

Thanks,
Kevin


On Sun, Apr 6, 2014 at 11:51 AM, Andy Polyakov via RT <[email protected]>
wrote:

> > Got those kind of messages when compiling openssl 1.0.1:
> > cbc128.c:175:6: warning: dereferencing type-punned pointer will break
> > strict-aliasing rules [-Wstrict-aliasing]
> > *(size_t *)(tmp.c+n) ^ *(size_t *)(ivec+n);
> > ^
> > gcc -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include
> > -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H
> > -Wa,--noexecstack -m64 -DL_ENDIAN -DTERMIO -O3 -Wall#
> > gcc -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include
> > -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H
> > -Wa,--noexecstack -m64 -DL_ENDIAN -DTERMIO -O3 -Wall#
> > cts128.c: In function ‘CRYPTO_cts128_encrypt’:
> > cts128.c:114:3: warning: dereferencing type-punned pointer will break
> > strict-aliasing rules [-Wstrict-aliasing]
> > *(size_t *)(tmp.c+n) = 0;
> > ^
>
> These were fixed in November 2012. Today warnings even in gcm128.c were
> addressed.
>
>
> ______________________________________________________________________
> OpenSSL Project                                 http://www.openssl.org
> Development Mailing List                       [email protected]
> Automated List Manager                           [email protected]
>

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [email protected]
Automated List Manager                           [email protected]

Reply via email to