home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.lang.c:11602 comp.lang.c++:11553
- Path: sparky!uunet!nwnexus!ole!rwing!fnx!nazgul!bright
- From: bright@nazgul.UUCP (Walter Bright)
- Newsgroups: comp.lang.c,comp.lang.c++
- Subject: Re: malloc/new memory allocatio overhead?
- Message-ID: <856@nazgul.UUCP>
- Date: 25 Jul 92 17:42:30 GMT
- References: <1992Jul14.132746.23256@ncsu.edu>
- Reply-To: bright@nazgul.UUCP (Walter Bright)
- Followup-To: comp.lang.c
- Organization: Zortech, Seattle
- Lines: 7
-
- In article <1992Jul14.132746.23256@ncsu.edu> odkahn@eos.ncsu.edu (Opher D. Kahn) writes:
- /Does anybody know exactly what memory allocation overhead results
- /from a new or malloc?
-
- With Zortech C/C++, the malloc'd size is rounded up to the nearest 2/4
- byte boundary, and then 2/4 bytes are added (for the size). Whether
- it is 2 or 4 depends on if it is a 16 or 32 bit program.
-