public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/115037] Unused std::vector is not optimized away. Date: Fri, 10 May 2024 16:12:17 +0000 [thread overview] Message-ID: <bug-115037-4-jlqnOC7eem@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115037-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115037 Jan Hubicka <hubicka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jason at redhat dot com, | |jwakely at redhat dot com --- Comment #2 from Jan Hubicka <hubicka at gcc dot gnu.org> --- I tried to look for duplicates, but did not find one. However I think the first problem is that we do not optimize away the store of 1 to vector while clang does. I think this is because we do not believe we can trust that delete operator is safe? We get: void test () { int * test$D25839$_M_impl$D25146$_M_start; struct vector test; int * _61; <bb 2> [local count: 1073741824]: _61 = operator new (4); <bb 3> [local count: 1063439392]: *_61 = 1; operator delete (_61, 4); test ={v} {CLOBBER}; test ={v} {CLOBBER(eol)}; return; <bb 4> [count: 0]: <L1>: test ={v} {CLOBBER}; resx 2 } If we can not trust fact that operator delete is good, perhaps we can arrange explicit clobber before calling it? I think it is up to std::vector to decide what it will do with the stored array so in this case even instane oprator delete has no right to expect that the data in vector will be sane :)
next prev parent reply other threads:[~2024-05-10 16:12 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-10 15:16 [Bug middle-end/115037] New: " hubicka at gcc dot gnu.org 2024-05-10 15:42 ` [Bug middle-end/115037] " pinskia at gcc dot gnu.org 2024-05-10 16:12 ` hubicka at gcc dot gnu.org [this message] 2024-05-10 16:22 ` pinskia at gcc dot gnu.org 2024-05-10 16:24 ` pinskia at gcc dot gnu.org 2024-05-10 17:19 ` xry111 at gcc dot gnu.org 2024-05-10 18:40 ` redi at gcc dot gnu.org 2024-05-11 0:07 ` xry111 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-115037-4-jlqnOC7eem@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).