Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!virtech!cpcahil
From: cpcahil@virtech.uucp (Conor P. Cahill)
Newsgroups: comp.lang.c
Subject: Re: Separate data and function address spaces
Message-ID: <1989Nov12.152753.9282@virtech.uucp>
Date: 12 Nov 89 15:27:53 GMT
References: <1989Nov10.123033.2494@virtech.uucp> <930@fiver.UUCP>
Organization: Virtual Technologies Inc.
Lines: 27

In article <930@fiver.UUCP>, palowoda@fiver.UUCP (Bob Palowoda) writes:
> From article <1989Nov10.123033.2494@virtech.uucp>, by cpcahil@virtech.uucp (Conor P. Cahill):
> > I don't know what unix you are using, but the System V/386 Unixs use the small
> > model for compiled programs which place the data and text portion into the 
> > same segment.  I have executed out of data space on these systems.  I have
> > even executed out of a shared memory segment.
> 
>   I'm curious, where did you find out that the System V/386 Unixs use the
> small model?  I look through my manuals and cannot find the refernce to
> "models".

I believe it was in the original System V/386 Release 3.0 release notes, but
I no longer have them around and can't check them.  However a check of the
assembly language generated by the C compiler shows that it does no use
any multi-segment function calls and/or data accesses.







-- 
+-----------------------------------------------------------------------+
| Conor P. Cahill     uunet!virtech!cpcahil      	703-430-9247	!
| Virtual Technologies Inc.,    P. O. Box 876,   Sterling, VA 22170     |
+-----------------------------------------------------------------------+