Mail Archives: djgpp-workers/2000/09/14/11:51:57
> The existence of both end and _end is historical and typical of older
> unix platforms.
Ok. The right fix seems to be removing _end from djgpp.djl. At the
same time I suggest we remove _etext and _edata as well. They have
similar detrimental effects if user code suddenly decides to use
variables with the names etext or edata.
libc compiles and works fine after this patch, so it should be right.
Right,
MartinS
--- djgpp.urg/lib/djgpp.djl Fri Jul 30 03:50:42 1999
+++ djgpp/lib/djgpp.djl Thu Sep 14 15:43:59 2000
@@ -6,8 +6,8 @@ SECTIONS
*(.text)
*(.gnu.linkonce.t*)
*(.gnu.linkonce.r*)
- etext = . ; _etext = .;
- . = ALIGN(0x200);
+ etext = . ;
+ . = ALIGN(0x200);
}
.data ALIGN(0x200) : {
djgpp_first_ctor = . ;
@@ -23,7 +23,7 @@ SECTIONS
*(.eh_fram*)
___EH_FRAME_END__ = . ;
LONG(0)
- edata = . ; _edata = .;
+ edata = . ;
. = ALIGN(0x200);
}
.bss SIZEOF(.data) + ADDR(.data) :
@@ -32,7 +32,7 @@ SECTIONS
. += 24 ;
*(.bss)
*(COMMON)
- end = . ; _end = .;
+ end = . ;
. = ALIGN(0x200);
}
}
- Raw text -