MSL C and Runtime libraries

[theJoel]

Hi,

I've tried this with CW6.4 and CW7.1:

I'm seeing large discrepancies in the file sizes between the support libraries created from the CW projects included in the install versus the pre-built libraries. Should I be able to create an exact binary image of the pre-built versions, using the same project / compiler settings? How much of the difference could be attributed to the debug or symbolics info that may be dependant on source code directory structure? It seems the output may have a different link order..

Eg.

pre-built MSL C StdABI:   622 kB

my build MSL C StdABI:    526 kB

first line of pre-built:       !<arch>.ansi_fp.o

first line of my lib:           !<arch>.abort_exit_e68k.

The libs are about 300 kB different doing the same test with CW7.1.

Is this to be expected? Is there any concern here? I want to be able to confidently debug my application, which has always used the pre-built libraries, without being concerned I've changed the underpinnings..

Any insight is appreciated!

Cheers,

Joel.

[theJoel]

Hi,

still looking for codewarrior or compiler gurus for info above..

Also, trying to understand the A6 stack frames setting in the ColdFire Processor panel of the project settings. How does this impact code and debugging? CodeWarrior Help didn't give me enough info..

Thanks,

Joel.

[CrasyCat]

Hello

I would recommend you to submit a service request for that.

Click here to submit a service request.

CrasyCat