On Sat, Aug 31, 2019 at 02:17:30PM -0500, Segher Boessenkool wrote:
> Hi all,
>
> On Sat, Mar 23, 2019 at 11:46:12PM +, Segher Boessenkool wrote:
> > CSE does not consider calls, not even const calls. This patch puts a
> > REG_EQUAL note on the pseudo we assign the __tls_get_addr result to,
>
Hi all,
On Sat, Mar 23, 2019 at 11:46:12PM +, Segher Boessenkool wrote:
> CSE does not consider calls, not even const calls. This patch puts a
> REG_EQUAL note on the pseudo we assign the __tls_get_addr result to,
> so that those pseudos can be CSE'd and the extra calls deleted as dead
> code
> There were REG_EQUAL notes on these tls calls in the past, but I
> recall removing them for one reason or another. So watch out for
> fall-out from this patch! ;-)
Others ports have them though, for example i386, ARM and SPARC.
--
Eric Botcazou
Hi Steven,
On Sun, Mar 24, 2019 at 11:02:20AM +0100, Steven Bosscher wrote:
> On Sun, Mar 24, 2019 at 12:46 AM Segher Boessenkool wrote:
> >
> > CSE does not consider calls, not even const calls. This patch puts a
> > REG_EQUAL note on the pseudo we assign the __tls_get_addr result to,
> > so tha
On Sun, Mar 24, 2019 at 12:46 AM Segher Boessenkool wrote:
>
> CSE does not consider calls, not even const calls. This patch puts a
> REG_EQUAL note on the pseudo we assign the __tls_get_addr result to,
> so that those pseudos can be CSE'd and the extra calls deleted as dead
> code.
Hi Segher,
T
CSE does not consider calls, not even const calls. This patch puts a
REG_EQUAL note on the pseudo we assign the __tls_get_addr result to,
so that those pseudos can be CSE'd and the extra calls deleted as dead
code.
CSE should really handle const calls directly, but it is stage 4.
Tested on power
