03-14-2010, 05:37 PM
I love some of these ideas.
I think SUb <name> as interrupt has fascinating possibilities - not least of which that the compiler could assume this entry point will happen, and follow that thread to see what variables and functions are used, as well as main.
It probably means two passes, but it's a way of allowing -O3 to not exclude the interrupt path of the program.
Also, if it can work out where it has the memory to do the vector table and ISR (probably in 2 pages at the end of the program, if there's room), then that's awesome.
I hate to waste memory though. I think I'll wishlist a memory map option too.
I think SUb <name> as interrupt has fascinating possibilities - not least of which that the compiler could assume this entry point will happen, and follow that thread to see what variables and functions are used, as well as main.
It probably means two passes, but it's a way of allowing -O3 to not exclude the interrupt path of the program.
Also, if it can work out where it has the memory to do the vector table and ISR (probably in 2 pages at the end of the program, if there's room), then that's awesome.
I hate to waste memory though. I think I'll wishlist a memory map option too.