public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/112748] memmove(ptr, ptr, n) call optimized out even at -O0 with -fsanitize=undefined Date: Thu, 30 Nov 2023 19:31:50 +0000 [thread overview] Message-ID: <bug-112748-4-B2pRg5ucFM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112748-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112748 --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- So, do we want something like --- gcc/gimple-fold.cc.jj 2023-11-02 12:15:12.205998817 +0100 +++ gcc/gimple-fold.cc 2023-11-30 20:24:01.092095623 +0100 @@ -5083,12 +5083,16 @@ gimple_fold_builtin (gimple_stmt_iterato return gimple_fold_builtin_bzero (gsi); case BUILT_IN_MEMSET: + if (!optimize) + return false; return gimple_fold_builtin_memset (gsi, gimple_call_arg (stmt, 1), gimple_call_arg (stmt, 2)); case BUILT_IN_MEMCPY: case BUILT_IN_MEMPCPY: case BUILT_IN_MEMMOVE: + if (!optimize) + return false; return gimple_fold_builtin_memory_op (gsi, gimple_call_arg (stmt, 0), gimple_call_arg (stmt, 1), fcode); case BUILT_IN_SPRINTF_CHK: (and repeat for many other builtins)? I'm afraid we can't do if (!optimize) return false; for all builtins in gimple_fold_builtin, because some builtins by design must be always folded and never expand. E.g. __builtin_clear_padding, __builtin_{clz,ctz,clrsb,ffs,popcount,parity}g, __builtin_{add,sub,mul}_overflow{,_p} and many others. expand_builtin has /* When not optimizing, generate calls to library functions for a certain set of builtins. */ if (!optimize && !called_as_built_in (fndecl) && fcode != BUILT_IN_FORK && fcode != BUILT_IN_EXECL && fcode != BUILT_IN_EXECV && fcode != BUILT_IN_EXECLP && fcode != BUILT_IN_EXECLE && fcode != BUILT_IN_EXECVP && fcode != BUILT_IN_EXECVE && fcode != BUILT_IN_CLEAR_CACHE && !ALLOCA_FUNCTION_CODE_P (fcode) && fcode != BUILT_IN_FREE && (fcode != BUILT_IN_MEMSET || !(flag_inline_stringops & ILSOP_MEMSET)) && (fcode != BUILT_IN_MEMCPY || !(flag_inline_stringops & ILSOP_MEMCPY)) && (fcode != BUILT_IN_MEMMOVE || !(flag_inline_stringops & ILSOP_MEMMOVE)) && (fcode != BUILT_IN_MEMCMP || !(flag_inline_stringops & ILSOP_MEMCMP))) return expand_call (exp, target, ignore); Perhaps just a general if (!optimize && !called_as_built_in (fndecl)) return false; at the start of gimple_fold_builtin? Or do we want to let some exceptions? Do we also apply GIMPLE match.pd simplification at -O0?
prev parent reply other threads:[~2023-11-30 19:31 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-28 18:02 [Bug c/112748] New: " tavianator at gmail dot com 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 [this message]
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-B2pRg5ucFM@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).