> On Mon, Oct 3, 2011 at 9:52 AM, Jan Hubicka wrote:
> >> This caused:
> >>
> >> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50601
> > Hi,
> > do you use linker with V2 API?
> >
>
> No.
Hi,
the problem is that partitioning algorithm forgets about the aliase and don't
put it into any partition.
I
On Mon, Oct 3, 2011 at 9:52 AM, Jan Hubicka wrote:
>> This caused:
>>
>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50601
> Hi,
> do you use linker with V2 API?
>
No.
--
H.J.
> This caused:
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50601
Hi,
do you use linker with V2 API?
Honza
>
> --
> H.J.
On Wed, Sep 28, 2011 at 5:29 AM, Jan Hubicka wrote:
> Hi,
> this patch adds support for V2 plugin API (thanks, Cary) that adds
> LDPR_PREVAILING_DEF_IRONLY_EXP.
> The reoslution is like LDPR_PREVAILING_DEF_IRONLY but the symbol is exported
> out of DSO. It is up to the compiler
On Wed, 28 Sep 2011, Jan Hubicka wrote:
> Hi,
> this patch adds support for V2 plugin API (thanks, Cary) that adds
> LDPR_PREVAILING_DEF_IRONLY_EXP.
> The reoslution is like LDPR_PREVAILING_DEF_IRONLY but the symbol is exported
> out of DSO. It is up to the compiler to optimize it
Hi,
this patch adds support for V2 plugin API (thanks, Cary) that adds
LDPR_PREVAILING_DEF_IRONLY_EXP.
The reoslution is like LDPR_PREVAILING_DEF_IRONLY but the symbol is exported
out of DSO. It is up to the compiler to optimize it out or keep it based on
the knowledge whether the symbol can be