public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nilsgladitz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99215] coroutines: debugging with gdb
Date: Tue, 23 Feb 2021 15:53:29 +0000	[thread overview]
Message-ID: <bug-99215-4-G3y80rwM2W@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99215-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99215

--- Comment #4 from Nils Gladitz <nilsgladitz at gmail dot com> ---
(In reply to Iain Sandoe from comment #3)
> ... the essence of the idea [on the mentioned long TODO] is to change the
> way in which frame vars are referenced; instead of changing the uses to
> point to the frame version, change the vars to have a DECL_VALUE_EXPR
> pointing to the frame version.  This is a totally theoretical sketch (no
> experiments done yet).
> 
> Stated in one sentence, that doesn't sound too tricky .. but maintaining the
> state of the coroutine *is* quite tricky (and lambdas already use the
> DECL_VALUE_EXPRs).

Alright, thank you! Just knowing that this is thought of, on a todo list and
currently not completely inaccessible helps build confidence somewhat; I think
for me enough to try some of this in production code. With some luck you still
get through your todo list faster than I get to my next corresponding release
:)

  parent reply	other threads:[~2021-02-23 15:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23  7:29 [Bug c++/99215] New: " nilsgladitz at gmail dot com
2021-02-23 14:21 ` [Bug c++/99215] " iains at gcc dot gnu.org
2021-02-23 14:59 ` nilsgladitz at gmail dot com
2021-02-23 15:26 ` iains at gcc dot gnu.org
2021-02-23 15:53 ` nilsgladitz at gmail dot com [this message]
2021-02-24 15:03 ` nilsgladitz at gmail dot com
2021-02-24 15:23 ` iains at gcc dot gnu.org
2021-03-22 12:13 ` nilsgladitz at gmail dot com
2021-03-22 12:23 ` iains at gcc dot gnu.org
2021-03-22 12:30 ` iains at gcc dot gnu.org
2021-07-09 18:14 ` cvs-commit at gcc dot gnu.org
2021-07-20  6:55 ` cvs-commit at gcc dot gnu.org
2021-09-03 20:25 ` iains at gcc dot gnu.org
2021-10-03 19:28 ` cvs-commit at gcc dot gnu.org
2022-02-15  2:12 ` jarrod.smith at ardentblue dot com

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-99215-4-G3y80rwM2W@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: link
Be 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).