| ??? 03/12/10 21:24 Read: times |
#174086 - Once you use ASM, the optimiser gives up Responding to: ???'s previous message |
From the compiler's point of view, you may be using any registers or other resources that are 'allowed' in a C function.
Yet it has no control over which resources you are using. So it assumes the worst case. e.g. it pushes everything. Personally, I would write the ISR() completely in C in its own source file. Let the compiler generate an ASM file. Then hand-optimise the ASM code and add isr_asm.asm to your project replacing isr_c.c David. |
| Topic | Author | Date |
| How to control PUSHes & POPs in interrupt? | 01/01/70 00:00 | |
| Don't know in Keil but | 01/01/70 00:00 | |
| What is the Code in the interupt? | 01/01/70 00:00 | |
| Code in Interrupt | 01/01/70 00:00 | |
| Once you use ASM, the optimiser gives up | 01/01/70 00:00 | |
| OR | 01/01/70 00:00 | |
Questions | 01/01/70 00:00 | |
| Use alternate register set... | 01/01/70 00:00 | |
| Yes, That's it. | 01/01/70 00:00 | |
| Using X | 01/01/70 00:00 | |
| Just Remember | 01/01/70 00:00 | |
| The cost... | 01/01/70 00:00 |