This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: proper tail recursion for gcc

To: Mark Probst <schani at mips dot complang dot tuwien dot ac dot at>
Subject: Re: proper tail recursion for gcc
From: Richard Henderson <rth at cygnus dot com>
Date: Thu, 20 Jul 2000 13:47:07 -0700
Cc: gcc at gcc dot gnu dot org
References: <20000720020357.M3827@vader.unix.cslab.tuwien.ac.at> <jmpuo949pr.fsf@envy.cygnus.com> <20000720112151.O3827@vader.unix.cslab.tuwien.ac.at> <20000720121215.B16905@cygnus.com> <20000720203711.V3827@vader.unix.cslab.tuwien.ac.at>

On Thu, Jul 20, 2000 at 08:37:11PM +0000, Mark Probst wrote:
> ... but if foo knew that bar might do a tail call to a non-static
> function, it could reload $gp and everything would be fine.

Not unless you communicate that knowledge to the linker
as well, which attempts to remove gp loads that are not
necessary.  Not necessary, that is, if you're following
the ABI rules.

r~

References:
- proper tail recursion for gcc
  - From: Mark Probst
- Re: proper tail recursion for gcc
  - From: Geoff Keating
- Re: proper tail recursion for gcc
  - From: Mark Probst
- Re: proper tail recursion for gcc
  - From: Richard Henderson
- Re: proper tail recursion for gcc
  - From: Mark Probst

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]