On Wed, 24 May 2023 at 12:41, Richard Biener wrote:
> On Wed, 24 May 2023, Christophe Lyon wrote:
>
> > Hi Richard,
> >
> > On Tue, 23 May 2023 at 11:55, Richard Biener via Gcc-patches <
> > gcc-patches@gcc.gnu.org> wrote:
> >
> > > The following fixes code hoisting to properly consider ANTIC_OUT
On Wed, 24 May 2023, Christophe Lyon wrote:
> Hi Richard,
>
> On Tue, 23 May 2023 at 11:55, Richard Biener via Gcc-patches <
> gcc-patches@gcc.gnu.org> wrote:
>
> > The following fixes code hoisting to properly consider ANTIC_OUT instead
> > of ANTIC_IN. That's a bit expensive to re-compute but
Hi Richard,
On Tue, 23 May 2023 at 11:55, Richard Biener via Gcc-patches <
gcc-patches@gcc.gnu.org> wrote:
> The following fixes code hoisting to properly consider ANTIC_OUT instead
> of ANTIC_IN. That's a bit expensive to re-compute but since we no
> longer iterate we're doing this only once pe
The following fixes code hoisting to properly consider ANTIC_OUT instead
of ANTIC_IN. That's a bit expensive to re-compute but since we no
longer iterate we're doing this only once per BB which should be
acceptable. This avoids missing hoistings to the end of blocks where
something in the block c
