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/109945] Escape analysis hates copy elision: different result with -O1 vs -O2 Date: Tue, 23 May 2023 16:48:29 +0000 [thread overview] Message-ID: <bug-109945-4-sNj4nJ8x8h@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jason at gcc dot gnu.org Known to fail|4.1.2, 4.5.3, 4.7.4, 4.9.0 | --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- The testcase is very related to the old PR and shows the issue manifests itself also for !TYPE_NEEDS_CONSTRUCTING types. I wonder whether we need a CTOR at all here to show the issue. I also wonder how we can query whether the type has a CTOR (as opposed to "needs" one). The function type is <function_type 0x7ffff6ff3bd0 type <record_type 0x7ffff6fdef18 Widget sizes-gimplified needs-constructing cxx-odr-p type_1 type_5 type_6 BLK size <integer_cst 0x7ffff6ff6048 constant 160> unit-size <integer_cst 0x7ffff6ff6060 constant 20> align:32 warn_if_not_align:0 symtab:0 alias-set 2 canonical-type 0x7ffff6fdef18 fields <function_decl 0x7ffff6ffd000 __dt type <method_type 0x7ffff6ff3f18> public abstract external autoinline decl_3 QI t.ii:1:8 align:16 warn_if_not_align:0 context <record_type 0x7ffff6fdef18 Widget> full-name "Widget::~Widget() noexcept (<uninstantiated>)" not-really-extern chain <function_decl 0x7ffff6ffd200 __dt_base >> context <translation_unit_decl 0x7ffff6e3f168 t.ii> full-name "struct Widget" needs-constructor X() X(constX&) this=(X&) n_parents=0 use_template=0 interface-unknown pointer_to_this <pointer_type 0x7ffff6ff30a8> reference_to_this <reference_type 0x7ffff6ff3930> chain <type_decl 0x7ffff6e64c78 Widget>> so the type has TYPE_NEEDS_CONSTRUCTING set but it isn't TREE_ADDRESSABLE.
next prev parent reply other threads:[~2023-05-23 16:48 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 [this message] 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 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-sNj4nJ8x8h@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).