> BTW, it seems to me that there is some problem with crt0.s - I have to > have my own start-up routine so I used crt0.s as template. Unfortunately > it can't be compiled unless .globl is added for l__INITIALIZE* and > s__INITIALIZE* values. Does it work differently when using standard crt0.s?
Not really. You want to do two things in the start of crt0.s 1. Mention all the sections you have in the order you want them to be linked (in particular gs* ordering matters a lot) 2. .globl any s__ or l__ symbol you need to reference in the crt0.s code itself. What I do for Fuzix btw is I have a program that loads the binary image built from sdcc and then copies the INITIALIZER data into INITIALIZED, trims the image and resave it. As I link INITIALIZER somewhere bogus (or at the end of the image) I can then trim the image to size. I can send you the source for that tool - it's pretty trivial as it just reads from the map file to work out what to move. Alan ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
