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 tree-optimization/109945] Escape analysis hates copy elision: different result with -O1 vs -O2 Date: Tue, 20 Feb 2024 10:45:43 +0000 [thread overview] Message-ID: <bug-109945-4-dfK23ILG8u@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109945-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109945 --- Comment #23 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Changing what types have TREE_ADDRESSABLE flag on it would cause significant ABI changes, that is not what we can do. Widget above does not have trivial default constructor, but has trivial copy constructor and trivial destructor, it certainly can be copied. Consider adjusted testcase: struct Widget { Widget(); long i = 1; long j = 2; }; Widget *global = nullptr; Widget::Widget() { global = this; } [[gnu::noipa]] Widget make() { return Widget(); } void g() { global->i = 42; } int main() { Widget w = make(); int i = w.i; g(); return (i == w.i); // Does this need to be reloaded and // compared? or is it obviously true? } On x86_64, this Widget is returned in registers, so the assumptions the testcase has look wrong to me, dereferencing global when the return went out of scope looks UB to me. On i686, this Widget is returned in memory. Is the testcase valid there or UB as well? Jason, thoughts on this? If the above testcase is for some reason valid conditionally (on some targets, not on others, depending on calling conventions), I think we could check TREE_ADDRESSABLE on the called function RESULT_DECL if it has some extra flag set by the FE that there was guaranteed copy ellision (and assume worst case if we don't see the called function (we then don't know if it has been compiled by C or C++ etc.) or it has noipa attribute).
next prev parent reply other threads:[~2024-02-20 10:45 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-23 14:00 [Bug c++/109945] New: " arthur.j.odwyer at gmail dot com 2023-05-23 16:09 ` [Bug tree-optimization/109945] " rguenth at gcc dot gnu.org 2023-05-23 16:11 ` rguenth at gcc dot gnu.org 2023-05-23 16:19 ` pinskia at gcc dot gnu.org 2023-05-23 16:48 ` rguenth at gcc dot gnu.org 2023-05-23 16:53 ` rguenth at gcc dot gnu.org 2023-05-23 16:53 ` pinskia at gcc dot gnu.org 2023-05-23 17:46 ` arthur.j.odwyer at gmail dot com 2023-05-23 17:49 ` pinskia at gcc dot gnu.org 2023-05-23 17:52 ` pinskia at gcc dot gnu.org 2023-05-23 17:53 ` pinskia at gcc dot gnu.org 2023-05-23 19:38 ` arthur.j.odwyer at gmail dot com 2023-05-24 6:48 ` rguenth at gcc dot gnu.org 2023-05-24 7:59 ` rguenth at gcc dot gnu.org 2023-05-24 8:16 ` jakub at gcc dot gnu.org 2023-05-24 8:42 ` rguenther at suse dot de 2023-05-24 8:51 ` jakub at gcc dot gnu.org 2023-05-24 8:55 ` rguenther at suse dot de 2023-05-24 9:00 ` jakub at gcc dot gnu.org 2023-05-24 10:12 ` rguenth at gcc dot gnu.org 2023-07-01 23:37 ` pinskia at gcc dot gnu.org 2023-07-10 8:52 ` rguenth at gcc dot gnu.org 2024-02-20 9:58 ` rguenth at gcc dot gnu.org 2024-02-20 10:45 ` jakub at gcc dot gnu.org [this message] 2024-02-20 11:53 ` jakub at gcc dot gnu.org 2024-02-20 12:07 ` redi at gcc dot gnu.org 2024-02-20 12:15 ` redi at gcc dot gnu.org 2024-02-20 12:33 ` rguenth at gcc dot gnu.org 2024-02-20 12:41 ` redi at gcc dot gnu.org 2024-02-20 12:48 ` jakub at gcc dot gnu.org 2024-02-20 15:47 ` arthur.j.odwyer at gmail dot com 2024-02-20 15:52 ` arthur.j.odwyer at gmail dot com 2024-02-20 16:49 ` redi at gcc dot gnu.org 2024-03-01 17:20 ` redi 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-109945-4-dfK23ILG8u@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).