Re: memcpy vs. gcc strict aliasing

[Ken Hornstein <kenh%cmf.nrl.navy.mil@localhost>]

>>(A side note - does it make sense to have lint use it's own allocator?  Could
>>it not simply use malloc()?  Are the memory demands by lint that large?)
>
>Which allocator would that be? I think it just wraps malloc.

Actually, it doesn't.  It does make some calls to malloc for some
things, for other things it calls mmap() directly to get memory and
then does some malloc-like pool management.

(see src/usr.bin/xlint/common/mem.c and src/usr.bin/xlint/lint1/mem1.c).

--Ken