> Hi,
>
> On Wed, Oct 30 2019, Jan Hubicka wrote:
> >>
> >> Looking at PR 92278, I think I found the real problem. In
> >> ipa_read_edge_info, you added code to throw away jump functions of edges
> >> that do not pass possibly_call_in_translation_unit_p() test. But that
> >> predicate incorrectl
Hi,
On Wed, Oct 30 2019, Jan Hubicka wrote:
>>
>> Looking at PR 92278, I think I found the real problem. In
>> ipa_read_edge_info, you added code to throw away jump functions of edges
>> that do not pass possibly_call_in_translation_unit_p() test. But that
>> predicate incorrectly - or at least
Hi again, now also CCing the mailing list,
On Wed, Oct 30 2019, Jan Hubicka wrote:
>> Hi,
>>
>> On Wed, Oct 30 2019, Jan Hubicka wrote:
>> > Hi,
>> > this patch fixes another place we may have missing argument summary.
>> > Here the situation is that the call site being inlined has no jump
>> >
On Wed, Oct 30, 2019 at 1:06 PM Martin Jambor wrote:
>
> Hi,
>
> On Wed, Oct 30 2019, Jan Hubicka wrote:
> > Hi,
> > this patch fixes another place we may have missing argument summary.
> > Here the situation is that the call site being inlined has no jump
> > functions while function which is bei
Hi,
On Wed, Oct 30 2019, Jan Hubicka wrote:
> Hi,
> this patch fixes another place we may have missing argument summary.
> Here the situation is that the call site being inlined has no jump
> functions while function which is being inlines has another call with
> jump function. This can validly h
Hi,
this patch fixes another place we may have missing argument summary.
Here the situation is that the call site being inlined has no jump
functions while function which is being inlines has another call with
jump function. This can validly happen when we inline into functions
with indirect inlin
