On 30/01/18 14:30, Matt Caswell wrote: > > > On 30/01/18 14:27, Benjamin Kaduk wrote: >> It seems that we've started getting issues with a single build >> configuration, e.g., >> https://travis-ci.org/openssl/openssl/jobs/335110257 >> >> Lots of complaints about alignment, like: >> >> crypto/modes/gcm128.c:1090:36: runtime error: load of misaligned >> address 0x000002350ce5 for type 'const size_t' (aka 'const unsigned >> long'), which requires 8 byte alignment >> 0x000002350ce5: note: pointer points here >> 68 1f ea 3b 14 00 00 0c 00 02 00 00 00 00 00 0c a3 35 89 7d a7 5e 9e 87 >> fa d7 fd 8b c7 34 8a 8d >> ^ >> I didn't see anything particularly special about that configuration >> on a quick once-over; any ideas? > > I raised an issue on this with some of my thoughts and investigation: > > https://github.com/openssl/openssl/issues/5203 > > > The error message about unsigned int requiring 8 byte alignment seems > suspicious to me. Shouldn't it be 4?
Oh...sorry just realised this is a slightly different but very similar error. In my issue it is complaining about an unsigned int requiring 8 byte alignment. This issue is for an unsigned long. Matt _______________________________________________ openssl-project mailing list email@example.com https://mta.openssl.org/mailman/listinfo/openssl-project