[Bug 3983] UMAC corruption for messages >1024 bytes due to strict-aliasing violation

[bugzilla-daemon at mindrot.org]

https://bugzilla.mindrot.org/show_bug.cgi?id=3983

--- Comment #2 from Peter Talaber <talaberp at gmail.com> ---
I use Ubuntu Noble, x86_64 with gcc 13.3.0.

The umac.c code is sourced into my C implementation which is how I run
into this. I did not explicitly pass -fno-strict-aliasing but compiled
with -O2 which implied -fstrict-aliasing.
You are right sockaddr usage is similar, and with your compilation
rules issue would never occur. Anyway, I just wanted to highlight that
this code could avoid this problem easily and could be independent
from -f(no-)strict-aliasing setting in downstream projects.

-- 
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.