Re: [PATCH 5/8] coroutines: Define and populate accessors for debug state.

2021-09-03 Thread Jason Merrill via Gcc-patches
On 9/3/21 9:42 AM, Iain Sandoe wrote: On 3 Sep 2021, at 14:39, Jason Merrill wrote: On 9/1/21 6:54 AM, Iain Sandoe wrote: This is an efficiency measure and repeats the pattern used for other identifiers used in the coroutine implementation. In support of debugging, the user might well need

Re: [PATCH 5/8] coroutines: Define and populate accessors for debug state.

2021-09-03 Thread Iain Sandoe
> On 3 Sep 2021, at 14:39, Jason Merrill wrote: > > On 9/1/21 6:54 AM, Iain Sandoe wrote: >> This is an efficiency measure and repeats the pattern used for >> other identifiers used in the coroutine implementation. >> In support of debugging, the user might well need to look at some >> of the

Re: [PATCH 5/8] coroutines: Define and populate accessors for debug state.

2021-09-03 Thread Iain Sandoe
> On 3 Sep 2021, at 14:39, Jason Merrill wrote: > > On 9/1/21 6:54 AM, Iain Sandoe wrote: >> This is an efficiency measure and repeats the pattern used for >> other identifiers used in the coroutine implementation. >> In support of debugging, the user might well need to look at some >> of the

Re: [PATCH 5/8] coroutines: Define and populate accessors for debug state.

2021-09-03 Thread Jason Merrill via Gcc-patches
On 9/1/21 6:54 AM, Iain Sandoe wrote: This is an efficiency measure and repeats the pattern used for other identifiers used in the coroutine implementation. In support of debugging, the user might well need to look at some of the variables that the implementation manipulates in lowering the

[PATCH 5/8] coroutines: Define and populate accessors for debug state.

2021-09-01 Thread Iain Sandoe
This is an efficiency measure and repeats the pattern used for other identifiers used in the coroutine implementation. In support of debugging, the user might well need to look at some of the variables that the implementation manipulates in lowering the coroutines. The defines the identifiers