Optimizer compile time constants problem

Hi Rolf.

I think that it can be done by not substituting the constant value at compile time. Then the assembler will replace by the appropriate value.

Please see my pm for appropriate assembler instructions. I also think that my suggestion could be applied to all constants and make the assembler more readable.

Regards.

@Rolf:
Thank you very much! New AvrCo from PM shows non-zero values which match the ones from ASM file.

@Merlin:
I get OptimiserRev=770 and OptimiserBuild=2816, which are $0302 and $0B00 from ASM file, but for MerlinOptimiser executable file properties show version 3.2.11.0. It seams a little different from CompilerRev where 504 translates to v5.0.4. My guess would be that I should look at individual bytes to form a version number, something like $03.$02.$0B.$00 should be translated to 3.2.11.0. Is this right?

Thanks Merlin, it is all clear now.