11.07.2015 Views

MSP430 IAR C/C++ Compiler reference guide - Rice University

MSP430 IAR C/C++ Compiler reference guide - Rice University

MSP430 IAR C/C++ Compiler reference guide - Rice University

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The CLIB runtimeenvironmentThis chapter describes the runtime environment in which an applicationexecutes. In particular, it covers the CLIB runtime library and how you canoptimize it for your application.The standard library uses a small set of low-level input and output routines forcharacter-based I/O. This chapter describes how the low-level routines can bereplaced by your own version. The chapter also describes how you can chooseprintf and scanf formatters.The chapter then describes system initialization and termination. It presentshow an application can control what happens before the start function main iscalled, and the method for how you can customize the initialization. Finally, theC-SPY® runtime interface is covered.Note that the legacy CLIB runtime environment is provided for backwardcompatibility and should not be used for new application projects.For information about migrating from CLIB to DLIB, see the <strong>MSP430</strong> <strong>IAR</strong>Embedded Workbench® Migration Guide.Runtime environmentThe CLIB runtime environment includes the C standard library. The linker will includeonly those routines that are required—directly or indirectly—by your application. Fordetailed <strong>reference</strong> information about the runtime libraries, see the chapter Libraryfunctions.The <strong>MSP430</strong> <strong>IAR</strong> Embedded Workbench comes with a set of prebuilt runtime libraries,which are configured for different combinations of the following features:●●●CoreData modelSize of the double floating-point typePart 1. Using the compiler 75

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!