Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!labrea!shelby!Portia!gilham
From: gilham@Portia.Stanford.EDU (fred gilham)
Newsgroups: comp.sys.amiga
Subject: Re: a68k, BSS directive
Summary: Sorry, not bug in a68k
Keywords: a68k, pdc
Message-ID: <1019@Portia.Stanford.EDU>
Date: 20 Mar 89 19:41:46 GMT
References: <918@Portia.Stanford.EDU>
Sender: fred gilham <gilham@Portia.stanford.edu>
Reply-To: gilham@Portia.UUCP (fred gilham)
Organization: Stanford University
Lines: 21

In article <918@Portia.Stanford.EDU> gilham@Portia.UUCP (me) writes:
>
>    The new a68k (version 2.42) that came over comp.binary.amiga
>recently seems to have problems with the BSS directive.

The problem is not a68k.  It is (I think) in the Sozobon c compiler.
When I compiled the sieve.c program from fish 110 pdc/examples with
zc, it produced the following code:

            BSS BSS
            XDEF     _flags
_flags:     ds.l 0
            ds.w 0
    (about 4000 more ds.w 0 statements)

Stupid me looked at that and wondered why a68k didn't put anything in
the bss hunk and why the result of linking was a bad object module.
The same person also thought he had gotten these results with pdc,
which doesn't even produce a bss directive.  Sorry for anyone who has
wasted any time trying to troubleshoot this.
-Fred Gilham