https://bugs.kde.org/show_bug.cgi?id=385409
Ivo Raisr <iv...@ivosh.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |iv...@ivosh.net
--- Comment #19 from Ivo Raisr <iv...@ivosh.net> ---
(In reply to Andreas Arnez from comment #18)
> Another suspicous construct is the type cast
> (const s390x_vec_op_details_t*) &details
> where 'details' is a ULong. I believe this violates the strict aliasing rule.
Indeed. In short words strict aliasing says you are not allowed to view the
same piece of memory through lenses of different types *other* than 'char *'.
I debugged once a nasty problem in SPEC2017 CPU due to a strict aliasing
violation combined with LTO.
The question is also whether strict aliasing is enabled for this compilation
unit...
--
You are receiving this mail because:
You are watching all bug changes.
