C++ use of Malloc/Realloc and Free

[gaf at blu.org (Jerry Feldman)]

On 24 Jun 2003 15:07:49 -0400
kclark at CetaceanNetworks.com (Kevin D. Clark) wrote:

> Ah, so we agree then -- excellent!
We ceretainly do. I just spent 3 years on a team porting Purify to Tru64
Unix. There were many endian problems. The bit map was maintained as big
endian, and accessed both by byte and by int. When accessed by int, I
had to do the appropriate endian conversion. For speed I did it in
assembler. 

Additionally, some compilers (like the DECC/Alpha) like to load bytes
and words using 64 bit quads (or 32 bit longwords). Even long after byte
and word instructions were added to the processor. (HP-UX and Solaris
compilers do similar things). So, trying to figure out whether the load
is a quad, long, word or byte is difficult. 



-- 
Jerry Feldman <gaf at blu.org>
Boston Linux and Unix user group
http://www.blu.org PGP key id:C5061EA9
PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.blu.org/pipermail/discuss/attachments/20030624/77fdae45/attachment.sig>