3.2.10 Intermediate Dump Options

The following options are provided for the purpose of retargetting and debugging the compiler. They provide a means to dump the intermediate code (iCode) generated by the compiler in human readable form at various stages of the compilation process. More on iCodes see chapter 9.1 ''The anatomy of the compiler''.

• [--dumpraw] This option will cause the compiler to dump the intermediate code into a file of named <source filename>.dumpraw just after the intermediate code has been generated for a function, i.e. before any optimizations are done. The basic blocks at this stage ordered in the depth first number, so they may not be in sequence of execution.
• [--dumpgcse] Will create a dump of iCodes, after global subexpression elimination, into a file named <source filename>.dumpgcse.
• [--dumpdeadcode] Will create a dump of iCodes, after deadcode elimination, into a file named <source filename>.dumpdeadcode.
• [--dumploop] Will create a dump of iCodes, after loop optimizations, into a file named <source filename>.dumploop.
• [--dumprange] Will create a dump of iCodes, after live range analysis, into a file named <source filename>.dumprange.
• [--dumlrange] Will dump the life ranges for all symbols.
• [--dumpregassign] Will create a dump of iCodes, after register assignment, into a file named <source filename>.dumprassgn.
• [--dumplrange] Will create a dump of the live ranges of iTemp's
• [--dumpall] Will cause all the above mentioned dumps to be created.