Editing Back-End
Please note that you are now editing the latest revision of this page, which is not the approved one shown by default.
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
| − | + | In a compiler, the term ''Back End'' (BE) is sometime confused with code generator for the overlapped functionality of generating assembly code. The work in back end is done in multiple steps: | |
| + | <br> | ||
| + | |||
| + | # Compiler analysis - This is the process to gather program information from the intermediate representation of the input source files. | ||
| + | # Optimization - the intermediate language representation is transformed into functionally equivalent but faster (or smaller) forms. | ||
| + | # Code generation - the transformed intermediate language is translated into the output language, usually the native machine language of the system. This involves resource and storage decisions, such as deciding which variables to fit into registers and memory and the selection and scheduling of appropriate machine instructions along with their associated addressing modes. | ||
| + | <br> | ||
| + | |||
| + | In general, the BE of a Language Processor (LP) is the subset of modules that, after the analysis phase, perform transformation that depend on the Intermediate Representation (IR) and not directly on the source tests. | ||
| + | |||
| + | [[Category:Basic Concepts]] | ||
