I see three differences between your two compiles: 1. The first is compiled for the 2013, the second for the 1121. 2. The files in each set are different files. 3. In the second set you do not show how setdco.o, I2C_master.o or DS1631.o were compiled.
I would hope that the specific target doesn't effect whether source is included or not. My best guess would be that perhaps you are compiling setdco.o, I2C_master.o or DS1631.o differently, and w/o w/e flags being set the final compile to binary couldn't find the source for some and simply decided to dump the source for the others. On Thu, Jun 11, 2009 at 10:56 PM, Dan Bloomquist<[email protected]> wrote: > > Hi, > I'm not sure what triggers it. But some of my code will compile with a > list output that includes the source. Sometimes it doesn't. And as far > as I can tell, all is the same. > > For instance: > msp430-gcc -mmcu=msp430x2013 -mendup-at=main -Os -g3 -Wall -c > -fmessage-length=0 -MMD -MP -MF "thermocouple.d" -MT"thermocouple.d" -o > "thermocouple.o" "../thermocouple.c" > > msp430-gcc -mmcu=msp430x2013 -mendup-at=main -Os -g3 -Wall -c > -fmessage-length=0 -MMD -MP -MF "i2c.d" -MT"i2c.d" -o "i2c.o" "../i2c.c" > > msp430-gcc -mmcu=msp430x2013 -mendup-at=main -Os -g3 -Wall -c > -fmessage-length=0 -MMD -MP -MF "HE_util.d" -MT"HE_util.d" -o > "HE_util.o" "../HE_util.c" > > msp430-gcc -mmcu=msp430x2013 -o"test.elf" ./thermocouple.o ./i2c.o > ./HE_util.o > > msp430-objdump -S test.elf >test.lst > ~~~ > > And I get the source shown in test.lst at least for thermocouple.c > > But: > cd C:\cpp\mspgcc\workspace\uart\Debug > > msp430-gcc -mmcu=msp430x1121 -mendup-at=main -Os -g3 -Wall -c > -fmessage-length=0 -MMD -MP -MF "uart.d" -MT"uart.d" -o "uart.o" "../uart.c" > > msp430-gcc -mmcu=msp430x1121 -o"test.elf" ./uart.o ./setdco.o > ./I2C_master.o ./DS1631.o > > msp430-objdump -S test.elf >test.lst > ~~~ > > And no source. I use the list to better optimize my size. It is so much > easier to see where I'm working. Is there some way to make it work all > the time? > > (BTW, I think it is nuts not to at least phase lock to a watch crystal, > the DCO, if you are going to us a uart.) > > Best, Dan. > > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Mspgcc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mspgcc-users >
