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 c++/99459] [11 Regression] Many coroutines regressions on armv7hl-linux-gnueabi Date: Mon, 08 Mar 2021 09:54:26 +0000 [thread overview] Message-ID: <bug-99459-4-QUWIoTLEM8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99459-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99459 --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- p debug_tree (dummy) <nop_expr 0x7fffe91ab380 type <void_type 0x7fffea0610a8 void type_6 VOID align:8 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type 0x7fffea0610a8 pointer_to_this <pointer_type 0x7fffea061150>> side-effects arg:0 <call_expr 0x7fffe917baf0 type <pointer_type 0x7fffea061150 type <void_type 0x7fffea0610a8 void> public unsigned type_6 SI size <integer_cst 0x7fffea0501c8 constant 32> unit-size <integer_cst 0x7fffea0501e0 constant 4> align:32 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type 0x7fffea061150 pointer_to_this <pointer_type 0x7fffea06b1f8> reference_to_this <reference_type 0x7fffe9997dc8>> side-effects nothrow fn <addr_expr 0x7fffe91ab360 type <pointer_type 0x7fffe970b5e8> constant arg:0 <function_decl 0x7fffe96d3000 __dt_comp >> arg:0 <addr_expr 0x7fffe91ab340 type <pointer_type 0x7fffe96d1888> arg:0 <var_decl 0x7fffe98f4c60 Fs>> ./example.cpp:317:1 start: ./example.cpp:317:1 finish: ./example.cpp:317:1> ./example.cpp:317:1 start: ./example.cpp:317:1 finish: ./example.cpp:317:1> $1 = void Guess the nop in there is added because of targetm.cxx.cdtor_returns_this. The NOP_EXPR is created by: else if (call != error_mark_node && DECL_DESTRUCTOR_P (cand->fn) && !VOID_TYPE_P (TREE_TYPE (call))) /* An explicit call of the form "x->~X()" has type "void". However, on platforms where destructors return "this" (i.e., those where targetm.cxx.cdtor_returns_this is true), such calls will appear to have a return value of pointer type to the low-level call machinery. We do not want to change the low-level machinery, since we want to be able to optimize "delete f()" on such platforms as "operator delete(~X(f()))" (rather than generating "t = f(), ~X(t), operator delete (t)"). */ call = build_nop (void_type_node, call);
next prev parent reply other threads:[~2021-03-08 9:54 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-08 9:26 [Bug c++/99459] New: " jakub at gcc dot gnu.org 2021-03-08 9:30 ` [Bug c++/99459] " clyon at gcc dot gnu.org 2021-03-08 9:35 ` jakub at gcc dot gnu.org 2021-03-08 9:54 ` jakub at gcc dot gnu.org [this message] 2021-03-08 9:54 ` jakub at gcc dot gnu.org 2021-03-08 9:55 ` jakub at gcc dot gnu.org 2021-03-08 9:56 ` iains at gcc dot gnu.org 2021-03-08 9:59 ` iains at gcc dot gnu.org 2021-03-08 10:01 ` rguenth at gcc dot gnu.org 2021-03-08 10:03 ` iains at gcc dot gnu.org 2021-03-08 10:08 ` jakub at gcc dot gnu.org 2021-03-08 14:27 ` iains at gcc dot gnu.org 2021-03-08 14:38 ` jakub at gcc dot gnu.org 2021-03-09 11:55 ` jakub at gcc dot gnu.org 2021-03-09 15:46 ` cvs-commit at gcc dot gnu.org 2021-03-09 15:48 ` jakub 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-99459-4-QUWIoTLEM8@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).