<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="MSHTML 5.00.2920.0" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi.</FONT></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Why does Kaffe (linux) uses sbrk(..) to allocate
memory. According to the man. pages for sbrk(..) it is not very feasible. Why
doesn't Kaffe use malloc(..)?</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>In gc_small_alloc(..) and
gc_large_alloc(..):</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial
size=2>info->funcs=(unitp8*)GCBLOCK2BASE(info);</FONT></DIV>
<DIV><FONT face=Arial
size=2>info->state=(unitp8*)(info->funcs+nr);</FONT></DIV>
<DIV><FONT face=Arial size=2>info->data=....;</FONT></DIV>
<DIV><FONT face=Arial size=2>.</FONT></DIV>
<DIV><FONT face=Arial size=2>What happens here? Where do these pointers point
to. Memory addresses in the heap or to addresses in the space allocated by
malloc for a number of gc_blocks (which is used by the
gc_primary_freelist).</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>The bottom line is, what of the gc_block is put on
the heap?</FONT></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>/johan</FONT></DIV>
<DIV> </DIV>
<DIV> </DIV></BODY></HTML>