On 1/31/24 03:51, Richard Biener wrote:
On Wed, Jan 31, 2024 at 4:38 AM Jason Merrill wrote:
Tested x86_64-pc-linux-gnu, OK for trunk?
It's a quite "late" fixup, I suppose you have tried to avoid marking it
during gimplification? I see we do parts of this during BIND_EXPR
processing which
On Wed, Jan 31, 2024 at 09:51:05AM +0100, Richard Biener wrote:
> On Wed, Jan 31, 2024 at 4:38 AM Jason Merrill wrote:
> >
> > Tested x86_64-pc-linux-gnu, OK for trunk?
>
> It's a quite "late" fixup, I suppose you have tried to avoid marking it
> during gimplification? I see we do parts of this
On Wed, Jan 31, 2024 at 4:38 AM Jason Merrill wrote:
>
> Tested x86_64-pc-linux-gnu, OK for trunk?
It's a quite "late" fixup, I suppose you have tried to avoid marking it
during gimplification? I see we do parts of this during BIND_EXPR
processing which is indeed a bit early but possibly
Tested x86_64-pc-linux-gnu, OK for trunk?
-- 8< --
Since my r14-1500-g4d935f52b0d5c0 we promote an initializer_list backing
array to static storage where appropriate, but this happens after we decided
to add it to asan_poisoned_variables. As a result we add unpoison/poison
for it to the gimple.
