#Aztec ASsembler BSS bug?
10 messages in this thread
A dumb question since I got it answered once but… (sigh) forgot what I
was told. Heres the trouble. I upgraded to 5.0 of Aztec "C". I'm using
the Assembler "AS" to assemble some files so that I can use the SDB
debugger. Now they were assembled using A68K before and no errors. Heck
they even worked! But now I'm AS'ing and it does not understand DATA and
BSS. Arg! I figured that this new version would be a bit more compatable
but its the same old bug. The worst thing is that I can't remember what I
did before. Anyone know? Thanks in advance.
I always change DATA to DSEG…
Humm as I understand it I am supposed to change a piece of code like this
*Unititialized data
BSS
temp DS.L 100 rtmp DS.l 245
CNOP 0,4 endbss DS.L 1
to somthing like? temp BSS DS.L 100 rtmp BSS DS.L 245
CNOP 0,4 etc.
What I know is that DATA
dc.l "somestring",0
etc. doesn't work cause DATA is an unknown op-code.. if I change DATA to
DSEG then it works… I think your top edxample would work if BSS were
BSEG…
Nope – we treat uninitialized data in a, um, somewhat weird way, due to the
way C historically had to treat uninitialized data. So instead of a BSEG
or a section,bss, you have to use the global or bss directives for each
individual uninitialized variable that you've got.
-Mike
Right-o Arnie. I have managed to get that part of it working but now
(sigh) I'm trying to get beyond a strange condition I don't understand at
all. What I want to do is take a file thats really assembly and set it up
as inline Assembly code for a dummie C program (like Hello world) compile
it with the SDB flag on so I can trace with SDB but it gives me some
errors. Undefined local symbol .1 (also .2 .3 .4) and undefined symbol –
_printf What gives? THe printf is my hello world dummie program.
Are you sure you need anything more than #asm and #endasm lines in your
prog? I would try that first.. no main() no calls to c.lib, I think I had
gotten that to work
s
I admited defeat and went back to A68K 2.6 and Debug. Thanks for the help
tho…
Change DATA to say DSEG. For a BSS section, you're going to have to
individually declare each item there using the BSS or Global directives
(described in the manual).
This is not really a bug, but rather lack-of-a-feature.
-Mike
Ok I will reread the manual on that. Funny I must have missed somthing?
Please put in my vote for this as a desired feature! Otherwise thanks for
the info!