Ron Wilson

options for allocating static constants

Discussion created by Ron Wilson on Mar 3, 2011
Latest reply on Mar 14, 2011 by Daniel Lundin

We are using Code Warrior 5.0 for S12X.


We have found that the default allocation of constants into the ROM_VAR seqment applies to static constants as well (that is, constants qualified as static to indicate they are private to the source file they are defined in).


For various reasons, we are using a comples thrisd party library supplied in object form. While we can freely specify the compile options we need, to ask the vendor to make any changes to the actual source code, like inserting #pragma directives to control constant allocation, would incur a $10,000 fee, plus $1000 per day (or fraction there of) for customization services.


I have read through the documentation, but I can't find an option to provide the same control as a #pragma would.