https://bugs.kde.org/show_bug.cgi?id=441109
--- Comment #2 from William Ashley <w...@amazon.com> ---
With stp (store pair), there's a similar problem. Pairs of 32, 64 and 128-bit
values all get reported as the wrong write sizes.
asm volatile ("stp s0, s1, [%0]" :: "r" (ptr) : "s0", "s1", "memory");
asm volatile ("stp d0, d1, [%0]" :: "r" (ptr) : "d0", "d1", "memory");
asm volatile ("stp q0, q1, [%0]" :: "r" (ptr) : "q0", "q1", "memory");
==26048== Invalid write of size 4
==26048== at 0x400630: main (strtest.c:12)
==26048== Address 0x4a1a140 is 0 bytes after a block of size 256 alloc'd
==26048== at 0x48682A4: malloc (vg_replace_malloc.c:431)
==26048== by 0x4005F3: main (strtest.c:3)
==26048==
==26048== Invalid write of size 8
==26048== at 0x400638: main (strtest.c:13)
==26048== Address 0x4a1a140 is 0 bytes after a block of size 256 alloc'd
==26048== at 0x48682A4: malloc (vg_replace_malloc.c:431)
==26048== by 0x4005F3: main (strtest.c:3)
==26048==
==26048== Invalid write of size 8
==26048== at 0x400640: main (strtest.c:14)
==26048== Address 0x4a1a140 is 0 bytes after a block of size 256 alloc'd
==26048== at 0x48682A4: malloc (vg_replace_malloc.c:431)
==26048== by 0x4005F3: main (strtest.c:3)
--
You are receiving this mail because:
You are watching all bug changes.
