public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/115201] Recursive binary search with struct iterator is not handled by tail Recursion Date: Thu, 23 May 2024 03:01:40 +0000 [thread overview] Message-ID: <bug-115201-4-xyRWBgVeMe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115201-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115201 --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Created attachment 58274 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58274&action=edit Slightly more reduced Slightly more reduced, foo3 should produce the same as foo4. Basically Tailr does not handle recusive calls with struct arguments really.
next prev parent reply other threads:[~2024-05-23 3:01 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-23 1:41 [Bug tree-optimization/115201] New: Recursive binary search is incorrectly inlined llvm at rifkin dot dev 2024-05-23 1:54 ` [Bug ipa/115201] " pinskia at gcc dot gnu.org 2024-05-23 2:04 ` llvm at rifkin dot dev 2024-05-23 2:10 ` pinskia at gcc dot gnu.org 2024-05-23 2:11 ` pinskia at gcc dot gnu.org 2024-05-23 2:13 ` [Bug tree-optimization/115201] Recursive binary search with struct iterator is not handled by tail Recursion pinskia at gcc dot gnu.org 2024-05-23 3:01 ` pinskia at gcc dot gnu.org [this message] 2024-05-23 3:26 ` [Bug tree-optimization/115201] Recursion not optimized for structs arguments pinskia at gcc dot gnu.org 2024-05-23 3:29 ` pinskia at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-115201-4-xyRWBgVeMe@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).