Von: Peter Bigot
Gesendet am: 12 Aug 2010 14:18:21
Do it; then do it right; then do it fast. -- Somebody
(Fast while still doing it right, a condition often neglected.)
Well, if this condition is neglected while following this rule, it
is because the rule is ambiguous.
'then do it fast' can
I'm not convinced that presence of a single far pointer requires that every
address kick up to 32 bits. If near/far is maintained as an attribute on
the symbol, as apparently IAR uses a __data20 qualifier, it should be
possible to manage things properly. Whether GCC+binutils makes it
reasonably
Von: Peter Bigot
Gesendet am: 12 Aug 2010 03:04:29
I'm not convinced that presence of a single far pointer requires that every
address kick up to 32 bits. If near/far is maintained as an attribute on
the symbol, as apparently IAR uses a __data20 qualifier, it should be
possible to manage
Von: Michiel Konstapel
Gesendet am: 10 Aug 2010 14:40:06
Generally using 20 bit registers isn't advisable as it increases code
size and execution times and only a fraction of the MSP users needs
the additional code size. Many (inlcuding me) just need the higher
speed, more ram or better
- Ursprüngliche Nachricht -
Von: Peter Bigot
Gesendet am: 10 Aug 2010 01:18:25
Having cut my teeth on 8088 assembly language, the concept of near and far
qualifiers is natural to me. Mixing memory models is ugly, but if the
linker can figure it out, 95% of the coders out there won't
Generally using 20 bit registers isn't advisable as it increases code
size and execution times and only a fraction of the MSP users needs
the
additional code size. Many (inlcuding me) just need the higher speed,
more ram or
better peripherals.
On the other hand, many (including me) are mainly
