On Mon, May 17, 2021 at 5:33 PM Joern Rennecke
wrote:
>
> On Mon, 17 May 2021 at 11:59, Richard Biener
> wrote:
>
> > The plan for reload is to axe it similar to CC0 support. Sooner than
> > later, but
> > give it's still used exclusively by a lot of target means it might
> > take some time.
>
On Mon, 17 May 2021 at 11:59, Richard Biener wrote:
> The plan for reload is to axe it similar to CC0 support. Sooner than later,
> but
> give it's still used exclusively by a lot of target means it might
> take some time.
> So for you it's always just -fretry-compilation -m[no-]lra? Given -m
On Mon, May 17, 2021 at 10:55 AM Joern Rennecke
wrote:
>
> On Mon, 17 May 2021 at 08:36, Richard Biener
> wrote:
> >
> > On Sun, May 16, 2021 at 8:53 PM Joern Rennecke
> > wrote:
> > >
> > > For architectures with likely spilled register classes, neither
> > > register allocator is guaranteed
>
On 16 May 2021 20:21:13 CEST, Joern Rennecke
wrote:
>The attached patch adds a new option -fretry-compilation that allows
>you to specify a list - or
>lists - of options to use for a compilation retry, which is
>implemented in the compiler driver.
That's gross ;)
+If the compiler fails, retry
On Mon, 17 May 2021 at 08:36, Richard Biener wrote:
>
> On Sun, May 16, 2021 at 8:53 PM Joern Rennecke
> wrote:
> >
> > For architectures with likely spilled register classes, neither
> > register allocator is guaranteed
> > to succeed when using optimization. If you have just a few files to
> >
On Sun, May 16, 2021 at 8:53 PM Joern Rennecke
wrote:
>
> For architectures with likely spilled register classes, neither
> register allocator is guaranteed
> to succeed when using optimization. If you have just a few files to
> compile, you can try
> by hand which compiler options will succeed a
