From: Richard Henderson <rth@cygnus.com>
To: Geert Bosch <bosch@gnat.com>
Cc: Bruno Haible <haible@ilog.fr>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: tail call optimization vs. debugging
Date: Sat, 25 Mar 2000 11:35:00 -0000 [thread overview]
Message-ID: <20000325113529.C21318@cygnus.com> (raw)
In-Reply-To: <20000325171727.D8EFD34D80@nile.gnat.com>
On Sat, Mar 25, 2000 at 12:18:25PM -0500, Geert Bosch wrote:
> Here are a few yes/no debugging questions that popped up for me:
> - Will function breakpoints be hit by a tail call or sibcall?
Yes.
> - In recursive functions, will printing arguments show the argument values
> of the last (recursive) call?
On pure tail calls, yes. The new arguments get put exactly where
they should have been for a normal call.
With tail recursion (which we had before, but will trigger more often
now) I can only say "probably". It's implemented with a goto internally,
so the optimizer has the chance to not put the new arguments in place.
> - Do cases where unbounded recursion (due to tail call optimizations)
> only show a few frames in a trace-back always use bounded stack space?
Eh? If I understand the question correctly, of course.
How else could it be a tail call optimization?
r~
next prev parent reply other threads:[~2000-03-25 11:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-25 9:17 Geert Bosch
2000-03-25 11:35 ` Richard Henderson [this message]
2000-03-25 12:54 ` Martin v. Loewis
-- strict thread matches above, loose matches on Subject: below --
2000-03-25 13:08 Geert Bosch
2000-03-25 14:07 ` Richard Henderson
2000-03-24 12:39 Bruno Haible
2000-03-24 14:03 ` Daniel Berlin+list.gcc
2000-03-24 14:24 ` Richard Henderson
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=20000325113529.C21318@cygnus.com \
--to=rth@cygnus.com \
--cc=bosch@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=haible@ilog.fr \
/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: link
Be 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).