Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!apple!bionet!csd4.milw.wisc.edu!leah!albanycs!crdgw1!uunet!mcvax!ukc!icdoc!tgould!iwm
From: iwm@ic.ac.uk (Ian Moor)
Newsgroups: comp.sys.amiga
Subject: Re: zc /a68k/blink
Message-ID: <IWM.89Jun15141209@amvax5.ic.ac.uk>
Date: 15 Jun 89 13:12:10 GMT
References: <IWM.89Jun6193326@amvax5.ic.ac.uk> <19362@cup.portal.com>
Sender: news@doc.ic.ac.uk
Organization: Dept. of Computing, Imperial College
Lines: 23
In-reply-to: stephan@cup.portal.com's message of 11 Jun 89 07:29:57 GMT
Posting-Front-End: GNU Emacs 18.45.10 of Tue Jan 12 1988 on amvax5 (berkeley-unix)


In article <19362@cup.portal.com> stephan@cup.portal.com (Stephen Derek Schaem) writes:

>    DC.x 0/DS.x 0 Will be generated the same way! only if DS is located in a
>   BSS section then it will only store the size of the data.
>    The only diference you will notice is that you cant address it pc relative.
>   ZC actualy put's all it's DS in a BSS chunk.I dont see what is your point
>   about DC/DS..

I could have been clearer in the original posting. 
Here's what I think they mean:

  DC.x n
allocate  store in the current section initialised to n
  
  DS.x n
allocate n units (depends on x) of uninitialised store in the current section.
If n = 0, allocate NO store, but align the following data according to x.
e.g 
  DC.L 0  ; Longword = 0
  DS.L 0  ; Align next item on  longword boundary
   
What I think ZC is doing wrong is using DS.L 0 to initialise static globals.