Re: How to avoid some built-in expansions in gcc?

[Paul Koning via Gcc]

> On May 31, 2024, at 9:52 AM, Georg-Johann Lay <a...@gjlay.de> wrote:
> 
> What's the recommended way to stop built-in expansions in gcc?
> 
> For example, avr-gcc expands isinff() to a bloated version of an isinff() 
> implementation that's written in asm (PR115307).
> 
> Johann

Isn't that up to the target back end?  It should define the optimization rules, 
and those should allow it to bias towards small code rather than fast big code.

        paul