https://bugs.kde.org/show_bug.cgi?id=453084
--- Comment #3 from mli...@suse.cz ---
(In reply to Tom Hughes from comment #2)
> Well which function did the compiler actually use for that?
>
> It doesn't really matter what you wrote in the source - if the compiler has
> decided that it's safe to replace it with memcpy (because it knows the
> memcpy implementation is overlap safe) then it might do that but valgrind
> has no way to know that so will warn about it.
No, it's not the case:
$ objdump -S ./a.out
...
int main() {
201146: 55 push %rbp
201147: 48 89 e5 mov %rsp,%rbp
...
201176: e8 95 fe ff ff call 201010 <__memmove_chk@plt>
>
> I'd try and reproduce it to see for myself but it's likely to be very
> environment sensitive and you haven't even said what version of Fedora
> you're using.
Fedora 35 (latest), please see the provided Dockerfile.
--
You are receiving this mail because:
You are watching all bug changes.
