This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Assembly Code Listing for Library Calls

I'm looking at the overhead required for the different assembler code produced by a case statement in C. The compiler uses the LCALL ?C?CCASE instruction with a data table for an unstructured case statement.

How can I get a listing for the assembly code for this library call? (Or C code)

Thanks!

Parents
  • Thanks for your reply!

    I've been away from this compiler and processor for the past several years and just getting familiar again.

    "Or C Code" was meant to say if there was a C code listing of the library call available.

    I have no assembly level debug capability available on my platform as my processor is embedded in a platform without debug access to the processor.

    A disassembler would work, although my experience has been that reading the output of this and locating the library call is not such an easy task (if you mean disassembling the final linked binary program). But certainly possible. However, I'm looking for the easiest way since I have to do this over and over again over the next few days with different code snippets. Perhaps dissassembling only the library code if I can locate it?

    The assembly code for the library calls is not made available? This is a problem if you want to code in C, but still need to understand exactly the performance of the code produced when code is linked in that is hidden from you.

    Is there a disassembler you can recommend?

Reply
  • Thanks for your reply!

    I've been away from this compiler and processor for the past several years and just getting familiar again.

    "Or C Code" was meant to say if there was a C code listing of the library call available.

    I have no assembly level debug capability available on my platform as my processor is embedded in a platform without debug access to the processor.

    A disassembler would work, although my experience has been that reading the output of this and locating the library call is not such an easy task (if you mean disassembling the final linked binary program). But certainly possible. However, I'm looking for the easiest way since I have to do this over and over again over the next few days with different code snippets. Perhaps dissassembling only the library code if I can locate it?

    The assembly code for the library calls is not made available? This is a problem if you want to code in C, but still need to understand exactly the performance of the code produced when code is linked in that is hidden from you.

    Is there a disassembler you can recommend?

Children