| ??? 05/04/06 12:27 Read: times |
#115561 - the root of many evils Responding to: ???'s previous message |
Also sfr16 is handled differently. SDCC does not require the bytes to be adjacent in memory.
SFR16 is one of these 'features' that have been added as support for those that can not be bothered writing actual code. It has caused legio problems since many SFR 'pairs' require a specific sequence in reading/writing (ADC - PCA etc) which most compilers (justifiably) screw up. Erik |
| Topic | Author | Date |
| SDCC and Keil C compatibility | 01/01/70 00:00 | |
| major differences | 01/01/70 00:00 | |
| ansi incompatabilities | 01/01/70 00:00 | |
| SDCC vs keil | 01/01/70 00:00 | |
| other way round :) | 01/01/70 00:00 | |
| SDCC vs Keil Part 2 | 01/01/70 00:00 | |
| actualy | 01/01/70 00:00 | |
| thanks | 01/01/70 00:00 | |
| sfr declarations NOT compatible | 01/01/70 00:00 | |
| too bad | 01/01/70 00:00 | |
| Perhaps it is? | 01/01/70 00:00 | |
| indeed | 01/01/70 00:00 | |
| it almost is | 01/01/70 00:00 | |
| the root of many evils | 01/01/70 00:00 | |
| Another important difference! | 01/01/70 00:00 | |
| fast & efficient code | 01/01/70 00:00 | |
| Problem with porting code | 01/01/70 00:00 | |
| bla bla | 01/01/70 00:00 | |
| semicolon missing | 01/01/70 00:00 | |
| set TI=1 in your init_uart() | 01/01/70 00:00 | |
| Have you looked at this? | 01/01/70 00:00 | |
General Tip: Disable all extensions | 01/01/70 00:00 |