On 21/07/15 15:33, Tom Browder wrote: > On Sun, Jul 19, 2015 at 11:00 AM, Tom Browder <tom.browder at gmail.com> wrote: >> On Thu, Jul 9, 2015 at 12:00 PM, Viktor Dukhovni >>> That surely means that you're compiling some patched version or >>> not even 1.0.2d. >> >> No, it's the correct version. >> >> But just now, after building gcc-5.2.0 and using it to rebuild >> openssl, all the warnings went away just as Matt said (although the >> jobserver doesn't work for some reason). > > I lied. After rebuilding gcc 5.2.0 and rechecking I get the following > warnings from building 1.0.2d: > > ec_key.c: In function 'EC_KEY_set_public_key_affine_coordinates': > ec_key.c:369:26: warning: variable 'is_char_two' set but not used > [-Wunused-but-set-variable] > int ok = 0, tmp_nid, is_char_two = 0; Like I said in my original email this one is due to compiling with no-ec2m. Its harmless (but should be fixed). > ^ > d1_both.c: In function 'dtls1_retransmit_message': > d1_both.c:1261:9: warning: 'save_write_sequence' may be used > uninitialized in this function [-Wmaybe-uninitialized] > memcpy(s->s3->write_sequence, save_write_sequence, > ^ This one is entirely bogus. "save_write_sequence" is initialized on line 1241. The compiler just isn't clever enough to figure that out. Matt
