public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tavianator at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/112748] New: memmove(ptr, ptr, n) call optimized out even at -O0 with -fsanitize=undefined Date: Tue, 28 Nov 2023 18:02:04 +0000 [thread overview] Message-ID: <bug-112748-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112748 Bug ID: 112748 Summary: memmove(ptr, ptr, n) call optimized out even at -O0 with -fsanitize=undefined Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: tavianator at gmail dot com Target Milestone: --- This is counter-productive, as I wrote the memmove() specifically to get the sanitizers to check that ptr really points to a big enough allocation. $ cat foo.c typedef __SIZE_TYPE__ size_t; void *memmove(void *dest, void *src, size_t n); void foo(void *ptr, size_t n) { memmove(ptr, ptr, n); } $ gcc -O0 -fsanitize=undefined -S foo.c $ cat foo.s .file "foo.c" .text .globl foo .type foo, @function foo: .LFB0: .cfi_startproc pushq %rbp .cfi_def_cfa_offset 16 .cfi_offset 6, -16 movq %rsp, %rbp .cfi_def_cfa_register 6 movq %rdi, -8(%rbp) movq %rsi, -16(%rbp) nop popq %rbp .cfi_def_cfa 7, 8 ret .cfi_endproc .LFE0: .size foo, .-foo .ident "GCC: (GNU) 13.2.1 20230801" .section .note.GNU-stack,"",@progbits
next reply other threads:[~2023-11-28 18:02 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-28 18:02 tavianator at gmail dot com [this message] 2023-11-28 18:08 ` [Bug middle-end/112748] " pinskia at gcc dot gnu.org 2023-11-28 18:21 ` tavianator at gmail dot com 2023-11-29 6:53 ` [Bug sanitizer/112748] " rguenth at gcc dot gnu.org 2023-11-30 19:31 ` jakub at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-112748-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).