public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109442] Dead local copy of std::vector not removed from function Date: Tue, 11 Apr 2023 13:28:53 +0000 [thread overview] Message-ID: <bug-109442-4-ZEGBQza7eb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109442-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109442 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC| |jwakely.gcc at gmail dot com, | |rguenth at gcc dot gnu.org Last reconfirmed| |2023-04-11 Version|unknown |13.0 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- So we're failing to DSE _13 = pretmp_25 - pretmp_63; if (_13 > 4) goto <bb 7>; [97.30%] else goto <bb 6>; [2.70%] <bb 6> [local count: 14278734]: if (_13 == 4) goto <bb 8>; [34.00%] else goto <bb 9>; [66.00%] <bb 7> [local count: 913536322]: _23 = (long unsigned int) _13; __builtin_memmove (_37, pretmp_63, _23); goto <bb 9>; [100.00%] <bb 8> [local count: 34511373]: _24 = *pretmp_63; *_37 = _24; <bb 9> [local count: 542742079]: operator delete (_37, _49); because I think the DTOR / overloaded global delete might inspect the vector contents. So I'm not sure it would be valid to elide the memmove/store. When the stores would be elided we'd DCE the new/delete pair as well.
next prev parent reply other threads:[~2023-04-11 13:28 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-06 19:00 [Bug tree-optimization/109442] New: " hiraditya at msn dot com 2023-04-11 13:28 ` rguenth at gcc dot gnu.org [this message] 2023-04-11 13:33 ` [Bug tree-optimization/109442] " redi at gcc dot gnu.org 2023-04-11 13:38 ` redi at gcc dot gnu.org 2023-04-12 7:40 ` [Bug libstdc++/109442] " rguenth at gcc dot gnu.org 2023-04-12 9:29 ` redi at gcc dot gnu.org 2023-04-12 9:45 ` rguenth at gcc dot gnu.org 2023-04-12 10:01 ` redi at gcc dot gnu.org 2023-04-12 10:13 ` redi at gcc dot gnu.org 2023-04-12 10:22 ` rguenth at gcc dot gnu.org 2023-04-12 10:29 ` redi at gcc dot gnu.org 2023-04-12 10:35 ` redi at gcc dot gnu.org 2023-04-12 11:52 ` rguenther at suse dot de 2023-04-12 11:55 ` redi at gcc dot gnu.org 2023-04-16 18:38 ` richard-gccbugzilla at metafoo dot co.uk 2023-04-17 6:49 ` rguenth at gcc dot gnu.org 2023-04-18 2:15 ` richard-gccbugzilla at metafoo dot co.uk 2023-06-15 18:38 ` hiraditya at msn dot com 2024-05-11 0:07 ` xry111 at gcc dot gnu.org 2024-05-11 16:05 ` hubicka at gcc dot gnu.org 2024-05-14 13:47 ` Jan Hubicka 2024-05-11 16:44 ` redi at gcc dot gnu.org 2024-05-14 13:47 ` hubicka at ucw dot cz
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-109442-4-ZEGBQza7eb@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).