>>>> "JV" == Jan Vroonhof
<vroonhof(a)math.ethz.ch> writes:
JV> Simon Josefsson <jas(a)pdc.kth.se> writes:
> Perhaps I should start by seeing what problems there might be
> compiling it with gcc then? :-) I'll do that now.
JV> This is Max Matveev describing the invariant his code is expecting.
JV> Does that hold when compiling with gcc?
Sounds like a question of which _linker_ is used, not which compiler.
Which one gcc uses is determined by the --with-gnu-ld flag used when
configuring gcc. The system ld comes for free, so folks are more
likely to install gcc than gnu ld (part of binutils).
JV> 1999-12-28 Max Matveev <max(a)melbourne.sgi.com>
JV> * unexelfsgi.c (unexec): Change the way we decide which segment
JV> should be extended.
JV> Assumption that .bss section should be outside the PT_LOADable
JV> segment. On IRIX with version 6.2 and above, .bss (or .sbss, if
JV> it's present) is inside the 'data' segment. This would fail the
JV> test which was used to find a segment to grow and cover new
JV> heap. Instead of this assumption, I created another one - on IRIX
JV> the segment to grow should start below .bss and it's address
JV> should extent above the end of .bss. Once this segment is
JV> identified, it's grown to accommodate the new heap and new
JV> zero-length .bss section is added at the end of .data2.