jackchaos Posted November 14, 2006 Report Share Posted November 14, 2006 I've been watching my code block size increase steadily as I work on my project and I'm now aware first hand of how assembler can be much more efficient than what a compiler can do.I wanted to share a method I use to determine if my C optimizations are reducing the code size. If you look inside the project.map file, at the top of the file look for the name of the function you're working on like this:S_main__Update_LFO_LED_Status code 0x006304 program 0x0000faOn the end is the size of the function in bytes: 0x0000fa = 250 bytesThis number will change when you make changes to this function. Quote Link to comment Share on other sites More sharing options...
stryd_one Posted November 14, 2006 Report Share Posted November 14, 2006 compiled_c_code_size :) Quote Link to comment Share on other sites More sharing options...
mess Posted November 14, 2006 Report Share Posted November 14, 2006 Hi Jackchaos,thank you for the tip, it could come handy sometime :)I always looked at the bottom of the .asm file of the module I was changing,but this only gives you a general code size (of the source file)Michaël Quote Link to comment Share on other sites More sharing options...
mess Posted November 14, 2006 Report Share Posted November 14, 2006 hehe nice one stryd :) Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.