https://bugs.kde.org/show_bug.cgi?id=385409
--- Comment #18 from Andreas Arnez <ar...@linux.ibm.com> --- (In reply to Julian Seward from comment #14) > More likely is that there's some violation of C "defined behaviour" > that the compiler is exploiting whilst optimising. Or some type > error. I would prefer that you investigated this more and found the > root cause of the problem. Right. The main problem seems to be caused by the inline assembly, where only the first byte of the_insn was declared as input: [insn] "m" (the_insn.bytes[0]) The whole insn is of course needed at this time. So this should be changed to [insn] "m" (the_insn) 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. -- You are receiving this mail because: You are watching all bug changes.
