With mspgcc 3.x (12/08 windows build) I found some problems with the assembler. Using some of the MOVA and MOVX.A instructions resulted into a 0x0000 0000 0000 instruction (in the assembler listing) and other problems. Including relocation problems. Since mspgcc4 was already in the works, I didn't report this. But incorrect handling os some seldom used addressing modes or a missing/wrong flag for 20 bit addresses (especially if the address is moved from 16 to 20 bit space by the linker while the compiler generated 16 bit code) might be a possible cause.
I'm just guessing :) JMGross ----- Ursprüngliche Nachricht ----- Von: Peter Bigot An: GCC for MSP430 - http://mspgcc.sf.net Gesendet am: 04 Jun 2010 19:44:19 Betreff: Re: [Mspgcc-users] mspgcc4 linking problems - relates to bug 5815 in mspgcc Good point; in fact, it's probably not related to MSP430X ("relocation" just signals that thought in my mind). Either way, it's on the queue (I've had a Chronos sitting on my desk for the last three months that I haven't had a chance to look at, so what you're doing could be very useful to me as well). The warning in signal.h is from a previous maintainer, and I just need to look again to confirm there's nothing wrong with what it's doing. Since it's been working fine since January, I don't have much concern. Peter On Fri, Jun 4, 2010 at 12:32 PM, Paul F. Sehorne <p...@sehorne.org> wrote: > Thank you, Peter. > > I notice you refer to the linking problem as MSP430X. Are the linking > problem and the warning issued in signal.h related? >
