public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug tree-optimization/78528] Recursion not optimized for structs
[not found] <bug-78528-4@http.gcc.gnu.org/bugzilla/>
@ 2021-06-03 4:52 ` pinskia at gcc dot gnu.org
0 siblings, 0 replies; only message in thread
From: pinskia at gcc dot gnu.org @ 2021-06-03 4:52 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78528
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
tailr1:
D.2500 = strlen (_2);
<bb 5> :
lhs$m_value_10 = D.2500.m_value;
_14 = lhs$m_value_10 + 1;
D.2496.m_value = _14;
<bb 6> :
return D.2496;
For tailr on structures we only allow for structure copies and nothing else.
For an example, if we remove the + 1 part, we do get the tail recursion. Now
the question becomes is it worth the effect in doing it.
clang can handle this case because they handle structures at a lower level than
GCC does.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-06-03 4:52 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-78528-4@http.gcc.gnu.org/bugzilla/>
2021-06-03 4:52 ` [Bug tree-optimization/78528] Recursion not optimized for structs pinskia at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).