This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: sibcall/tailcall terminology
- From: Richard Henderson <rth at redhat dot com>
- To: Fergus Henderson <fjh at cs dot mu dot OZ dot AU>
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 17 Sep 2002 08:55:46 -0700
- Subject: Re: sibcall/tailcall terminology
- References: <20020917095910.GA20400@ceres.cs.mu.oz.au>
On Tue, Sep 17, 2002 at 07:59:10PM +1000, Fergus Henderson wrote:
> Proposal A:
> I propose that we use "tail call" to mean (3)
> and "sibling call" to mean (2).
>
> As a consequence:
> - sibcall.c should renamed tailcall.c
> - -foptimize-sibling-calls should be renamed -foptimize-tail-calls
> (or perhaps -foptimize-tailcalls?)
> - try_tail_call in calls.c should be renamed try_sibling_call
While I agree that this would be more consistent, I don't think
it's worth renaming files. And certainly we can't change the
user interface without pain.
r~