Please rewrite such constructions without reading/using the general registers. The examples EXAMPLE 1 - Code referencing to one of the MCU registers. The GCC compiler seems to give the user more responsibility to the user, where IAR Embedded Workbench for ARM instead uses keywords, intrinsic functions and/or options for covering the same construction in the application. The goal is that the 9 examples + comments should cover the issues that are most different between GCC and IAR Embedded Workbench for ARM, and that other issues can be sorted out by the developer that performs the migration. The most different area between GCC and IAR Embedded Workbench for ARM is Inline Assembler and such constructions (and some other issues) will be commented in this Technical Note (and in the attachment). This might seem to be trivial task (as IAR have written other Migration Guides), but it is not trivial - as there is no "one single GCC compiler" we are not able to cover all GCC variants. Now and then there are users requesting that IAR makes a "GCC to IAR Embedded Workbench for ARM Migration Guide". We are most grateful that he shares his findings with IAR Embedded Workbench for ARM users. Ivan Paulik, Pasat, Bratislava, Slovakia, Europe. This Technical Note discusses migration from GCC inline assembler to IAR Embedded Workbench for ARM. This Technical Note applies to ARM7/9 devices, not to Cortex devices.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |