2015-12-16 10:08 GMT+03:00 Senthil Kumar Selvaraj
:
> Hi,
>
> When analyzing code size regressions for AVR for top-of-trunk, I
> found a few cases where aggresive inlining (by the middle-end)
> of functions containing calls to memcpy was bloating up the code.
>
> Turns out that the AVR back
Hi,
When analyzing code size regressions for AVR for top-of-trunk, I
found a few cases where aggresive inlining (by the middle-end)
of functions containing calls to memcpy was bloating up the code.
Turns out that the AVR backend has MOVE_MAX set to 4 (unchanged from the
original commit