public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99215] coroutines: debugging with gdb
Date: Fri, 09 Jul 2021 18:14:26 +0000	[thread overview]
Message-ID: <bug-99215-4-oHYIAlhGJW@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 #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Iain D Sandoe <iains@gcc.gnu.org>:

https://gcc.gnu.org/g:d5b1bb0d197f9141a0f0e510f8d1b598c3df9552

commit r12-2229-gd5b1bb0d197f9141a0f0e510f8d1b598c3df9552
Author: Iain Sandoe <iain@sandoe.co.uk>
Date:   Wed Jul 7 19:56:20 2021 +0100

    coroutines: Factor code. Match original source location in helpers [NFC].

    This is primarily a source code refactoring, the only change is to
    ensure that the outlined functions are marked to begin at the same
    line as the original.  Otherwise, they get the default (which seems
    to be input_location, which corresponds to the closing brace at the
    point that this is done).  Having the source location point to that
    confuses some debuggers.

    This is a contributory fix to:
    PR c++/99215 - coroutines: debugging with gdb

    Signed-off-by: Iain Sandoe <iain@sandoe.co.uk>

    gcc/cp/ChangeLog:

            * coroutines.cc (build_actor_fn): Move common code to
            act_des_fn.
            (build_destroy_fn): Likewise.
            (act_des_fn): Build the void return here.  Ensure that the
            source location matches the original function.

  parent reply	other threads:[~2021-07-09 18:14 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
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 [this message]
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-oHYIAlhGJW@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).