public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Darrell.Wright at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/104276] memset is not elimited when followed by a store loop writing to that memory location Date: Fri, 15 Jul 2022 19:14:34 +0000 [thread overview] Message-ID: <bug-104276-4-uaf0KBjBja@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104276-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104276 --- Comment #8 from Darrell Wright <Darrell.Wright at gmail dot com> --- What about something like a __builtin_overwrite( ptr, size_t ) that tells the compiler that the range specified will be written. It forms a contract to do so with the compiler and would allow the memset to be eliminated or augmented to part of the range
prev parent reply other threads:[~2022-07-15 19:14 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-28 23:16 [Bug c++/104276] New: Fail to eliminate deadstore from vector constructor Darrell.Wright at gmail dot com 2022-01-28 23:33 ` [Bug tree-optimization/104276] " pinskia at gcc dot gnu.org 2022-01-28 23:33 ` pinskia at gcc dot gnu.org 2022-01-28 23:35 ` pinskia at gcc dot gnu.org 2022-01-28 23:37 ` Darrell.Wright at gmail dot com 2022-01-28 23:40 ` [Bug tree-optimization/104276] memset is not elimited when followed by a store loop writing to that memory location pinskia at gcc dot gnu.org 2022-01-28 23:44 ` pinskia at gcc dot gnu.org 2022-01-28 23:45 ` pinskia at gcc dot gnu.org 2022-01-31 8:15 ` rguenth at gcc dot gnu.org 2022-07-15 19:14 ` Darrell.Wright at gmail dot com [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-104276-4-uaf0KBjBja@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).