public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi 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 12:07:14 +0000 [thread overview] Message-ID: <bug-109945-4-4yMmW8ujFp@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 #25 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Andrew Pinski from comment #9) > struct Widget { > int i; > int a[4]; > }; > Widget *global = 0; > Widget make2() { Widget w; w.i = 1; global = &w; return w; } > void g() { global->i = 42; } > int main() { > Widget w = make2(); > int i = w.i; > g(); > return (i == w.i); > // Does this need to be reloaded and > // compared? or is it obviously true? > } > ``` > > But does w go out of the scope at the end of make2? Yes. This example has undefined behaviour in all versions of C++. w is a local variable, its lifetime is the function body of make2, and global becomes an invalid pointer after make2 returns, so dereferencing global in g() is UB. > Similar question to make > in the original testcase, does the temp go out of scope? Before C++17 yes, it was undefined for exactly the same reasons. That changed in C++17 and now a temporary is not "materialized" until as late as possible. In many cases there would be no temporary, the prvalue returned by make() would initialize w in main without any intermediate temporary. However, [class.temporary] p3 explicitly allows the compiler to create a temporary object when returning a class with a trivial copy constructor and trivial (or deleted) destructor. This is permitted precisely to allow what the x86_64 ABI requires: the return value is passed in registers. Completely eliding the creation and copy of a temporary would have required an ABI break. So the example in comment 0 is also an incorrect program, even in C++17. It's unspecified whether the prvalue created in make() is only materialized when constructing w (so there is never any temporary Widget) or whether the prvalue is materialized to a temporary which then gets copied to w using the trivial copy constructor. Since it's unspecified, the program cannot rely on any particular behaviour. The 'global' pointer might point to w, or it might point to a temporary which has gone out of scope, and in the latter case, dereferencing it in g() is UB. So inconsistent behaviour with different optimization settings and/or noipa attributes seems fine. Either global == &w or the program has UB. I think this is INVALID.
next prev parent reply other threads:[~2024-02-20 12:07 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 2024-02-20 11:53 ` jakub at gcc dot gnu.org 2024-02-20 12:07 ` redi at gcc dot gnu.org [this message] 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-4yMmW8ujFp@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).