https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99215
--- Comment #14 from Jarrod Smith ---
I've been following this and experiencing the issue in gcc 10.2. I still see
"" for all variables when debugging C++20 coroutines with gcc
11.2.
Is there a workaround (e.g. using a certain branch of gcc) in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99215
--- Comment #13 from CVS Commits ---
The releases/gcc-10 branch has been updated by Iain D Sandoe
:
https://gcc.gnu.org/g:ddef3142151a3e88743aa4a990062d953a16c04e
commit r10-10164-gddef3142151a3e88743aa4a990062d953a16c04e
Author: Iain Sandoe
D
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99215
--- Comment #12 from Iain Sandoe ---
also :
https://gcc.gnu.org/pipermail/gcc-cvs/2021-September/352947.html
https://gcc.gnu.org/pipermail/gcc-cvs/2021-September/352948.html
https://gcc.gnu.org/pipermail/gcc-cvs/2021-September/352949.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99215
--- Comment #11 from CVS Commits ---
The releases/gcc-11 branch has been updated by Iain D Sandoe
:
https://gcc.gnu.org/g:feef2e414d45f732509ab044d4ad14aed125b024
commit r11-8786-gfeef2e414d45f732509ab044d4ad14aed125b024
Author: Iain Sandoe
Da
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99215
--- Comment #10 from CVS Commits ---
The master branch has been updated by Iain D Sandoe :
https://gcc.gnu.org/g:d5b1bb0d197f9141a0f0e510f8d1b598c3df9552
commit r12-2229-gd5b1bb0d197f9141a0f0e510f8d1b598c3df9552
Author: Iain Sandoe
Date: Wed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99215
--- Comment #9 from Iain Sandoe ---
(In reply to Iain Sandoe from comment #8)
> (In reply to Nils Gladitz from comment #7)
> > (In reply to Nils Gladitz from comment #5)
> > > Apparently when the coroutine happens to be a member function (even a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99215
--- Comment #8 from Iain Sandoe ---
(In reply to Nils Gladitz from comment #7)
> (In reply to Nils Gladitz from comment #5)
> > Apparently when the coroutine happens to be a member function (even a static
> > one) printing *frame_ptr results in "
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99215
--- Comment #7 from Nils Gladitz ---
(In reply to Nils Gladitz from comment #5)
> Apparently when the coroutine happens to be a member function (even a static
> one) printing *frame_ptr results in "{}".
I reported the "{}" issue at the gdb issue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99215
--- Comment #6 from Iain Sandoe ---
(In reply to Nils Gladitz from comment #5)
> Apparently when the coroutine happens to be a member function (even a static
> one) printing *frame_ptr results in "{}".
>
> Ideally I'd want to have non-static mem
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99215
--- Comment #5 from Nils Gladitz ---
Apparently when the coroutine happens to be a member function (even a static
one) printing *frame_ptr results in "{}".
Ideally I'd want to have non-static member coroutines and would like to be able
to inspec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99215
--- Comment #4 from Nils Gladitz ---
(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 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99215
--- Comment #3 from Iain Sandoe ---
(In reply to Nils Gladitz from comment #2)
> (In reply to Iain Sandoe from comment #1)
> > Can you identify specific key blockers to progress?
> > (I think the paper cited contained a number of desiderata, but
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99215
--- Comment #2 from Nils Gladitz ---
(In reply to Iain Sandoe from comment #1)
> Can you identify specific key blockers to progress?
> (I think the paper cited contained a number of desiderata, but it would be
> good to start from the most import
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99215
Iain Sandoe changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
14 matches
Mail list logo
