It is also interesting (to me) to point out that "Metal C" uses the same back-end. Metal-C generates assembler code which is not dependent on the C library or LE, supports user inlined assembler code, etc. Just like with C/C++, you can specify ARCH(),TUNE(), INLINE, etc.
With the explosion of new instructions, at what point does writing hand-written assembler code become less and less practical? Kirk Wolf Dovetailed Technologies http://dovetail.com On Thu, Apr 12, 2012 at 11:29 PM, Tom Ross <tmr...@stlvm20.vnet.ibm.com>wrote: > > That is close to what I said. I said that C/C++ and PL/I currently share > a common back end, and that eventually IBM would like all compilers to > share > a common backend. In response to another comment, the JIT compiler does > create optimized sequences of instructions, and we hope to use some of > that technology as well in a new COBOL compiler release. > > As for assembler code generated for COBOL usage of BINARY data items, we > are highly influenced by the COBOL standard. COBOL data items are all > base 10, with digits 1-9, so mapping BINARY data items to that requires > some trickery. The good news is that you can process dollars and cents > in many different data types with no floating points if you want to, > unlike some other languages. > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
