AM
> To: Gary Oblock
> Cc: Jan Hubicka ; gcc@gcc.gnu.org
> Subject: Re: [EXT] Re: Comparing types at LTO time
>
> On Thu, Jan 9, 2020 at 9:36 PM Gary Oblock wrote:
> >
> > Richard,
> >
> > Alas, when doing structure reorg I have to be able to know s
Oblock
Cc: Jan Hubicka ; gcc@gcc.gnu.org
Subject: Re: [EXT] Re: Comparing types at LTO time
On Thu, Jan 9, 2020 at 9:36 PM Gary Oblock wrote:
>
> Richard,
>
> Alas, when doing structure reorg I have to be able to know some
> arbitrary use of variable X in some GIMPLE expression
me
extent (worst case by providing a copy in/out to a temporary with the
old layout).
Richard.
>
> From: Richard Biener
> Sent: Thursday, January 9, 2020 3:51 AM
> To: Jan Hubicka
> Cc: Gary Oblock ; gcc@gcc.gnu.org
> Subject: [EXT] Re: Compari
, January 9, 2020 3:51 AM
To: Jan Hubicka
Cc: Gary Oblock ; gcc@gcc.gnu.org
Subject: [EXT] Re: Comparing types at LTO time
External Email
--
On Thu, Jan 9, 2020 at 9:53 AM Jan Hubicka wrote:
>
> > There doesn't seem to
On Thu, Jan 9, 2020 at 9:53 AM Jan Hubicka wrote:
>
> > There doesn't seem to be a way to compare types at LTO time. The functions
> > same_type_p and comptypes are front end only if I'm not totally confused
> > (which is quite possible) and type_hash_eq doesn't seem to apply for
> > structure
> There doesn't seem to be a way to compare types at LTO time. The functions
> same_type_p and comptypes are front end only if I'm not totally confused
> (which is quite possible) and type_hash_eq doesn't seem to apply for
> structure types. Please, any advice would be welcome.
At LTO time it is
There doesn't seem to be a way to compare types at LTO time. The functions
same_type_p and comptypes are front end only if I'm not totally confused
(which is quite possible) and type_hash_eq doesn't seem to apply for
structure types. Please, any advice would be welcome.
Thanks,
Gary Oblock
