On 12/20/22 14:39, Richard Biener wrote:
Am 20.12.2022 um 18:38 schrieb Jason Merrill :
On 12/20/22 07:07, Richard Biener wrote:
On Fri, Dec 2, 2022 at 4:46 PM Jason Merrill via Gcc-patches
wrote:
Tested x86_64-pc-linux-gnu, OK for trunk?
-- 8< --
If the DECL_VALUE_EXPR of a VAR_DECL ha
> Am 20.12.2022 um 18:38 schrieb Jason Merrill :
>
> On 12/20/22 07:07, Richard Biener wrote:
>>> On Fri, Dec 2, 2022 at 4:46 PM Jason Merrill via Gcc-patches
>>> wrote:
>>>
>>> Tested x86_64-pc-linux-gnu, OK for trunk?
>>>
>>> -- 8< --
>>>
>>> If the DECL_VALUE_EXPR of a VAR_DECL has EXPR
On 12/20/22 07:07, Richard Biener wrote:
On Fri, Dec 2, 2022 at 4:46 PM Jason Merrill via Gcc-patches
wrote:
Tested x86_64-pc-linux-gnu, OK for trunk?
-- 8< --
If the DECL_VALUE_EXPR of a VAR_DECL has EXPR_LOCATION set, then any use of
that variable looks like it has that location, which lea
On Fri, Dec 2, 2022 at 4:46 PM Jason Merrill via Gcc-patches
wrote:
>
> Tested x86_64-pc-linux-gnu, OK for trunk?
>
> -- 8< --
>
> If the DECL_VALUE_EXPR of a VAR_DECL has EXPR_LOCATION set, then any use of
> that variable looks like it has that location, which leads to the debugger
> jumping back
Ping.
On 12/2/22 10:45, Jason Merrill wrote:
Tested x86_64-pc-linux-gnu, OK for trunk?
-- 8< --
If the DECL_VALUE_EXPR of a VAR_DECL has EXPR_LOCATION set, then any use of
that variable looks like it has that location, which leads to the debugger
jumping back and forth for both lambdas and str
Tested x86_64-pc-linux-gnu, OK for trunk?
-- 8< --
If the DECL_VALUE_EXPR of a VAR_DECL has EXPR_LOCATION set, then any use of
that variable looks like it has that location, which leads to the debugger
jumping back and forth for both lambdas and structured bindings.
Rather than fix all the uses,
