ARM Compiler toolchain v4.1 for ÂµVision Using the Compiler

More documents

Recommendations

Info

Getting started with the Compiler 3.5 Using stdin to input source code to the compiler Instead of creating a file for your source code, you can use stdin to input source code directly on the command line. This is useful if you want to test a short piece of code without having to create a file for it. To use stdin to input source code directly on the command line: 1. Invoke the compiler with the command-line options you want to use. The default compiler mode is C. Use the minus character (-) as the source filename to instruct the compiler to take input from stdin. For example: armcc --bigend -c - If you want an object file to be written, use the -o option. If you want preprocessor output to be sent to the output stream, use the -E option. If you want the output to be sent to stdout, use the -o- option. If you want an assembly listing of the keyboard input to be sent to the output stream after input has been terminated, use none of these options. 2. You cannot input on the same line after the minus character. You must press the return key if you have not already done so. The command prompt waits for you to enter more input. 3. Enter your input. For example: #include int main(void) { printf("Hello world\n"); } 4. Terminate your input by entering Ctrl-Z then Return. An assembly listing for the keyboard input is sent to the output stream after input has been terminated if both the following are true: • no output file is specified • no preprocessor-only option is specified, for example -E. Otherwise, an object file is created or preprocessor output is sent to the standard output stream, depending on whether you used the -o option or the -E option. The compiler accepts source code from the standard input stream in combination with other files, when performing a link step. For example, the following are permitted: • armcc -o output.axf - object.o mylibrary.a • armcc -o output.axf --c90 source.c - Executing the following command compiles the source code you provide on standard input, and links it into test.axf: armcc -o test.axf - You can only combine standard input with other source files when you are linking code. If you attempt to combine standard input with other source files when not linking, the compiler generates an error. 3.5.1 See also Tasks Introducing the ARM Compiler toolchain: • Using a text file to specify command-line options on page 2-20. ARM DUI 0375C Copyright © 2007-2008, 2011 ARM. All rights reserved. 3-11 ID061811 Non-Confidential
Getting started with the Compiler Reference • Compiler command-line syntax on page 3-3 • Compiler command-line options listed by group on page 3-4. Introducing the ARM Compiler toolchain: • Compilation tools command-line option rules on page 2-17. ARM DUI 0375C Copyright © 2007-2008, 2011 ARM. All rights reserved. 3-12 ID061811 Non-Confidential
Page 1 and 2: ® ARM Compiler toolchain v4.1 for
Page 3 and 4: Contents ARM Compiler toolchain v4.
Page 5 and 6: Contents 5.19 Inline functions ....
Page 7 and 8: Contents 7.41 __mcall_is_virtual(D,
Page 9 and 10: Conventions and Feedback • the se
Page 11 and 12: Overview of the compiler 2.1 The co
Page 13 and 14: Overview of the compiler 2.3 The C
Page 15 and 16: Getting started with the Compiler
Page 17 and 18: Getting started with the Compiler 3
Page 19 and 20: Getting started with the Compiler
Page 23: Getting started with the Compiler 3
Page 45 and 46: Chapter 4 Compiler Features The fol
Page 47 and 48: Compiler Features 4.1 Compiler intr
Page 49 and 50: Compiler Features 4.2 Performance b
Page 51 and 52: Compiler Features 4.4 Generic intri
Page 57 and 58: Compiler Features 4.10 Compiler sup
Page 59 and 60: Compiler Features 4.12 Texas Instru
Page 61 and 62: Compiler Features /* Declare PSR as
Page 63 and 64: Compiler Features 4.13.1 See also R
Page 65 and 66: Compiler Features 4.15 Compiler and
Page 67 and 68: Compiler Features Using the Linker:
Page 69 and 70: Compiler Features Reference Compile
Page 71 and 72: Compiler Features 4.19 Compiler sup
Page 73 and 74: Compiler Features 4.21 PreCompiled
Page 75 and 76:
Compiler Features 4.23 PreCompiled
Page 77 and 78:
Compiler Features Reference Compile
Page 79 and 80:
Compiler Features 4.26 Obsolete Pre
Page 81 and 82:
Compiler Features 4.28 Selectively
Page 83 and 84:
Compiler Features 4.30 Message outp
Page 85 and 86:
Compiler Features 4.32 Default comp
Page 87 and 88:
Compiler Coding Practices • Guard
Page 89 and 90:
Compiler Coding Practices • Exten
Page 91 and 92:
Compiler Coding Practices 5.2 Compi
Page 93 and 94:
Compiler Coding Practices 5.4 Selec
Page 95 and 96:
Compiler Coding Practices In additi
Page 97 and 98:
Compiler Coding Practices Table 5-4
Page 99 and 100:
Compiler Coding Practices Table 5-6
Page 101 and 102:
Compiler Coding Practices 5.9 Code
Page 103 and 104:
Compiler Coding Practices 4. After
Page 105 and 106:
Compiler Coding Practices 5.12 Meth
Page 107 and 108:
Compiler Coding Practices 5.14 Meth
Page 109 and 110:
Compiler Coding Practices 5.16 Func
Page 111 and 112:
Compiler Coding Practices Reference
Page 113 and 114:
Compiler Coding Practices • __val
Page 115 and 116:
Compiler Coding Practices 5.20 Comp
Page 117 and 118:
Compiler Coding Practices 5.21 Auto
Page 119 and 120:
Compiler Coding Practices 5.23 Auto
Page 121 and 122:
Page 123 and 124:
Compiler Coding Practices 5.27 Inli
Page 125 and 126:
Compiler Coding Practices 5.28 Inli
Page 127 and 128:
Compiler Coding Practices 5.30 Adva
Page 129 and 130:
Compiler Coding Practices 5.32 Rele
Page 131 and 132:
Compiler Coding Practices 5.34 The
Page 133 and 134:
Compiler Coding Practices 5.36 Perf
Page 135 and 136:
Compiler Coding Practices 5.38 Unal
Page 137 and 138:
Compiler Coding Practices (LDR/STR/
Page 139 and 140:
Compiler Coding Practices • Hexad
Page 141 and 142:
Compiler Coding Practices 5.42 Exam
Page 143 and 144:
Compiler Coding Practices 5.43 Vect
Page 145 and 146:
Compiler Coding Practices 5.45 Impl
Page 147 and 148:
Compiler Coding Practices 5.47 Half
Page 149 and 150:
Compiler Coding Practices 5.49 Type
Page 151 and 152:
Compiler Coding Practices If you us
Page 153 and 154:
Compiler Coding Practices 5.52 Abou
Page 155 and 156:
Compiler Coding Practices 5.54 Iden
Page 157 and 158:
Compiler Coding Practices 5.56 Soft
Page 159 and 160:
Compiler Coding Practices 5.58 Iden
Page 161 and 162:
Compiler Coding Practices 5.59 Soft
Page 163 and 164:
Compiler Coding Practices 5.60.1 Se
Page 165 and 166:
Compiler Coding Practices 5.62 // c
Page 167 and 168:
Compiler Coding Practices 5.64 Desi
Page 169 and 170:
Compiler Coding Practices 5.66 Flex
Page 171 and 172:
Compiler Coding Practices 5.68 inli
Page 173 and 174:
Compiler Coding Practices 5.70 Macr
Page 175 and 176:
Compiler Coding Practices 5.72 New
Page 177 and 178:
Compiler Coding Practices 5.74 Rest
Page 179 and 180:
Page 181 and 182:
Compiler Coding Practices 5.78 Exte
Page 183 and 184:
Compiler Coding Practices 5.80 snp
Page 185 and 186:
Compiler Coding Practices 5.82 wid
Page 187 and 188:
Chapter 6 Compiler Diagnostic Messa
Page 189 and 190:
Compiler Diagnostic Messages 6.2 Se
Page 191 and 192:
Compiler Diagnostic Messages 6.4 Pr
Page 193 and 194:
Compiler Diagnostic Messages 6.6 Co
Page 195 and 196:
Using the Inline and Embedded Assem
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251:
show all

ARM Compiler toolchain v4.1 for ÂµVision Using the Compiler

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?