Ah, ok, thanks for the info!

Likely fixed by commit a4d1595a2638db63ac4c73e722c8ba95fdd85ff7 (rijndael-aesni: split assembly block to ease register pressure) in 1.7 branch (and included in 1.7.3+).

Compiler bug. Probably misdetection of aesni support in old AMD processors?

I have now learnt how GCC uses 'undefined behavior' for aggressive optimization
and that this could break code doing unaligned accesses even on x86. So this
needs to be fixed after all.

Thus clang is wrong here because it prints an "error" and not something like a
"performance hint". I close this bug.

Current code is perfectly fine as crc-intel-pclmul.c is i386/amd64-only source
file and that target architecture can handle unaligned loads.

1.4.12 has been released.

Fixed but not tested with commit 6daa9db; to be released in 1.4.12.

Given the proposed workaround, I'd say we don't fix that.

Did you run "make distclean" before trying with --disable-asm?
I'll check the OS detection.

Did you run "make distclean" before trying with --disable-asm?
I'll check the OS detection.

Insufficient information to analyze.