Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!uunet!tut.cis.ohio-state.edu!ucbvax!dog.ee.lbl.gov!elf.ee.lbl.gov!torek
From: torek@elf.ee.lbl.gov (Chris Torek)
Newsgroups: comp.lang.c
Subject: alloca (was Alloca for Turbo C)
Keywords: memory allocation
Message-ID: <10528@dog.ee.lbl.gov>
Date: 3 Mar 91 06:39:53 GMT
References: <91026.223149ACPS2924@Ryerson.Ca> <51339@cornell.UUCP>
Reply-To: torek@elf.ee.lbl.gov (Chris Torek)
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 15
X-Local-Date: Sat, 2 Mar 91 22:39:53 PST

In article <51339@cornell.UUCP> ressler@cs.cornell.edu (Gene Ressler) writes:
>I'm asking those who are really familiar with the TC's code generator 
>if they know of other dangers e.g. functions with no locals,
>tail calls, nested blocks with locals, and so on. ...

This sort of thing is exactly why (choose all that apply):

    (a) alloca should never be used;
    (b) alloca must be built into the compiler;
    (c) using alloca makes code less portable.

(Note that different people will choose different sets.)
-- 
In-Real-Life: Chris Torek, Lawrence Berkeley Lab EE div (+1 415 486 5427)
Berkeley, CA		Domain:	torek@ee.lbl.gov