🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.lang.asm.x86
Article #85

Re: DOSSEG and TLINK

#85
From: assassin17
Date: Fri, 21 May 1999 00:00
104 lines
3488 bytes
  bsmith@sudleyplacedespam.com wrote:
> assassin17@rocketmail.com wrote:
[snip]
> > 1. All segments with a class name ending in CODE
> > 2. Far data segments (segments outside DGROUP)
> > 3. Near data (DGROUP) segments, in the following order:
> >       a. Segments of class BEGDATA (reserved for Microsoft use)
> >       b. Any segments not of class BEGDATA, BSS, or STACK
> >       c. Segments of class BSS
> >       d. Segments of class STACK
> >
> > however, TLINK seems to always put segments with class 'STACK' at
the
> > end, even if they're _not_ in DGROUP.  MASM's LINK behaves according
to
> > the above list.  is there any standard to how other linkers handle
> > DOSSEG, or can they arrange the different classed segments however
they
> > want?
>
> The standard is the set of rules you mentioned above.  TLINK just
> doesn't observe them.

thanks for the reply.  heh, TLINK is wacky..

> > ----------
> > DOSSEG
> >
> > DGROUP GROUP OERP,AAAA,xaaa,LOPE,FBSS,DARK
> >
> > xaaa SEGMENT 'CODE'
> > xaaa ENDS
> >
> > CBF SEGMENT
> > CBF ENDS
> >
> > FBSS SEGMENT 'DATA'
> > FBSS ENDS
> >
> > LOSER SEGMENT 'STACK'
> > LOSER ENDS
> >
> > ztr SEGMENT 'DATA'
> > ztr ENDS
> >
> > aab SEGMENT 'BSS'
> > aab ENDS
> >
> > OERP SEGMENT 'BEGDATA'
> > OERP ENDS
> >
> > AAAA SEGMENT 'ARPA'
> > AAAA ENDS
> >
> > LOPE SEGMENT 'STACK'
> > LOPE ENDS
> >
> > ZZZU SEGMENT 'ARPA'
> > ZZZU ENDS
> >
> > DARK SEGMENT 'CODE'
> > DARK ENDS
> >
> > END
> > -----
[SNIP lots of my crap]
> > any idea what steps TLINK is going through when ordering these
segments?
> >  sometimes its behavior matches the documentation on DOSSEG; other
times
> > not.  very confusing..
>
> According to the rules, the correct order (for the original segments)
is
> as follows:
>
> Name	Class	Rule
> --------------------
> xaaa	CODE	1
> DARK	CODE	1
> CBF		2
> ztr	DATA	2
> LOSER	STACK	2
> aab	BSS	2
> ZZZU	ARPA	2
> OERP	BEGDATA	3a
> FBSS	DATA	3b
> AAAA	ARPA	3b
> LOPE	STACK	3d
> _________________________________________

ok, M$ LINK does it right then.  hmm.. why is ztr before LOSER, even
though it's after it in the source file?  is it because FBSS is the same
class as ztr, and _it's_ before LOSER?

thanks

--
=-=  assassin17@rocketmail.com  =-=
=-= Join us in the fight against violence! =-=


--== Sent via Deja.com http://www.deja.com/ ==--
---Share what you know. Learn what you don't.---
Technical Details
Message-ID: <7i4quj$n25$1@autumn.news.rcn.net>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <7hg7kq$ksb$1@autumn.news.rcn.net> <7hih7k$8vb$2@autumn.news.rcn.net>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: feaef,dda8022d1c19bc63
X-Google-Attributes: gidfeaef,public
X-Google-Thread: f7d8d,dda8022d1c19bc63
X-Google-Attributes: gidf7d8d,public
X-Google-Thread: 114917,dda8022d1c19bc63
X-Google-Attributes: gid114917,public
From: assassin17@rocketmail.com
Subject: Re: DOSSEG and TLINK
Date: 1999/05/21
Message-ID: <7i4quj$n25$1@autumn.news.rcn.net>
X-Deja-AN: 480713178
Approved: <johnfine@erols.com>
References: <7hg7kq$ksb$1@autumn.news.rcn.net> <7hih7k$8vb$2@autumn.news.rcn.net>
X-Http-User-Agent: Mozilla/4.08 [en] (Win95; I)
X-Mozilla-Status: 0801
X-Complaints-To: abuse@rcn.com
X-Trace: yoUDU9yBGKoeSczKw4wLPSDNtcngf6JMm9XEERvuXXs=
X-Http-Proxy: 1.0 x32.deja.com:80 (Squid/1.1.22) for client 206.68.208.231
Organization: Deja.com - Share what you know. Learn what you don't.
X-Article-Creation-Date: Sat May 15 18:47:42 1999 GMT
NNTP-Posting-Date: 21 May 1999 23:41:07 GMT
Newsgroups: comp.lang.asm.x86,borland.public.tasm,alt.lang.asm