Hi,
On Tue, Jan 08, 2013 at 02:32:24PM +0100, Richard Biener wrote:
> On Tue, Jan 8, 2013 at 2:29 PM, Martin Jambor wrote:
> > Hi,
> >
> > On Mon, Jan 07, 2013 at 01:26:23AM +0100, Jan Hubicka wrote:
> >> Hi,
> >> as discused in the PR log there seems to be ordering issue in
> >> update_indirect_
On Tue, Jan 8, 2013 at 2:29 PM, Martin Jambor wrote:
> Hi,
>
> On Mon, Jan 07, 2013 at 01:26:23AM +0100, Jan Hubicka wrote:
>> Hi,
>> as discused in the PR log there seems to be ordering issue in
>> update_indirect_edges_after_inlining that first updates info in call edge to
>> correspond the situ
Hi,
On Mon, Jan 07, 2013 at 01:26:23AM +0100, Jan Hubicka wrote:
> Hi,
> as discused in the PR log there seems to be ordering issue in
> update_indirect_edges_after_inlining that first updates info in call edge to
> correspond the situation after inlining and then it tries to devirtualize that
> i
Hi,
as discused in the PR log there seems to be ordering issue in
update_indirect_edges_after_inlining that first updates info in call edge to
correspond the situation after inlining and then it tries to devirtualize that
is trying to look up the info prior inlining.
Bootstrapped/regtested x86_64-
