??? 12/02/05 14:21 Read: times |
#104588 - ICE and optimization Responding to: ???'s previous message |
This could possibly reduce your code size to below 64K - although it would be more difficult to debug (even with an ICE).
my experience: "although it would be virtually impossible to debug (even with an ICE)" Re code size reduction: I have learned that thai can be accomplished to a very large extent by "helping" the compiler. an example, albeit small, that I see very often: if (variable == TRUE) { variable = FALSE; } why not just variable = FALSE;which is both more compact and faster. Sometimes it really pays to check 2 versions of the same code e.g. "do while" and "for" can be used interchangeably in most cases, and have a look at the generated assembler. Then jot down in your DNA computer which to use. Erik |
Topic | Author | Date |
In-circuit emulator | 01/01/70 00:00 | |
emulator or debugger | 01/01/70 00:00 | |
delicate??? | 01/01/70 00:00 | |
Re | 01/01/70 00:00 | |
re Phyton | 01/01/70 00:00 | |
I think you need some expensive version | 01/01/70 00:00 | |
Ceibo supports code banking | 01/01/70 00:00 | |
are yoy using the DS ? | 01/01/70 00:00 | |
Yes it is a DS-51 | 01/01/70 00:00 | |
What's an emulator ( ICE)? | 01/01/70 00:00 | |
a simple definition | 01/01/70 00:00 | |
Reduce code size? | 01/01/70 00:00 | |
ICE and optimization | 01/01/70 00:00 | |
Good Point | 01/01/70 00:00 | |
Optimisation | 01/01/70 00:00 | |
Re: ICE | 01/01/70 00:00 | |
I can not speak for you, but evaluating![]() | 01/01/70 00:00 |