https://bugs.kde.org/show_bug.cgi?id=460616
--- Comment #6 from William Ashley ---
Thanks Mark!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460616
William Ashley changed:
What|Removed |Added
Attachment #160568|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=460616
William Ashley changed:
What|Removed |Added
CC||w...@amazon.com
--- Comment #1 from William
https://bugs.kde.org/show_bug.cgi?id=441109
--- Comment #2 from William Ashley ---
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&q
https://bugs.kde.org/show_bug.cgi?id=460616
--- Comment #2 from William Ashley ---
On Friday I submitted the change to the valgrind-developers mailing list,
https://sourceforge.net/p/valgrind/mailman/valgrind-developers/thread/ed40273d-295d-445c-8d97-9fc48f535...@amazon.com/
--
You
https://bugs.kde.org/show_bug.cgi?id=441109
--- Comment #1 from William Ashley ---
To expand on this a bit, here's a sweep through all of the 'str' sizes:
#include
int main(void) {
char *ptr = malloc(256);
ptr += 256;
asm volatile ("str b0, [%0]" :: "r" (
https://bugs.kde.org/show_bug.cgi?id=438322
William Ashley changed:
What|Removed |Added
CC|w...@amazon.com |
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=438322
William Ashley changed:
What|Removed |Added
CC||w...@amazon.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=441109
William Ashley changed:
What|Removed |Added
CC||w...@amazon.com
--
You are receiving
