https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104405
--- Comment #8 from Eric Botcazou ---
> There is of course the option to switch to alternate heuristics if, by
> heuristic, the argument/return part of the function is a big part of it (aka
> for toy examples or small functions which do happen i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104405
--- Comment #7 from Richard Biener ---
(In reply to Eric Botcazou from comment #6)
> > But seems to me a simple enough thing that we should be able to handle.
>
> Register allocation is a global problem though, so what happens on toy
> examples
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104405
Eric Botcazou changed:
What|Removed |Added
Severity|normal |enhancement
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104405
--- Comment #5 from Andrew Pinski ---
(In reply to Tamar Christina from comment #4)
> But seems to me a simple enough thing that we should be able to handle.
It looks simple but register allocation especially with demands on some things
in spec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104405
--- Comment #4 from Tamar Christina ---
(In reply to Andrew Pinski from comment #2)
> The big question becomes now is really an issue in real world code or just a
> toy benchmark which is testing argument/return passing optimizations?
Can't say
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104405
Andrew Pinski changed:
What|Removed |Added
Component|middle-end |rtl-optimization
Blocks|101
