public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/59813] tail-call elimintation didn't fired with left-shift of char to cout Date: Wed, 15 Jan 2014 07:23:00 -0000 [thread overview] Message-ID: <bug-59813-4-ZJuG1N5NH6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59813-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59813 --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- If you only care about tail recursion and not tail call optimization, perhaps, but either solution would be very dumb. We now have var ={v} {CLOBBER}; stmts, even if those vars escape and are address taken, if there is a clobber stmt for those vars on every path from the escape point to the tail call candidate, we could perform tail recursion or tail call optimization, what we are really after is that the address of no automatic variable from the current function can escape to the tail recursion/call candidate. As in: void bar (char *); void foo (char *p) { char c; bar (&c); bar (NULL); // We can't tail call optimize this } void baz (char *p) { { char c; bar (&c); } bar (NULL); // We could tail call optimize this }
prev parent reply other threads:[~2014-01-15 7:23 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-14 21:35 [Bug c++/59813] New: " virkony at gmail dot com 2014-01-14 22:05 ` [Bug c++/59813] " virkony at gmail dot com 2014-01-15 0:13 ` pinskia at gcc dot gnu.org 2014-01-15 7:18 ` virkony at gmail dot com 2014-01-15 7:23 ` jakub at gcc dot gnu.org [this message]
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-59813-4-ZJuG1N5NH6@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).