https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51982
--- Comment #5 from Segher Boessenkool ---
Yes, the only two calls in the resulting machine code are both to unicode_eq.
Splitting the ranges (and then assigning volatile regs to the first half)
hurts if it doesn't end up helping shrink-wrapping
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51982
--- Comment #4 from Peter Bergner ---
(In reply to David Edelsohn from comment #3)
> The function lookup_unicode should be shrink-wrapped to not create a stack
> frame if unicode_eq is not called, which is the common case
>
> if (!PyUnicode_
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51982
Bug 51982 depends on bug 10474, which changed state.
Bug 10474 Summary: shrink wrapping for functions
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10474
What|Removed |Added
---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51982
--- Comment #3 from David Edelsohn 2013-04-21 23:26:03
UTC ---
Created attachment 29912
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29912
self-contained example
The function lookup_unicode should be shrink-wrapped to not create
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51982
Alan Modra changed:
What|Removed |Added
CC|amodra at gcc dot gnu.org |amodra at gmail dot com
--- Comment #2 from
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51982
Andrew Pinski changed:
What|Removed |Added
Depends on||10474
--- Comment #1 from Andrew Pinski
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51982
David Edelsohn changed:
What|Removed |Added
Keywords||missed-optimization
Status|U
