Re: [PATCH 2/2] Avoid registering __builtin_setjmp_receiver label twice [PR101347]

2022-07-20 Thread Alexander Monakov via Gcc-patches
On Wed, 20 Jul 2022, Eric Botcazou wrote: > > Eric is probably most familiar with this, but can you make sure to bootstrap > > and test this on a SJLJ EH target? I'm not sure --enable-sjlj-exceptions > > is well tested anywhere but on targets not supporting DWARF EH and the > > configury is a b

Re: [PATCH 2/2] Avoid registering __builtin_setjmp_receiver label twice [PR101347]

2022-07-20 Thread Eric Botcazou via Gcc-patches
> Eric is probably most familiar with this, but can you make sure to bootstrap > and test this on a SJLJ EH target? I'm not sure --enable-sjlj-exceptions > is well tested anywhere but on targets not supporting DWARF EH and the > configury is a bit odd suggesting the option is mostly ignored ... T

Re: [PATCH 2/2] Avoid registering __builtin_setjmp_receiver label twice [PR101347]

2022-07-20 Thread Richard Biener via Gcc-patches
On Tue, Jul 19, 2022 at 5:17 PM Alexander Monakov via Gcc-patches wrote: > > The testcase in the PR demonstrates how it is possible for one > __builtin_setjmp_receiver label to appear in > nonlocal_goto_handler_labels list twice (after the block with > __builtin_setjmp_setup referring to it was du

[PATCH 2/2] Avoid registering __builtin_setjmp_receiver label twice [PR101347]

2022-07-19 Thread Alexander Monakov via Gcc-patches
The testcase in the PR demonstrates how it is possible for one __builtin_setjmp_receiver label to appear in nonlocal_goto_handler_labels list twice (after the block with __builtin_setjmp_setup referring to it was duplicated). remove_node_from_insn_list did not account for this possibility and remo