• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 55 subscribers
  • Views 3223 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP430FR5992: MSP430 GCC memory model

BO
Genius 12760 points
Part Number: MSP430FR5992


Customer will stay with MSP430 GCC and wants to know:

 

  With the "large" memory model for data and code (option -mlarge) the code will be about 20% larger than the "small" memory model (option -msmall).

  This is unusable for us.

  With a "large" memory model only for code, and "small" model for data, the code would be about 5% larger. This is acceptable.

  Is there an option to have "large" model for code and "small" model for data ?

  If no, is it planned to have such possibility in the near future ?

 

Regards, Bernd

  • 0
    Guru 318920 points
    You'd have to ask the GCC developers.

    As far as I know, nothing like this is planned.
  • 0 in reply to Clemens Ladisch
    TI__Genius 12760 points

    According to the latest MSP430 GCC Users Guide www.ti.com/lit/SLAU646 we support that

    Whom can I contact?

    Regards, Bernd

  • 0 in reply to BO
    Guru 318920 points
    GCC has nothing but the "-msmall" and "-mlarge" options. The msp430 target code makes no effort whatsoever to distinguish between code and data accesses.

    The actual support is done by Somnium.
  • 0 in reply to Clemens Ladisch
    TI__Genius 12760 points

    Clemens,

    meanwhile I found the TI-internal supporter.
    But anyway thank you for the hint with www.somniumtech.com/news/somnium-partner-texas-instruments

    Regards, Bernd

  • 0 in reply to Clemens Ladisch
    TI__Guru**** 251490 points

    I apologize for the delay.  I can confirm the following is correct ...

    Clemens Ladisch said:
    GCC has nothing but the "-msmall" and "-mlarge" options. The msp430 target code makes no effort whatsoever to distinguish between code and data accesses.

    Documentation on the entire GCC compiler (all targets it supports!) can be found at https://gcc.gnu.org/onlinedocs/ .  Search it for the section titled MSP430 Options.  The only options related to memory model are -mshort and -mlarge.  The description of these options is very short.  To see what they do, build an example source file and inspect it like this ...

    % ofd430 --obj_display=none,battrs file.o

OBJECT FILE:  file.o

 Build Attributes in ".MSP430.attributes"

    Format Version:  'A'

    <0>  Vendor Name:  "mspabi" (ABI for the Texas Instruments MSP430 Architecture)

         Tag_File:
            Attributes:
             Tag_ISA         2  (MSPX)
             Tag_Code_Model  1  (small code)
             Tag_Data_Model  1  (small data)

    The utility ofd430 is from the TI compiler toolset.  But you can use it on object files built with the GCC compiler.  You will see that all you can get are small code and small data, or large code and large data.  No other combinations are supported.  The TI compiler supports several other combinations and variations.

    The GCC MSP430 compiler is in maintenance only mode.  No new work is planned.

    Thanks and regards,

    -George