>
> I wonder whether it would be appropriate for this tiny patch to be applied
> as part of the mspgcc4 build process?
>
Probably somebody included <iomacros.h> before including a chip-specific
header. What I think I'll do is just remove the condition in the iomacros.h
that comes with the TI header variant so it's not necessary. If you could
file a bug on the mspgcc4 SF tracker that'd help remind me to do this.
Do any of y'all have any ideas about the cleanest way to deal with this? So
> far, I haven't found a way to either trick the C preprocessor into stripping
> out the "U" suffixes, or to get the assembler to digest them properly.
>
Bah. Those had to be added in to avoid warnings about integer value
overflow when generating 16-bit constants that had the high bit set.
In the short term, I'd suggest editing the installed headers to remove the
suffix from the constants you need, and again filing a tracker ticket, which
I'll resolve by coming up with some solution that works on both C and
assembler.
Fixes for both these should be pretty straightforward, and ought to be in
the next release (no estimate when that'll be, I'm buried in other tasks at
the moment).
Peter
On Sun, Oct 24, 2010 at 5:46 PM, Mark J. Blair <[email protected]> wrote:
> I'm trying to switch from using the legacy headers to the TI ones, in order
> to start compiling code for MSP430F55xx processors. My first flow-flushing
> process is to re-do my previous port of the slac139d code for the
> ez430-RF2500 platform, since I found that it would no longer compile
> properly once I switched to the TI headers.
>
> I'm using mspgcc4 from the git repository, from the master branch, last
> pulled around 10/6/2010. I'm building under Mac OS X.
>
> First, I found that I had to add this #define near the beginning of
> .../msp430-gcc-4.4.4/msp430/include/iomacros.h in order to get the
> const_sfrb() macros to work:
>
> #define __MSP430_TI_HEADERS__
>
> I'm not sure why this definition didn't carry through from the other
> headers that included iomacros.h, but adding that line cured the barfing on
> const_sfrb(), and let my compilation proceed a lot further.
>
> I wonder whether it would be appropriate for this tiny patch to be applied
> as part of the mspgcc4 build process?
>
> I'm stuck on the best way to approach the second issue I'm having, though.
> There's a small amount of assembled code in the slac139d project, and it
> includes <msp430x22x4.h> to pick up register definitions. Unfortunately,
> lots of the TI header files use integer constants with "U" suffixes, and the
> assembler barfs on those. I hope that I can avoid needing to massage all of
> the TI header files to get rid of those, because that would be a headache
> that I'd need to re-live every time I upgrade mspgcc4, and such a sweeping
> change doesn't seem like something that's appropriate as part of the
> standard mspgcc4 distribution.
>
> Do any of y'all have any ideas about the cleanest way to deal with this? So
> far, I haven't found a way to either trick the C preprocessor into stripping
> out the "U" suffixes, or to get the assembler to digest them properly.
>
> Thanks in advance for any suggestions.
>
> --
> Mark J. Blair, NF6X <[email protected]>
> Web page: http://www.nf6x.net/
> GnuPG public key available from my web page.
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Nokia and AT&T present the 2010 Calling All Innovators-North America
> contest
> Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in
> marketing
> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
> http://p.sf.net/sfu/nokia-dev2dev
> _______________________________________________
> Mspgcc-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>
------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
_______________________________________________
Mspgcc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
