Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84 SMI; site sun.uucp Path: utzoo!watmath!clyde!cbosgd!ihnp4!mhuxn!mhuxm!sftig!sftri!sfmag!eagle!ulysses!allegra!bellcore!decvax!decwrl!sun!gnu From: gnu@sun.uucp Newsgroups: net.lang.c Subject: Re: C stack frame > 32K (on a Sun) Message-ID: <1904@sun.uucp> Date: Thu, 27-Dec-84 21:06:33 EST Article-I.D.: sun.1904 Posted: Thu Dec 27 21:06:33 1984 Date-Received: Sat, 29-Dec-84 03:02:26 EST References: <18092@arizona.UUCP> <6255@brl-tgr.ARPA> <1837@sun.uucp> <2951@allegra.UUCP> Organization: Sun Microsystems, Inc. Lines: 13 Mark Plotnick (allegra!mp) says: > Note that if you care about getting correct code out of the SMI C > compiler, you shouldn't use stack frames larger than 32Kbytes. This is > because of a bug in their compiler (at least as of release 1.1, which > is what we have) with the handling of floating point operations that > require scratch areas on the stack. The compiler doesn't seem to know > that displacements, as in reg@(disp), are limited to 16-bit signed > integers. This is true. A more recent version of the compiler (as yet unreleased) gives a compile-time diagnostic rather than a runtime error, and we're working on a fix. Sorry folks...we fixed SOME of the bugs with large stack frames...