Mercurial > hg > Members > kono > nitros9-code
changeset 617:fd2cb29abee5
Chapter 2 finished
author | roug |
---|---|
date | Sat, 30 Nov 2002 09:44:49 +0000 |
parents | aed4cad385af |
children | 7a4d7a896b8f |
files | docs/ccguide/ccguide.docbook docs/ccguide/chap1.chapter |
diffstat | 2 files changed, 22 insertions(+), 4 deletions(-) [+] |
line wrap: on
line diff
--- a/docs/ccguide/ccguide.docbook Sat Nov 30 09:44:49 2002 +0000 +++ b/docs/ccguide/ccguide.docbook Sat Nov 30 09:44:49 2002 +0000 @@ -85,7 +85,8 @@ ]> <book id="cc-guide" lang="en"> <bookinfo> - <title>C Compiler User's Guide</title> + <title>Microware C Compiler User's Guide</title> + <subtitle>for OS-9</subtitle> <publisher> <publishername>Cleglen Publishing Limited</publishername> @@ -126,7 +127,7 @@ <preface> <title>Acknowledgements</title> <para> -Thw OS-9 C Compiler was written by James McCosh with OS-9 +The OS-9 C Compiler was written by James McCosh with OS-9 implementation assistance from Terry Crane and Kim Kempf. The Relocatable Assembler, Linker, and Profiler was edited by Wes Camden and Ken Kaplan.
--- a/docs/ccguide/chap1.chapter Sat Nov 30 09:44:49 2002 +0000 +++ b/docs/ccguide/chap1.chapter Sat Nov 30 09:44:49 2002 +0000 @@ -89,6 +89,10 @@ <section> <title>Implementation-dependent Characteristics</title> <para> +K & R frequently refer to characteristics of the C language +whose exact operations depend on the architacture and instruction +set of the computer actually used. This section contains specific +information regarding this version of C for the 6809 processor. </para> <section> @@ -142,12 +146,25 @@ <section> <title>Achieving Maximum Program Performance</title> -<para> -</para> <section> <title>Programming Considerations</title> <para> +Because the 6809 is an 8/16 bit microprocessor, the compiler +can generate efficient code for 8 and 16 bit objects (CHARs, INTs, +etc.). However, code for 32 and 64 bit values (LONGs, FLOATs, +DOUBLEs) can be at least four times longer and slower. Therefore +don't use LONG, FLOAT, or DOUBLE where INT or UNSIGNED will do. +</para> +<para> +The compiler can perform extensive evaluation of constant +expressions provided they involve only constants of type CHAR, INT, +and UNSIGNED. There is no constant expression evaluation at +compile-time (except single constants and "casts" of them) where +there are constants of type LONG, FLOAT, or DOUBLE, therefore, +complex constant expressions involving these types are evaluated at +run time by the compiled program. You should manually compute the +value of constant expressions of these types if speed is essential. </para> </section>