Related articles |
---|
[26 earlier articles] |
Re: Using C as a back end rhyde@cs.ucr.edu (Randall Hyde) (2000-11-01) |
Re: Using C as a back end rhyde@cs.ucr.edu (Randall Hyde) (2000-11-01) |
Re: Using C as a back end vbdis@aol.com (2000-11-04) |
Re: Using C as a back end joachim_d@gmx.de (Joachim Durchholz) (2000-11-04) |
Re: Using C as a back end thp@roam-thp2.cs.ucr.edu (Tom Payne) (2000-11-04) |
Re: Using C as a back end gneuner@dyn.com (2000-11-04) |
Re: Using C as a back end fjh@cs.mu.OZ.AU (2000-11-05) |
Re: Using C as a back end freitag@alancoxonachip.com (Andi Kleen) (2000-11-05) |
Re: Using C as a back end christl@rosalind.fmi.uni-passau.de (2000-11-05) |
From: | fjh@cs.mu.OZ.AU (Fergus Henderson) |
Newsgroups: | comp.compilers |
Date: | 5 Nov 2000 20:46:07 -0500 |
Organization: | Computer Science, University of Melbourne |
References: | 00-10-148 00-10-174 00-10-182 00-11-035 |
Keywords: | C, optimize |
gneuner@dyn.com (George Neuner) writes:
>Another way would be to bundle all the state variables into a
>structure and generate a separate, one parameter function for each
>verilog statement which explicitly tail calls the next function. Also
>sounds stupid, but GCC will *sometimes* understand this and optimize
>the function calls away.
Last time I looked, GCC was only capable of doing last call optimization
for functions that tail-call themselves (and even then only in some cases).
So this approach would result in a stack leak.
--
Fergus Henderson <fjh@cs.mu.oz.au> | "I have always known that the pursuit
| of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh> | -- the last words of T. S. Garp.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.