??? 06/26/06 08:57 Read: times |
#119087 - General Tip: Disable all extensions Responding to: ???'s previous message |
Most compilers have an option to disable all their extensions.
So your first step should be to use this option in the compiler from which you're porting the code. Thus the "original" compiler will identify everywhere that you've used its specific extensions. You can then go to the "destination" compiler's Manual, and look-up the corresponding syntax for all those features For Keil, see http://www.keil.com/support/m...extend.htm Note that this just identifies syntax extensions - it won't help you idetify where you've relied on other things like calling conventions, data representations, etc... |
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 |