> Did the way to adress Config bits in SDCC change from 2.6.0 to 2.6.4?
> On the 2.6.4 build this code doesn't work anymore... what's wrong?:
> code char at __CONFIG1H config1h = 0xc2;
The __CONFIGnl defines have (unintentionally) been renamed to _CONFIGnl
(single underscore up front) while generating the device library files
for the 18f1 family.
For consistency, I committed a modified version of the header files with
the old naming scheme (__CONFIGnl) as SDCC r4684, although this is
inconsistent with the assembler's naming scheme (only one underscore).
Thanks for the notice.
Additional thanks for revealing to me that config bits should currently
be set using the `__code' modifier---not using it is currently causing
major trouble, as gputils silently relocate the resulting definitions to
ADDRESS/2, which in turn renders the .hex file unusable in most cases.