3-3 Development Flow We’ll show the development environment that is included as standard in the HEW. Programs created in C language can be converted to object programs directly or via assembly language source programs. If they are via assembly source the local symbol information is deleted so normally they are converted directly. Load modules are created by optimization linkage editors combining objects created in assembly language, user libraries created by the librarian or standard libraries. At this time in order to optimize information that handles global variables that couldn’t be optimized by the compiler because of differing files, symbol allocation information can be returned to the compiler. The output format is ELF/Dwarf2, which is supported by many debuggers, including simulators and emulators. For the ROM writer, the data is converted into to Motorola S, Intel hex or others. As an integrated development environment the HEW comes with standard tools such as stack analysis tools and simulators. In addition the HEW provides interface to the upstream CASE tool ZIP and interface to the version management tool. Further, all tools including the compiler, assembler and editor can be replaced. In this way the Build can be used to build the standard library for a specific purpose, compile, assemble and link objects, and even activate the simulator and emulator with option settings.