On Thu, Aug 24, 2017 at 1:34 PM, Richard Biener wrote:
> On Thu, 24 Aug 2017, Uros Bizjak wrote:
>
>> On Thu, Aug 24, 2017 at 1:10 PM, Richard Biener wrote:
>> >
>> > This adjusts the x86 backend to allow -mfpmath differences when
>> > deciding whether to allow inlining. -mfpmath doesn't really
On Thu, 24 Aug 2017, Uros Bizjak wrote:
> On Thu, Aug 24, 2017 at 1:10 PM, Richard Biener wrote:
> >
> > This adjusts the x86 backend to allow -mfpmath differences when
> > deciding whether to allow inlining. -mfpmath doesn't really
> > matter for functions not containing FP operations.
> >
> >
On Thu, Aug 24, 2017 at 1:10 PM, Richard Biener wrote:
>
> This adjusts the x86 backend to allow -mfpmath differences when
> deciding whether to allow inlining. -mfpmath doesn't really
> matter for functions not containing FP operations.
>
> It appears that the can_inline_p target hook is called
This adjusts the x86 backend to allow -mfpmath differences when
deciding whether to allow inlining. -mfpmath doesn't really
matter for functions not containing FP operations.
It appears that the can_inline_p target hook is called from the
C++ FE for multi-versioning, thus the ! ipa_fn_summaries