]>
Commit | Line | Data |
---|---|---|
fed3cef0 RK |
1 | @c Copyright (C) 1988,1989,1992,1993,1994,1995,1996,1997,1998,1999,2000 |
2 | @c Free Software Foundation, Inc. | |
feca2ed3 JW |
3 | @c This is part of the GCC manual. |
4 | @c For copying conditions, see the file gcc.texi. | |
5 | ||
6 | @node Target Macros | |
7 | @chapter Target Description Macros | |
8 | @cindex machine description macros | |
9 | @cindex target description macros | |
10 | @cindex macros, target description | |
11 | @cindex @file{tm.h} macros | |
12 | ||
13 | In addition to the file @file{@var{machine}.md}, a machine description | |
14 | includes a C header file conventionally given the name | |
15 | @file{@var{machine}.h}. This header file defines numerous macros | |
16 | that convey the information about the target machine that does not fit | |
17 | into the scheme of the @file{.md} file. The file @file{tm.h} should be | |
18 | a link to @file{@var{machine}.h}. The header file @file{config.h} | |
19 | includes @file{tm.h} and most compiler source files include | |
20 | @file{config.h}. | |
21 | ||
22 | @menu | |
23 | * Driver:: Controlling how the driver runs the compilation passes. | |
24 | * Run-time Target:: Defining @samp{-m} options like @samp{-m68000} and @samp{-m68020}. | |
25 | * Storage Layout:: Defining sizes and alignments of data. | |
26 | * Type Layout:: Defining sizes and properties of basic user data types. | |
27 | * Registers:: Naming and describing the hardware registers. | |
28 | * Register Classes:: Defining the classes of hardware registers. | |
29 | * Stack and Calling:: Defining which way the stack grows and by how much. | |
30 | * Varargs:: Defining the varargs macros. | |
31 | * Trampolines:: Code set up at run time to enter a nested function. | |
32 | * Library Calls:: Controlling how library routines are implicitly called. | |
33 | * Addressing Modes:: Defining addressing modes valid for memory operands. | |
34 | * Condition Code:: Defining how insns update the condition code. | |
35 | * Costs:: Defining relative costs of different operations. | |
36 | * Sections:: Dividing storage into text, data, and other sections. | |
37 | * PIC:: Macros for position independent code. | |
38 | * Assembler Format:: Defining how to write insns and pseudo-ops to output. | |
39 | * Debugging Info:: Defining the format of debugging output. | |
40 | * Cross-compilation:: Handling floating point for cross-compilers. | |
9f09b1f2 | 41 | * Mode Switching:: Insertion of mode-switching instructions. |
feca2ed3 JW |
42 | * Misc:: Everything else. |
43 | @end menu | |
44 | ||
45 | @node Driver | |
46 | @section Controlling the Compilation Driver, @file{gcc} | |
47 | @cindex driver | |
48 | @cindex controlling the compilation driver | |
49 | ||
50 | @c prevent bad page break with this line | |
51 | You can control the compilation driver. | |
52 | ||
53 | @table @code | |
54 | @findex SWITCH_TAKES_ARG | |
55 | @item SWITCH_TAKES_ARG (@var{char}) | |
56 | A C expression which determines whether the option @samp{-@var{char}} | |
57 | takes arguments. The value should be the number of arguments that | |
58 | option takes--zero, for many options. | |
59 | ||
60 | By default, this macro is defined as | |
61 | @code{DEFAULT_SWITCH_TAKES_ARG}, which handles the standard options | |
62 | properly. You need not define @code{SWITCH_TAKES_ARG} unless you | |
63 | wish to add additional options which take arguments. Any redefinition | |
64 | should call @code{DEFAULT_SWITCH_TAKES_ARG} and then check for | |
65 | additional options. | |
66 | ||
67 | @findex WORD_SWITCH_TAKES_ARG | |
68 | @item WORD_SWITCH_TAKES_ARG (@var{name}) | |
69 | A C expression which determines whether the option @samp{-@var{name}} | |
70 | takes arguments. The value should be the number of arguments that | |
71 | option takes--zero, for many options. This macro rather than | |
72 | @code{SWITCH_TAKES_ARG} is used for multi-character option names. | |
73 | ||
74 | By default, this macro is defined as | |
75 | @code{DEFAULT_WORD_SWITCH_TAKES_ARG}, which handles the standard options | |
76 | properly. You need not define @code{WORD_SWITCH_TAKES_ARG} unless you | |
77 | wish to add additional options which take arguments. Any redefinition | |
78 | should call @code{DEFAULT_WORD_SWITCH_TAKES_ARG} and then check for | |
79 | additional options. | |
80 | ||
88117d44 NC |
81 | @findex SWITCH_CURTAILS_COMPILATION |
82 | @item SWITCH_CURTAILS_COMPILATION (@var{char}) | |
83 | A C expression which determines whether the option @samp{-@var{char}} | |
84 | stops compilation before the generation of an executable. The value is | |
85 | boolean, non-zero if the option does stop an executable from being | |
86 | generated, zero otherwise. | |
87 | ||
88 | By default, this macro is defined as | |
89 | @code{DEFAULT_SWITCH_CURTAILS_COMPILATION}, which handles the standard | |
90 | options properly. You need not define | |
91 | @code{SWITCH_CURTAILS_COMPILATION} unless you wish to add additional | |
92 | options which affect the generation of an executable. Any redefinition | |
93 | should call @code{DEFAULT_SWITCH_CURTAILS_COMPILATION} and then check | |
94 | for additional options. | |
95 | ||
feca2ed3 JW |
96 | @findex SWITCHES_NEED_SPACES |
97 | @item SWITCHES_NEED_SPACES | |
98 | A string-valued C expression which enumerates the options for which | |
99 | the linker needs a space between the option and its argument. | |
100 | ||
101 | If this macro is not defined, the default value is @code{""}. | |
102 | ||
103 | @findex CPP_SPEC | |
104 | @item CPP_SPEC | |
a3a15b4d | 105 | A C string constant that tells the GCC driver program options to |
feca2ed3 | 106 | pass to CPP. It can also specify how to translate options you |
a3a15b4d | 107 | give to GCC into options for GCC to pass to the CPP. |
feca2ed3 JW |
108 | |
109 | Do not define this macro if it does not need to do anything. | |
110 | ||
111 | @findex NO_BUILTIN_SIZE_TYPE | |
112 | @item NO_BUILTIN_SIZE_TYPE | |
113 | If this macro is defined, the preprocessor will not define the builtin macro | |
114 | @code{__SIZE_TYPE__}. The macro @code{__SIZE_TYPE__} must then be defined | |
115 | by @code{CPP_SPEC} instead. | |
116 | ||
117 | This should be defined if @code{SIZE_TYPE} depends on target dependent flags | |
118 | which are not accessible to the preprocessor. Otherwise, it should not | |
119 | be defined. | |
120 | ||
121 | @findex NO_BUILTIN_PTRDIFF_TYPE | |
122 | @item NO_BUILTIN_PTRDIFF_TYPE | |
123 | If this macro is defined, the preprocessor will not define the builtin macro | |
124 | @code{__PTRDIFF_TYPE__}. The macro @code{__PTRDIFF_TYPE__} must then be | |
125 | defined by @code{CPP_SPEC} instead. | |
126 | ||
127 | This should be defined if @code{PTRDIFF_TYPE} depends on target dependent flags | |
128 | which are not accessible to the preprocessor. Otherwise, it should not | |
0209c340 ZW |
129 | be defined. |
130 | ||
131 | @findex NO_BUILTIN_WCHAR_TYPE | |
132 | @item NO_BUILTIN_WCHAR_TYPE | |
133 | If this macro is defined, the preprocessor will not define the builtin macro | |
134 | @code{__WCHAR_TYPE__}. The macro @code{__WCHAR_TYPE__} must then be | |
135 | defined by @code{CPP_SPEC} instead. | |
136 | ||
137 | This should be defined if @code{WCHAR_TYPE} depends on target dependent flags | |
138 | which are not accessible to the preprocessor. Otherwise, it should not | |
feca2ed3 JW |
139 | be defined. |
140 | ||
141 | @findex SIGNED_CHAR_SPEC | |
142 | @item SIGNED_CHAR_SPEC | |
a3a15b4d | 143 | A C string constant that tells the GCC driver program options to |
feca2ed3 JW |
144 | pass to CPP. By default, this macro is defined to pass the option |
145 | @samp{-D__CHAR_UNSIGNED__} to CPP if @code{char} will be treated as | |
146 | @code{unsigned char} by @code{cc1}. | |
147 | ||
148 | Do not define this macro unless you need to override the default | |
149 | definition. | |
150 | ||
151 | @findex CC1_SPEC | |
152 | @item CC1_SPEC | |
a3a15b4d | 153 | A C string constant that tells the GCC driver program options to |
66519c70 JL |
154 | pass to @code{cc1}, @code{cc1plus}, @code{f771}, and the other language |
155 | front ends. | |
a3a15b4d JL |
156 | It can also specify how to translate options you give to GCC into options |
157 | for GCC to pass to front ends.. | |
feca2ed3 JW |
158 | |
159 | Do not define this macro if it does not need to do anything. | |
160 | ||
161 | @findex CC1PLUS_SPEC | |
162 | @item CC1PLUS_SPEC | |
a3a15b4d | 163 | A C string constant that tells the GCC driver program options to |
feca2ed3 | 164 | pass to @code{cc1plus}. It can also specify how to translate options you |
a3a15b4d | 165 | give to GCC into options for GCC to pass to the @code{cc1plus}. |
feca2ed3 JW |
166 | |
167 | Do not define this macro if it does not need to do anything. | |
1d96e5b4 FF |
168 | Note that everything defined in CC1_SPEC is already passed to |
169 | @code{cc1plus} so there is no need to duplicate the contents of | |
170 | CC1_SPEC in CC1PLUS_SPEC. | |
feca2ed3 JW |
171 | |
172 | @findex ASM_SPEC | |
173 | @item ASM_SPEC | |
a3a15b4d | 174 | A C string constant that tells the GCC driver program options to |
feca2ed3 | 175 | pass to the assembler. It can also specify how to translate options |
a3a15b4d | 176 | you give to GCC into options for GCC to pass to the assembler. |
feca2ed3 JW |
177 | See the file @file{sun3.h} for an example of this. |
178 | ||
179 | Do not define this macro if it does not need to do anything. | |
180 | ||
181 | @findex ASM_FINAL_SPEC | |
182 | @item ASM_FINAL_SPEC | |
a3a15b4d | 183 | A C string constant that tells the GCC driver program how to |
feca2ed3 JW |
184 | run any programs which cleanup after the normal assembler. |
185 | Normally, this is not needed. See the file @file{mips.h} for | |
186 | an example of this. | |
187 | ||
188 | Do not define this macro if it does not need to do anything. | |
189 | ||
190 | @findex LINK_SPEC | |
191 | @item LINK_SPEC | |
a3a15b4d | 192 | A C string constant that tells the GCC driver program options to |
feca2ed3 | 193 | pass to the linker. It can also specify how to translate options you |
a3a15b4d | 194 | give to GCC into options for GCC to pass to the linker. |
feca2ed3 JW |
195 | |
196 | Do not define this macro if it does not need to do anything. | |
197 | ||
198 | @findex LIB_SPEC | |
199 | @item LIB_SPEC | |
200 | Another C string constant used much like @code{LINK_SPEC}. The difference | |
201 | between the two is that @code{LIB_SPEC} is used at the end of the | |
202 | command given to the linker. | |
203 | ||
204 | If this macro is not defined, a default is provided that | |
205 | loads the standard C library from the usual place. See @file{gcc.c}. | |
206 | ||
207 | @findex LIBGCC_SPEC | |
208 | @item LIBGCC_SPEC | |
a3a15b4d | 209 | Another C string constant that tells the GCC driver program |
feca2ed3 JW |
210 | how and when to place a reference to @file{libgcc.a} into the |
211 | linker command line. This constant is placed both before and after | |
212 | the value of @code{LIB_SPEC}. | |
213 | ||
a3a15b4d | 214 | If this macro is not defined, the GCC driver provides a default that |
feca2ed3 JW |
215 | passes the string @samp{-lgcc} to the linker unless the @samp{-shared} |
216 | option is specified. | |
217 | ||
218 | @findex STARTFILE_SPEC | |
219 | @item STARTFILE_SPEC | |
220 | Another C string constant used much like @code{LINK_SPEC}. The | |
221 | difference between the two is that @code{STARTFILE_SPEC} is used at | |
222 | the very beginning of the command given to the linker. | |
223 | ||
224 | If this macro is not defined, a default is provided that loads the | |
225 | standard C startup file from the usual place. See @file{gcc.c}. | |
226 | ||
227 | @findex ENDFILE_SPEC | |
228 | @item ENDFILE_SPEC | |
229 | Another C string constant used much like @code{LINK_SPEC}. The | |
230 | difference between the two is that @code{ENDFILE_SPEC} is used at | |
231 | the very end of the command given to the linker. | |
232 | ||
233 | Do not define this macro if it does not need to do anything. | |
234 | ||
235 | @findex EXTRA_SPECS | |
236 | @item EXTRA_SPECS | |
237 | Define this macro to provide additional specifications to put in the | |
238 | @file{specs} file that can be used in various specifications like | |
239 | @code{CC1_SPEC}. | |
240 | ||
241 | The definition should be an initializer for an array of structures, | |
242 | containing a string constant, that defines the specification name, and a | |
243 | string constant that provides the specification. | |
244 | ||
245 | Do not define this macro if it does not need to do anything. | |
246 | ||
247 | @code{EXTRA_SPECS} is useful when an architecture contains several | |
248 | related targets, which have various @code{..._SPECS} which are similar | |
249 | to each other, and the maintainer would like one central place to keep | |
250 | these definitions. | |
251 | ||
252 | For example, the PowerPC System V.4 targets use @code{EXTRA_SPECS} to | |
253 | define either @code{_CALL_SYSV} when the System V calling sequence is | |
254 | used or @code{_CALL_AIX} when the older AIX-based calling sequence is | |
255 | used. | |
256 | ||
257 | The @file{config/rs6000/rs6000.h} target file defines: | |
258 | ||
259 | @example | |
260 | #define EXTRA_SPECS \ | |
261 | @{ "cpp_sysv_default", CPP_SYSV_DEFAULT @}, | |
262 | ||
263 | #define CPP_SYS_DEFAULT "" | |
264 | @end example | |
265 | ||
266 | The @file{config/rs6000/sysv.h} target file defines: | |
267 | @smallexample | |
268 | #undef CPP_SPEC | |
269 | #define CPP_SPEC \ | |
270 | "%@{posix: -D_POSIX_SOURCE @} \ | |
271 | %@{mcall-sysv: -D_CALL_SYSV @} %@{mcall-aix: -D_CALL_AIX @} \ | |
272 | %@{!mcall-sysv: %@{!mcall-aix: %(cpp_sysv_default) @}@} \ | |
273 | %@{msoft-float: -D_SOFT_FLOAT@} %@{mcpu=403: -D_SOFT_FLOAT@}" | |
274 | ||
275 | #undef CPP_SYSV_DEFAULT | |
276 | #define CPP_SYSV_DEFAULT "-D_CALL_SYSV" | |
277 | @end smallexample | |
278 | ||
279 | while the @file{config/rs6000/eabiaix.h} target file defines | |
280 | @code{CPP_SYSV_DEFAULT} as: | |
281 | ||
282 | @smallexample | |
283 | #undef CPP_SYSV_DEFAULT | |
284 | #define CPP_SYSV_DEFAULT "-D_CALL_AIX" | |
285 | @end smallexample | |
286 | ||
287 | @findex LINK_LIBGCC_SPECIAL | |
288 | @item LINK_LIBGCC_SPECIAL | |
289 | Define this macro if the driver program should find the library | |
290 | @file{libgcc.a} itself and should not pass @samp{-L} options to the | |
291 | linker. If you do not define this macro, the driver program will pass | |
292 | the argument @samp{-lgcc} to tell the linker to do the search and will | |
293 | pass @samp{-L} options to it. | |
294 | ||
295 | @findex LINK_LIBGCC_SPECIAL_1 | |
296 | @item LINK_LIBGCC_SPECIAL_1 | |
297 | Define this macro if the driver program should find the library | |
298 | @file{libgcc.a}. If you do not define this macro, the driver program will pass | |
299 | the argument @samp{-lgcc} to tell the linker to do the search. | |
300 | This macro is similar to @code{LINK_LIBGCC_SPECIAL}, except that it does | |
301 | not affect @samp{-L} options. | |
302 | ||
9ec36da5 JL |
303 | @findex LINK_COMMAND_SPEC |
304 | @item LINK_COMMAND_SPEC | |
305 | A C string constant giving the complete command line need to execute the | |
306 | linker. When you do this, you will need to update your port each time a | |
307 | change is made to the link command line within @file{gcc.c}. Therefore, | |
308 | define this macro only if you need to completely redefine the command | |
309 | line for invoking the linker and there is no other way to accomplish | |
310 | the effect you need. | |
311 | ||
feca2ed3 JW |
312 | @findex MULTILIB_DEFAULTS |
313 | @item MULTILIB_DEFAULTS | |
314 | Define this macro as a C expression for the initializer of an array of | |
315 | string to tell the driver program which options are defaults for this | |
316 | target and thus do not need to be handled specially when using | |
317 | @code{MULTILIB_OPTIONS}. | |
318 | ||
319 | Do not define this macro if @code{MULTILIB_OPTIONS} is not defined in | |
320 | the target makefile fragment or if none of the options listed in | |
321 | @code{MULTILIB_OPTIONS} are set by default. | |
322 | @xref{Target Fragment}. | |
323 | ||
324 | @findex RELATIVE_PREFIX_NOT_LINKDIR | |
325 | @item RELATIVE_PREFIX_NOT_LINKDIR | |
326 | Define this macro to tell @code{gcc} that it should only translate | |
327 | a @samp{-B} prefix into a @samp{-L} linker option if the prefix | |
328 | indicates an absolute file name. | |
329 | ||
330 | @findex STANDARD_EXEC_PREFIX | |
331 | @item STANDARD_EXEC_PREFIX | |
332 | Define this macro as a C string constant if you wish to override the | |
333 | standard choice of @file{/usr/local/lib/gcc-lib/} as the default prefix to | |
334 | try when searching for the executable files of the compiler. | |
335 | ||
336 | @findex MD_EXEC_PREFIX | |
337 | @item MD_EXEC_PREFIX | |
338 | If defined, this macro is an additional prefix to try after | |
339 | @code{STANDARD_EXEC_PREFIX}. @code{MD_EXEC_PREFIX} is not searched | |
340 | when the @samp{-b} option is used, or the compiler is built as a cross | |
5505263f JL |
341 | compiler. If you define @code{MD_EXEC_PREFIX}, then be sure to add it |
342 | to the list of directories used to find the assembler in @file{configure.in}. | |
feca2ed3 JW |
343 | |
344 | @findex STANDARD_STARTFILE_PREFIX | |
345 | @item STANDARD_STARTFILE_PREFIX | |
346 | Define this macro as a C string constant if you wish to override the | |
347 | standard choice of @file{/usr/local/lib/} as the default prefix to | |
348 | try when searching for startup files such as @file{crt0.o}. | |
349 | ||
350 | @findex MD_STARTFILE_PREFIX | |
351 | @item MD_STARTFILE_PREFIX | |
352 | If defined, this macro supplies an additional prefix to try after the | |
353 | standard prefixes. @code{MD_EXEC_PREFIX} is not searched when the | |
354 | @samp{-b} option is used, or when the compiler is built as a cross | |
355 | compiler. | |
356 | ||
357 | @findex MD_STARTFILE_PREFIX_1 | |
358 | @item MD_STARTFILE_PREFIX_1 | |
359 | If defined, this macro supplies yet another prefix to try after the | |
360 | standard prefixes. It is not searched when the @samp{-b} option is | |
361 | used, or when the compiler is built as a cross compiler. | |
362 | ||
363 | @findex INIT_ENVIRONMENT | |
364 | @item INIT_ENVIRONMENT | |
e9a25f70 | 365 | Define this macro as a C string constant if you wish to set environment |
feca2ed3 JW |
366 | variables for programs called by the driver, such as the assembler and |
367 | loader. The driver passes the value of this macro to @code{putenv} to | |
368 | initialize the necessary environment variables. | |
369 | ||
370 | @findex LOCAL_INCLUDE_DIR | |
371 | @item LOCAL_INCLUDE_DIR | |
372 | Define this macro as a C string constant if you wish to override the | |
373 | standard choice of @file{/usr/local/include} as the default prefix to | |
374 | try when searching for local header files. @code{LOCAL_INCLUDE_DIR} | |
375 | comes before @code{SYSTEM_INCLUDE_DIR} in the search order. | |
376 | ||
377 | Cross compilers do not use this macro and do not search either | |
378 | @file{/usr/local/include} or its replacement. | |
379 | ||
380 | @findex SYSTEM_INCLUDE_DIR | |
381 | @item SYSTEM_INCLUDE_DIR | |
382 | Define this macro as a C string constant if you wish to specify a | |
383 | system-specific directory to search for header files before the standard | |
384 | directory. @code{SYSTEM_INCLUDE_DIR} comes before | |
385 | @code{STANDARD_INCLUDE_DIR} in the search order. | |
386 | ||
387 | Cross compilers do not use this macro and do not search the directory | |
388 | specified. | |
389 | ||
390 | @findex STANDARD_INCLUDE_DIR | |
391 | @item STANDARD_INCLUDE_DIR | |
392 | Define this macro as a C string constant if you wish to override the | |
393 | standard choice of @file{/usr/include} as the default prefix to | |
394 | try when searching for header files. | |
395 | ||
396 | Cross compilers do not use this macro and do not search either | |
397 | @file{/usr/include} or its replacement. | |
398 | ||
e9a25f70 JL |
399 | @findex STANDARD_INCLUDE_COMPONENT |
400 | @item STANDARD_INCLUDE_COMPONENT | |
401 | The ``component'' corresponding to @code{STANDARD_INCLUDE_DIR}. | |
402 | See @code{INCLUDE_DEFAULTS}, below, for the description of components. | |
403 | If you do not define this macro, no component is used. | |
404 | ||
feca2ed3 JW |
405 | @findex INCLUDE_DEFAULTS |
406 | @item INCLUDE_DEFAULTS | |
407 | Define this macro if you wish to override the entire default search path | |
e9a25f70 JL |
408 | for include files. For a native compiler, the default search path |
409 | usually consists of @code{GCC_INCLUDE_DIR}, @code{LOCAL_INCLUDE_DIR}, | |
feca2ed3 JW |
410 | @code{SYSTEM_INCLUDE_DIR}, @code{GPLUSPLUS_INCLUDE_DIR}, and |
411 | @code{STANDARD_INCLUDE_DIR}. In addition, @code{GPLUSPLUS_INCLUDE_DIR} | |
412 | and @code{GCC_INCLUDE_DIR} are defined automatically by @file{Makefile}, | |
413 | and specify private search areas for GCC. The directory | |
414 | @code{GPLUSPLUS_INCLUDE_DIR} is used only for C++ programs. | |
415 | ||
416 | The definition should be an initializer for an array of structures. | |
e9a25f70 | 417 | Each array element should have four elements: the directory name (a |
9f6dc500 HPN |
418 | string constant), the component name (also a string constant), a flag |
419 | for C++-only directories, | |
e9a25f70 JL |
420 | and a flag showing that the includes in the directory don't need to be |
421 | wrapped in @code{extern @samp{C}} when compiling C++. Mark the end of | |
422 | the array with a null element. | |
423 | ||
424 | The component name denotes what GNU package the include file is part of, | |
425 | if any, in all upper-case letters. For example, it might be @samp{GCC} | |
9f6dc500 | 426 | or @samp{BINUTILS}. If the package is part of a vendor-supplied |
e9a25f70 JL |
427 | operating system, code the component name as @samp{0}. |
428 | ||
e9a25f70 | 429 | For example, here is the definition used for VAX/VMS: |
feca2ed3 JW |
430 | |
431 | @example | |
432 | #define INCLUDE_DEFAULTS \ | |
433 | @{ \ | |
e9a25f70 JL |
434 | @{ "GNU_GXX_INCLUDE:", "G++", 1, 1@}, \ |
435 | @{ "GNU_CC_INCLUDE:", "GCC", 0, 0@}, \ | |
436 | @{ "SYS$SYSROOT:[SYSLIB.]", 0, 0, 0@}, \ | |
437 | @{ ".", 0, 0, 0@}, \ | |
438 | @{ 0, 0, 0, 0@} \ | |
feca2ed3 JW |
439 | @} |
440 | @end example | |
441 | @end table | |
442 | ||
443 | Here is the order of prefixes tried for exec files: | |
444 | ||
445 | @enumerate | |
446 | @item | |
447 | Any prefixes specified by the user with @samp{-B}. | |
448 | ||
449 | @item | |
450 | The environment variable @code{GCC_EXEC_PREFIX}, if any. | |
451 | ||
452 | @item | |
453 | The directories specified by the environment variable @code{COMPILER_PATH}. | |
454 | ||
455 | @item | |
456 | The macro @code{STANDARD_EXEC_PREFIX}. | |
457 | ||
458 | @item | |
459 | @file{/usr/lib/gcc/}. | |
460 | ||
461 | @item | |
462 | The macro @code{MD_EXEC_PREFIX}, if any. | |
463 | @end enumerate | |
464 | ||
465 | Here is the order of prefixes tried for startfiles: | |
466 | ||
467 | @enumerate | |
468 | @item | |
469 | Any prefixes specified by the user with @samp{-B}. | |
470 | ||
471 | @item | |
472 | The environment variable @code{GCC_EXEC_PREFIX}, if any. | |
473 | ||
474 | @item | |
475 | The directories specified by the environment variable @code{LIBRARY_PATH} | |
512b62fb | 476 | (or port-specific name; native only, cross compilers do not use this). |
feca2ed3 JW |
477 | |
478 | @item | |
479 | The macro @code{STANDARD_EXEC_PREFIX}. | |
480 | ||
481 | @item | |
482 | @file{/usr/lib/gcc/}. | |
483 | ||
484 | @item | |
485 | The macro @code{MD_EXEC_PREFIX}, if any. | |
486 | ||
487 | @item | |
488 | The macro @code{MD_STARTFILE_PREFIX}, if any. | |
489 | ||
490 | @item | |
491 | The macro @code{STANDARD_STARTFILE_PREFIX}. | |
492 | ||
493 | @item | |
494 | @file{/lib/}. | |
495 | ||
496 | @item | |
497 | @file{/usr/lib/}. | |
498 | @end enumerate | |
499 | ||
500 | @node Run-time Target | |
501 | @section Run-time Target Specification | |
502 | @cindex run-time target specification | |
503 | @cindex predefined macros | |
504 | @cindex target specifications | |
505 | ||
506 | @c prevent bad page break with this line | |
507 | Here are run-time target specifications. | |
508 | ||
509 | @table @code | |
510 | @findex CPP_PREDEFINES | |
511 | @item CPP_PREDEFINES | |
512 | Define this to be a string constant containing @samp{-D} options to | |
513 | define the predefined macros that identify this machine and system. | |
514 | These macros will be predefined unless the @samp{-ansi} option is | |
515 | specified. | |
516 | ||
517 | In addition, a parallel set of macros are predefined, whose names are | |
518 | made by appending @samp{__} at the beginning and at the end. These | |
519 | @samp{__} macros are permitted by the ANSI standard, so they are | |
520 | predefined regardless of whether @samp{-ansi} is specified. | |
521 | ||
522 | For example, on the Sun, one can use the following value: | |
523 | ||
524 | @smallexample | |
525 | "-Dmc68000 -Dsun -Dunix" | |
526 | @end smallexample | |
527 | ||
528 | The result is to define the macros @code{__mc68000__}, @code{__sun__} | |
529 | and @code{__unix__} unconditionally, and the macros @code{mc68000}, | |
530 | @code{sun} and @code{unix} provided @samp{-ansi} is not specified. | |
531 | ||
532 | @findex extern int target_flags | |
533 | @item extern int target_flags; | |
534 | This declaration should be present. | |
535 | ||
536 | @cindex optional hardware or system features | |
537 | @cindex features, optional, in system conventions | |
538 | @item TARGET_@dots{} | |
539 | This series of macros is to allow compiler command arguments to | |
540 | enable or disable the use of optional features of the target machine. | |
541 | For example, one machine description serves both the 68000 and | |
542 | the 68020; a command argument tells the compiler whether it should | |
543 | use 68020-only instructions or not. This command argument works | |
544 | by means of a macro @code{TARGET_68020} that tests a bit in | |
545 | @code{target_flags}. | |
546 | ||
547 | Define a macro @code{TARGET_@var{featurename}} for each such option. | |
9f6dc500 HPN |
548 | Its definition should test a bit in @code{target_flags}. It is |
549 | recommended that a helper macro @code{TARGET_MASK_@var{featurename}} | |
550 | is defined for each bit-value to test, and used in | |
551 | @code{TARGET_@var{featurename}} and @code{TARGET_SWITCHES}. For | |
552 | example: | |
feca2ed3 JW |
553 | |
554 | @smallexample | |
9f6dc500 HPN |
555 | #define TARGET_MASK_68020 1 |
556 | #define TARGET_68020 (target_flags & TARGET_MASK_68020) | |
feca2ed3 JW |
557 | @end smallexample |
558 | ||
559 | One place where these macros are used is in the condition-expressions | |
560 | of instruction patterns. Note how @code{TARGET_68020} appears | |
561 | frequently in the 68000 machine description file, @file{m68k.md}. | |
562 | Another place they are used is in the definitions of the other | |
563 | macros in the @file{@var{machine}.h} file. | |
564 | ||
565 | @findex TARGET_SWITCHES | |
566 | @item TARGET_SWITCHES | |
567 | This macro defines names of command options to set and clear | |
568 | bits in @code{target_flags}. Its definition is an initializer | |
569 | with a subgrouping for each command option. | |
570 | ||
571 | Each subgrouping contains a string constant, that defines the option | |
b8468bc7 NC |
572 | name, a number, which contains the bits to set in |
573 | @code{target_flags}, and a second string which is the description | |
574 | displayed by --help. If the number is negative then the bits specified | |
575 | by the number are cleared instead of being set. If the description | |
576 | string is present but empty, then no help information will be displayed | |
577 | for that option, but it will not count as an undocumented option. The | |
578 | actual option name is made by appending @samp{-m} to the specified name. | |
feca2ed3 JW |
579 | |
580 | One of the subgroupings should have a null string. The number in | |
581 | this grouping is the default value for @code{target_flags}. Any | |
582 | target options act starting with that value. | |
583 | ||
584 | Here is an example which defines @samp{-m68000} and @samp{-m68020} | |
585 | with opposite meanings, and picks the latter as the default: | |
586 | ||
587 | @smallexample | |
588 | #define TARGET_SWITCHES \ | |
9f6dc500 HPN |
589 | @{ @{ "68020", TARGET_MASK_68020, "" @}, \ |
590 | @{ "68000", -TARGET_MASK_68020, "Compile for the 68000" @}, \ | |
591 | @{ "", TARGET_MASK_68020, "" @}@} | |
feca2ed3 JW |
592 | @end smallexample |
593 | ||
594 | @findex TARGET_OPTIONS | |
595 | @item TARGET_OPTIONS | |
596 | This macro is similar to @code{TARGET_SWITCHES} but defines names of command | |
597 | options that have values. Its definition is an initializer with a | |
598 | subgrouping for each command option. | |
599 | ||
600 | Each subgrouping contains a string constant, that defines the fixed part | |
b8468bc7 NC |
601 | of the option name, the address of a variable, and a description string. |
602 | The variable, type @code{char *}, is set to the variable part of the | |
603 | given option if the fixed part matches. The actual option name is made | |
604 | by appending @samp{-m} to the specified name. | |
feca2ed3 JW |
605 | |
606 | Here is an example which defines @samp{-mshort-data-@var{number}}. If the | |
607 | given option is @samp{-mshort-data-512}, the variable @code{m88k_short_data} | |
608 | will be set to the string @code{"512"}. | |
609 | ||
610 | @smallexample | |
611 | extern char *m88k_short_data; | |
612 | #define TARGET_OPTIONS \ | |
b8468bc7 | 613 | @{ @{ "short-data-", &m88k_short_data, "Specify the size of the short data section" @} @} |
feca2ed3 JW |
614 | @end smallexample |
615 | ||
616 | @findex TARGET_VERSION | |
617 | @item TARGET_VERSION | |
618 | This macro is a C statement to print on @code{stderr} a string | |
619 | describing the particular machine description choice. Every machine | |
620 | description should define @code{TARGET_VERSION}. For example: | |
621 | ||
622 | @smallexample | |
623 | #ifdef MOTOROLA | |
624 | #define TARGET_VERSION \ | |
625 | fprintf (stderr, " (68k, Motorola syntax)"); | |
626 | #else | |
627 | #define TARGET_VERSION \ | |
628 | fprintf (stderr, " (68k, MIT syntax)"); | |
629 | #endif | |
630 | @end smallexample | |
631 | ||
632 | @findex OVERRIDE_OPTIONS | |
633 | @item OVERRIDE_OPTIONS | |
634 | Sometimes certain combinations of command options do not make sense on | |
635 | a particular target machine. You can define a macro | |
636 | @code{OVERRIDE_OPTIONS} to take account of this. This macro, if | |
637 | defined, is executed once just after all the command options have been | |
638 | parsed. | |
639 | ||
640 | Don't use this macro to turn on various extra optimizations for | |
641 | @samp{-O}. That is what @code{OPTIMIZATION_OPTIONS} is for. | |
642 | ||
643 | @findex OPTIMIZATION_OPTIONS | |
c6aded7c | 644 | @item OPTIMIZATION_OPTIONS (@var{level}, @var{size}) |
feca2ed3 JW |
645 | Some machines may desire to change what optimizations are performed for |
646 | various optimization levels. This macro, if defined, is executed once | |
647 | just after the optimization level is determined and before the remainder | |
648 | of the command options have been parsed. Values set in this macro are | |
649 | used as the default values for the other command line options. | |
650 | ||
651 | @var{level} is the optimization level specified; 2 if @samp{-O2} is | |
652 | specified, 1 if @samp{-O} is specified, and 0 if neither is specified. | |
653 | ||
c6aded7c AG |
654 | @var{size} is non-zero if @samp{-Os} is specified and zero otherwise. |
655 | ||
feca2ed3 JW |
656 | You should not use this macro to change options that are not |
657 | machine-specific. These should uniformly selected by the same | |
658 | optimization level on all supported machines. Use this macro to enable | |
659 | machine-specific optimizations. | |
660 | ||
661 | @strong{Do not examine @code{write_symbols} in | |
662 | this macro!} The debugging options are not supposed to alter the | |
663 | generated code. | |
664 | ||
665 | @findex CAN_DEBUG_WITHOUT_FP | |
666 | @item CAN_DEBUG_WITHOUT_FP | |
667 | Define this macro if debugging can be performed even without a frame | |
a3a15b4d | 668 | pointer. If this macro is defined, GCC will turn on the |
feca2ed3 JW |
669 | @samp{-fomit-frame-pointer} option whenever @samp{-O} is specified. |
670 | @end table | |
671 | ||
672 | @node Storage Layout | |
673 | @section Storage Layout | |
674 | @cindex storage layout | |
675 | ||
676 | Note that the definitions of the macros in this table which are sizes or | |
677 | alignments measured in bits do not need to be constant. They can be C | |
678 | expressions that refer to static variables, such as the @code{target_flags}. | |
679 | @xref{Run-time Target}. | |
680 | ||
681 | @table @code | |
682 | @findex BITS_BIG_ENDIAN | |
683 | @item BITS_BIG_ENDIAN | |
684 | Define this macro to have the value 1 if the most significant bit in a | |
685 | byte has the lowest number; otherwise define it to have the value zero. | |
686 | This means that bit-field instructions count from the most significant | |
687 | bit. If the machine has no bit-field instructions, then this must still | |
688 | be defined, but it doesn't matter which value it is defined to. This | |
689 | macro need not be a constant. | |
690 | ||
691 | This macro does not affect the way structure fields are packed into | |
692 | bytes or words; that is controlled by @code{BYTES_BIG_ENDIAN}. | |
693 | ||
694 | @findex BYTES_BIG_ENDIAN | |
695 | @item BYTES_BIG_ENDIAN | |
696 | Define this macro to have the value 1 if the most significant byte in a | |
697 | word has the lowest number. This macro need not be a constant. | |
698 | ||
699 | @findex WORDS_BIG_ENDIAN | |
700 | @item WORDS_BIG_ENDIAN | |
701 | Define this macro to have the value 1 if, in a multiword object, the | |
702 | most significant word has the lowest number. This applies to both | |
a3a15b4d | 703 | memory locations and registers; GCC fundamentally assumes that the |
feca2ed3 JW |
704 | order of words in memory is the same as the order in registers. This |
705 | macro need not be a constant. | |
706 | ||
707 | @findex LIBGCC2_WORDS_BIG_ENDIAN | |
708 | @item LIBGCC2_WORDS_BIG_ENDIAN | |
709 | Define this macro if WORDS_BIG_ENDIAN is not constant. This must be a | |
710 | constant value with the same meaning as WORDS_BIG_ENDIAN, which will be | |
711 | used only when compiling libgcc2.c. Typically the value will be set | |
712 | based on preprocessor defines. | |
713 | ||
714 | @findex FLOAT_WORDS_BIG_ENDIAN | |
715 | @item FLOAT_WORDS_BIG_ENDIAN | |
716 | Define this macro to have the value 1 if @code{DFmode}, @code{XFmode} or | |
717 | @code{TFmode} floating point numbers are stored in memory with the word | |
718 | containing the sign bit at the lowest address; otherwise define it to | |
719 | have the value 0. This macro need not be a constant. | |
720 | ||
721 | You need not define this macro if the ordering is the same as for | |
722 | multi-word integers. | |
723 | ||
724 | @findex BITS_PER_UNIT | |
725 | @item BITS_PER_UNIT | |
726 | Define this macro to be the number of bits in an addressable storage | |
727 | unit (byte); normally 8. | |
728 | ||
729 | @findex BITS_PER_WORD | |
730 | @item BITS_PER_WORD | |
731 | Number of bits in a word; normally 32. | |
732 | ||
733 | @findex MAX_BITS_PER_WORD | |
734 | @item MAX_BITS_PER_WORD | |
735 | Maximum number of bits in a word. If this is undefined, the default is | |
736 | @code{BITS_PER_WORD}. Otherwise, it is the constant value that is the | |
737 | largest value that @code{BITS_PER_WORD} can have at run-time. | |
738 | ||
739 | @findex UNITS_PER_WORD | |
740 | @item UNITS_PER_WORD | |
741 | Number of storage units in a word; normally 4. | |
742 | ||
743 | @findex MIN_UNITS_PER_WORD | |
744 | @item MIN_UNITS_PER_WORD | |
745 | Minimum number of units in a word. If this is undefined, the default is | |
746 | @code{UNITS_PER_WORD}. Otherwise, it is the constant value that is the | |
747 | smallest value that @code{UNITS_PER_WORD} can have at run-time. | |
748 | ||
749 | @findex POINTER_SIZE | |
750 | @item POINTER_SIZE | |
751 | Width of a pointer, in bits. You must specify a value no wider than the | |
752 | width of @code{Pmode}. If it is not equal to the width of @code{Pmode}, | |
753 | you must define @code{POINTERS_EXTEND_UNSIGNED}. | |
754 | ||
755 | @findex POINTERS_EXTEND_UNSIGNED | |
756 | @item POINTERS_EXTEND_UNSIGNED | |
757 | A C expression whose value is nonzero if pointers that need to be | |
f5963e61 JL |
758 | extended from being @code{POINTER_SIZE} bits wide to @code{Pmode} are to |
759 | be zero-extended and zero if they are to be sign-extended. | |
feca2ed3 JW |
760 | |
761 | You need not define this macro if the @code{POINTER_SIZE} is equal | |
762 | to the width of @code{Pmode}. | |
763 | ||
764 | @findex PROMOTE_MODE | |
765 | @item PROMOTE_MODE (@var{m}, @var{unsignedp}, @var{type}) | |
766 | A macro to update @var{m} and @var{unsignedp} when an object whose type | |
767 | is @var{type} and which has the specified mode and signedness is to be | |
768 | stored in a register. This macro is only called when @var{type} is a | |
769 | scalar type. | |
770 | ||
771 | On most RISC machines, which only have operations that operate on a full | |
772 | register, define this macro to set @var{m} to @code{word_mode} if | |
773 | @var{m} is an integer mode narrower than @code{BITS_PER_WORD}. In most | |
774 | cases, only integer modes should be widened because wider-precision | |
775 | floating-point operations are usually more expensive than their narrower | |
776 | counterparts. | |
777 | ||
778 | For most machines, the macro definition does not change @var{unsignedp}. | |
779 | However, some machines, have instructions that preferentially handle | |
780 | either signed or unsigned quantities of certain modes. For example, on | |
781 | the DEC Alpha, 32-bit loads from memory and 32-bit add instructions | |
782 | sign-extend the result to 64 bits. On such machines, set | |
783 | @var{unsignedp} according to which kind of extension is more efficient. | |
784 | ||
785 | Do not define this macro if it would never modify @var{m}. | |
786 | ||
787 | @findex PROMOTE_FUNCTION_ARGS | |
788 | @item PROMOTE_FUNCTION_ARGS | |
789 | Define this macro if the promotion described by @code{PROMOTE_MODE} | |
790 | should also be done for outgoing function arguments. | |
791 | ||
792 | @findex PROMOTE_FUNCTION_RETURN | |
793 | @item PROMOTE_FUNCTION_RETURN | |
794 | Define this macro if the promotion described by @code{PROMOTE_MODE} | |
795 | should also be done for the return value of functions. | |
796 | ||
797 | If this macro is defined, @code{FUNCTION_VALUE} must perform the same | |
798 | promotions done by @code{PROMOTE_MODE}. | |
799 | ||
800 | @findex PROMOTE_FOR_CALL_ONLY | |
801 | @item PROMOTE_FOR_CALL_ONLY | |
802 | Define this macro if the promotion described by @code{PROMOTE_MODE} | |
803 | should @emph{only} be performed for outgoing function arguments or | |
804 | function return values, as specified by @code{PROMOTE_FUNCTION_ARGS} | |
805 | and @code{PROMOTE_FUNCTION_RETURN}, respectively. | |
806 | ||
807 | @findex PARM_BOUNDARY | |
808 | @item PARM_BOUNDARY | |
809 | Normal alignment required for function parameters on the stack, in | |
810 | bits. All stack parameters receive at least this much alignment | |
811 | regardless of data type. On most machines, this is the same as the | |
812 | size of an integer. | |
813 | ||
814 | @findex STACK_BOUNDARY | |
815 | @item STACK_BOUNDARY | |
c795bca9 BS |
816 | Define this macro if there is a guaranteed alignment for the stack |
817 | pointer on this machine. The definition is a C expression | |
818 | for the desired alignment (measured in bits). This value is used as a | |
819 | default if PREFERRED_STACK_BOUNDARY is not defined. | |
820 | ||
821 | @findex PREFERRED_STACK_BOUNDARY | |
822 | @item PREFERRED_STACK_BOUNDARY | |
feca2ed3 JW |
823 | Define this macro if you wish to preserve a certain alignment for |
824 | the stack pointer. The definition is a C expression | |
c795bca9 BS |
825 | for the desired alignment (measured in bits). If STACK_BOUNDARY is |
826 | also defined, this macro must evaluate to a value equal to or larger | |
827 | than STACK_BOUNDARY. | |
feca2ed3 | 828 | |
c795bca9 | 829 | @cindex @code{PUSH_ROUNDING}, interaction with @code{PREFERRED_STACK_BOUNDARY} |
feca2ed3 | 830 | If @code{PUSH_ROUNDING} is not defined, the stack will always be aligned |
c795bca9 BS |
831 | to the specified boundary. If @code{PUSH_ROUNDING} is defined and specifies |
832 | a less strict alignment than @code{PREFERRED_STACK_BOUNDARY}, the stack may | |
833 | be momentarily unaligned while pushing arguments. | |
feca2ed3 JW |
834 | |
835 | @findex FUNCTION_BOUNDARY | |
836 | @item FUNCTION_BOUNDARY | |
837 | Alignment required for a function entry point, in bits. | |
838 | ||
839 | @findex BIGGEST_ALIGNMENT | |
840 | @item BIGGEST_ALIGNMENT | |
841 | Biggest alignment that any data type can require on this machine, in bits. | |
842 | ||
861bb6c1 JL |
843 | @findex MINIMUM_ATOMIC_ALIGNMENT |
844 | @item MINIMUM_ATOMIC_ALIGNMENT | |
845 | If defined, the smallest alignment, in bits, that can be given to an | |
846 | object that can be referenced in one operation, without disturbing any | |
847 | nearby object. Normally, this is @code{BITS_PER_UNIT}, but may be larger | |
848 | on machines that don't have byte or half-word store operations. | |
849 | ||
feca2ed3 JW |
850 | @findex BIGGEST_FIELD_ALIGNMENT |
851 | @item BIGGEST_FIELD_ALIGNMENT | |
852 | Biggest alignment that any structure field can require on this machine, | |
853 | in bits. If defined, this overrides @code{BIGGEST_ALIGNMENT} for | |
854 | structure fields only. | |
855 | ||
856 | @findex ADJUST_FIELD_ALIGN | |
857 | @item ADJUST_FIELD_ALIGN (@var{field}, @var{computed}) | |
858 | An expression for the alignment of a structure field @var{field} if the | |
a3a15b4d | 859 | alignment computed in the usual way is @var{computed}. GCC uses |
feca2ed3 JW |
860 | this value instead of the value in @code{BIGGEST_ALIGNMENT} or |
861 | @code{BIGGEST_FIELD_ALIGNMENT}, if defined, for structure fields only. | |
862 | ||
863 | @findex MAX_OFILE_ALIGNMENT | |
864 | @item MAX_OFILE_ALIGNMENT | |
865 | Biggest alignment supported by the object file format of this machine. | |
866 | Use this macro to limit the alignment which can be specified using the | |
867 | @code{__attribute__ ((aligned (@var{n})))} construct. If not defined, | |
868 | the default value is @code{BIGGEST_ALIGNMENT}. | |
869 | ||
870 | @findex DATA_ALIGNMENT | |
871 | @item DATA_ALIGNMENT (@var{type}, @var{basic-align}) | |
8a198bd2 JW |
872 | If defined, a C expression to compute the alignment for a variables in |
873 | the static store. @var{type} is the data type, and @var{basic-align} is | |
874 | the alignment that the object would ordinarily have. The value of this | |
feca2ed3 JW |
875 | macro is used instead of that alignment to align the object. |
876 | ||
877 | If this macro is not defined, then @var{basic-align} is used. | |
878 | ||
879 | @findex strcpy | |
880 | One use of this macro is to increase alignment of medium-size data to | |
881 | make it all fit in fewer cache lines. Another is to cause character | |
882 | arrays to be word-aligned so that @code{strcpy} calls that copy | |
883 | constants to character arrays can be done inline. | |
884 | ||
885 | @findex CONSTANT_ALIGNMENT | |
886 | @item CONSTANT_ALIGNMENT (@var{constant}, @var{basic-align}) | |
887 | If defined, a C expression to compute the alignment given to a constant | |
888 | that is being placed in memory. @var{constant} is the constant and | |
889 | @var{basic-align} is the alignment that the object would ordinarily | |
890 | have. The value of this macro is used instead of that alignment to | |
891 | align the object. | |
892 | ||
893 | If this macro is not defined, then @var{basic-align} is used. | |
894 | ||
895 | The typical use of this macro is to increase alignment for string | |
896 | constants to be word aligned so that @code{strcpy} calls that copy | |
897 | constants can be done inline. | |
898 | ||
d16790f2 JW |
899 | @findex LOCAL_ALIGNMENT |
900 | @item LOCAL_ALIGNMENT (@var{type}, @var{basic-align}) | |
901 | If defined, a C expression to compute the alignment for a variables in | |
902 | the local store. @var{type} is the data type, and @var{basic-align} is | |
903 | the alignment that the object would ordinarily have. The value of this | |
904 | macro is used instead of that alignment to align the object. | |
905 | ||
906 | If this macro is not defined, then @var{basic-align} is used. | |
907 | ||
908 | One use of this macro is to increase alignment of medium-size data to | |
909 | make it all fit in fewer cache lines. | |
910 | ||
feca2ed3 JW |
911 | @findex EMPTY_FIELD_BOUNDARY |
912 | @item EMPTY_FIELD_BOUNDARY | |
913 | Alignment in bits to be given to a structure bit field that follows an | |
914 | empty field such as @code{int : 0;}. | |
915 | ||
916 | Note that @code{PCC_BITFIELD_TYPE_MATTERS} also affects the alignment | |
917 | that results from an empty field. | |
918 | ||
919 | @findex STRUCTURE_SIZE_BOUNDARY | |
920 | @item STRUCTURE_SIZE_BOUNDARY | |
921 | Number of bits which any structure or union's size must be a multiple of. | |
922 | Each structure or union's size is rounded up to a multiple of this. | |
923 | ||
924 | If you do not define this macro, the default is the same as | |
925 | @code{BITS_PER_UNIT}. | |
926 | ||
927 | @findex STRICT_ALIGNMENT | |
928 | @item STRICT_ALIGNMENT | |
929 | Define this macro to be the value 1 if instructions will fail to work | |
930 | if given data not on the nominal alignment. If instructions will merely | |
931 | go slower in that case, define this macro as 0. | |
932 | ||
933 | @findex PCC_BITFIELD_TYPE_MATTERS | |
934 | @item PCC_BITFIELD_TYPE_MATTERS | |
935 | Define this if you wish to imitate the way many other C compilers handle | |
936 | alignment of bitfields and the structures that contain them. | |
937 | ||
938 | The behavior is that the type written for a bitfield (@code{int}, | |
939 | @code{short}, or other integer type) imposes an alignment for the | |
940 | entire structure, as if the structure really did contain an ordinary | |
941 | field of that type. In addition, the bitfield is placed within the | |
942 | structure so that it would fit within such a field, not crossing a | |
943 | boundary for it. | |
944 | ||
945 | Thus, on most machines, a bitfield whose type is written as @code{int} | |
946 | would not cross a four-byte boundary, and would force four-byte | |
947 | alignment for the whole structure. (The alignment used may not be four | |
948 | bytes; it is controlled by the other alignment parameters.) | |
949 | ||
950 | If the macro is defined, its definition should be a C expression; | |
951 | a nonzero value for the expression enables this behavior. | |
952 | ||
953 | Note that if this macro is not defined, or its value is zero, some | |
954 | bitfields may cross more than one alignment boundary. The compiler can | |
955 | support such references if there are @samp{insv}, @samp{extv}, and | |
956 | @samp{extzv} insns that can directly reference memory. | |
957 | ||
958 | The other known way of making bitfields work is to define | |
959 | @code{STRUCTURE_SIZE_BOUNDARY} as large as @code{BIGGEST_ALIGNMENT}. | |
960 | Then every structure can be accessed with fullwords. | |
961 | ||
962 | Unless the machine has bitfield instructions or you define | |
963 | @code{STRUCTURE_SIZE_BOUNDARY} that way, you must define | |
964 | @code{PCC_BITFIELD_TYPE_MATTERS} to have a nonzero value. | |
965 | ||
a3a15b4d | 966 | If your aim is to make GCC use the same conventions for laying out |
feca2ed3 JW |
967 | bitfields as are used by another compiler, here is how to investigate |
968 | what the other compiler does. Compile and run this program: | |
969 | ||
970 | @example | |
971 | struct foo1 | |
972 | @{ | |
973 | char x; | |
974 | char :0; | |
975 | char y; | |
976 | @}; | |
977 | ||
978 | struct foo2 | |
979 | @{ | |
980 | char x; | |
981 | int :0; | |
982 | char y; | |
983 | @}; | |
984 | ||
985 | main () | |
986 | @{ | |
987 | printf ("Size of foo1 is %d\n", | |
988 | sizeof (struct foo1)); | |
989 | printf ("Size of foo2 is %d\n", | |
990 | sizeof (struct foo2)); | |
991 | exit (0); | |
992 | @} | |
993 | @end example | |
994 | ||
995 | If this prints 2 and 5, then the compiler's behavior is what you would | |
996 | get from @code{PCC_BITFIELD_TYPE_MATTERS}. | |
997 | ||
998 | @findex BITFIELD_NBYTES_LIMITED | |
999 | @item BITFIELD_NBYTES_LIMITED | |
1000 | Like PCC_BITFIELD_TYPE_MATTERS except that its effect is limited to | |
1001 | aligning a bitfield within the structure. | |
1002 | ||
9f6dc500 HPN |
1003 | @findex STRUCT_FORCE_BLK |
1004 | @item STRUCT_FORCE_BLK (@var{field}) | |
1005 | Return 1 if a structure containing @var{field} should be accessed using | |
1006 | @code{BLKMODE}. | |
1007 | ||
1008 | Normally, this is not needed. See the file @file{c4x.h} for an example | |
1009 | of how to use this macro to prevent a structure having a floating point | |
1010 | field from being accessed in an integer mode. | |
1011 | ||
feca2ed3 | 1012 | @findex ROUND_TYPE_SIZE |
0003feb2 VM |
1013 | @item ROUND_TYPE_SIZE (@var{type}, @var{computed}, @var{specified}) |
1014 | Define this macro as an expression for the overall size of a type | |
1015 | (given by @var{type} as a tree node) when the size computed in the | |
1016 | usual way is @var{computed} and the alignment is @var{specified}. | |
feca2ed3 | 1017 | |
0003feb2 | 1018 | The default is to round @var{computed} up to a multiple of @var{specified}. |
feca2ed3 | 1019 | |
fed3cef0 RK |
1020 | @findex ROUND_TYPE_SIZE_UNIT |
1021 | @item ROUND_TYPE_SIZE_UNIT (@var{type}, @var{computed}, @var{specified}) | |
1022 | Similar to @code{ROUND_TYPE_SIZE}, but sizes and alignments are | |
1023 | specified in units (bytes). If you define @code{ROUND_TYPE_SIZE}, | |
1024 | you must also define this macro and they must be defined consistently | |
1025 | with each other. | |
1026 | ||
feca2ed3 | 1027 | @findex ROUND_TYPE_ALIGN |
0003feb2 VM |
1028 | @item ROUND_TYPE_ALIGN (@var{type}, @var{computed}, @var{specified}) |
1029 | Define this macro as an expression for the alignment of a type (given | |
1030 | by @var{type} as a tree node) if the alignment computed in the usual | |
1031 | way is @var{computed} and the alignment explicitly specified was | |
feca2ed3 JW |
1032 | @var{specified}. |
1033 | ||
1034 | The default is to use @var{specified} if it is larger; otherwise, use | |
1035 | the smaller of @var{computed} and @code{BIGGEST_ALIGNMENT} | |
1036 | ||
1037 | @findex MAX_FIXED_MODE_SIZE | |
1038 | @item MAX_FIXED_MODE_SIZE | |
1039 | An integer expression for the size in bits of the largest integer | |
1040 | machine mode that should actually be used. All integer machine modes of | |
1041 | this size or smaller can be used for structures and unions with the | |
1042 | appropriate sizes. If this macro is undefined, @code{GET_MODE_BITSIZE | |
1043 | (DImode)} is assumed. | |
1044 | ||
73c8090f DE |
1045 | @findex STACK_SAVEAREA_MODE |
1046 | @item STACK_SAVEAREA_MODE (@var{save_level}) | |
1047 | If defined, an expression of type @code{enum machine_mode} that | |
39403d82 DE |
1048 | specifies the mode of the save area operand of a |
1049 | @code{save_stack_@var{level}} named pattern (@pxref{Standard Names}). | |
1050 | @var{save_level} is one of @code{SAVE_BLOCK}, @code{SAVE_FUNCTION}, or | |
1051 | @code{SAVE_NONLOCAL} and selects which of the three named patterns is | |
1052 | having its mode specified. | |
73c8090f DE |
1053 | |
1054 | You need not define this macro if it always returns @code{Pmode}. You | |
1055 | would most commonly define this macro if the | |
1056 | @code{save_stack_@var{level}} patterns need to support both a 32- and a | |
1057 | 64-bit mode. | |
1058 | ||
39403d82 DE |
1059 | @findex STACK_SIZE_MODE |
1060 | @item STACK_SIZE_MODE | |
1061 | If defined, an expression of type @code{enum machine_mode} that | |
1062 | specifies the mode of the size increment operand of an | |
1063 | @code{allocate_stack} named pattern (@pxref{Standard Names}). | |
1064 | ||
1065 | You need not define this macro if it always returns @code{word_mode}. | |
1066 | You would most commonly define this macro if the @code{allocate_stack} | |
1067 | pattern needs to support both a 32- and a 64-bit mode. | |
1068 | ||
feca2ed3 JW |
1069 | @findex CHECK_FLOAT_VALUE |
1070 | @item CHECK_FLOAT_VALUE (@var{mode}, @var{value}, @var{overflow}) | |
1071 | A C statement to validate the value @var{value} (of type | |
1072 | @code{double}) for mode @var{mode}. This means that you check whether | |
1073 | @var{value} fits within the possible range of values for mode | |
1074 | @var{mode} on this target machine. The mode @var{mode} is always | |
1075 | a mode of class @code{MODE_FLOAT}. @var{overflow} is nonzero if | |
1076 | the value is already known to be out of range. | |
1077 | ||
1078 | If @var{value} is not valid or if @var{overflow} is nonzero, you should | |
1079 | set @var{overflow} to 1 and then assign some valid value to @var{value}. | |
1080 | Allowing an invalid value to go through the compiler can produce | |
1081 | incorrect assembler code which may even cause Unix assemblers to crash. | |
1082 | ||
1083 | This macro need not be defined if there is no work for it to do. | |
1084 | ||
1085 | @findex TARGET_FLOAT_FORMAT | |
1086 | @item TARGET_FLOAT_FORMAT | |
1087 | A code distinguishing the floating point format of the target machine. | |
1088 | There are three defined values: | |
1089 | ||
1090 | @table @code | |
1091 | @findex IEEE_FLOAT_FORMAT | |
1092 | @item IEEE_FLOAT_FORMAT | |
1093 | This code indicates IEEE floating point. It is the default; there is no | |
1094 | need to define this macro when the format is IEEE. | |
1095 | ||
1096 | @findex VAX_FLOAT_FORMAT | |
1097 | @item VAX_FLOAT_FORMAT | |
1098 | This code indicates the peculiar format used on the Vax. | |
1099 | ||
1100 | @findex UNKNOWN_FLOAT_FORMAT | |
1101 | @item UNKNOWN_FLOAT_FORMAT | |
1102 | This code indicates any other format. | |
1103 | @end table | |
1104 | ||
1105 | The value of this macro is compared with @code{HOST_FLOAT_FORMAT} | |
1106 | (@pxref{Config}) to determine whether the target machine has the same | |
1107 | format as the host machine. If any other formats are actually in use on | |
1108 | supported machines, new codes should be defined for them. | |
1109 | ||
1110 | The ordering of the component words of floating point values stored in | |
1111 | memory is controlled by @code{FLOAT_WORDS_BIG_ENDIAN} for the target | |
1112 | machine and @code{HOST_FLOAT_WORDS_BIG_ENDIAN} for the host. | |
e9a25f70 JL |
1113 | |
1114 | @findex DEFAULT_VTABLE_THUNKS | |
1115 | @item DEFAULT_VTABLE_THUNKS | |
a3a15b4d | 1116 | GCC supports two ways of implementing C++ vtables: traditional or with |
e9a25f70 JL |
1117 | so-called ``thunks''. The flag @samp{-fvtable-thunk} chooses between them. |
1118 | Define this macro to be a C expression for the default value of that flag. | |
a3a15b4d | 1119 | If @code{DEFAULT_VTABLE_THUNKS} is 0, GCC uses the traditional |
e9a25f70 JL |
1120 | implementation by default. The ``thunk'' implementation is more efficient |
1121 | (especially if you have provided an implementation of | |
1122 | @code{ASM_OUTPUT_MI_THUNK}, see @ref{Function Entry}), but is not binary | |
1123 | compatible with code compiled using the traditional implementation. | |
89bcce1b | 1124 | If you are writing a new port, define @code{DEFAULT_VTABLE_THUNKS} to 1. |
e9a25f70 JL |
1125 | |
1126 | If you do not define this macro, the default for @samp{-fvtable-thunk} is 0. | |
feca2ed3 JW |
1127 | @end table |
1128 | ||
1129 | @node Type Layout | |
1130 | @section Layout of Source Language Data Types | |
1131 | ||
1132 | These macros define the sizes and other characteristics of the standard | |
1133 | basic data types used in programs being compiled. Unlike the macros in | |
1134 | the previous section, these apply to specific features of C and related | |
1135 | languages, rather than to fundamental aspects of storage layout. | |
1136 | ||
1137 | @table @code | |
1138 | @findex INT_TYPE_SIZE | |
1139 | @item INT_TYPE_SIZE | |
1140 | A C expression for the size in bits of the type @code{int} on the | |
1141 | target machine. If you don't define this, the default is one word. | |
1142 | ||
1143 | @findex MAX_INT_TYPE_SIZE | |
1144 | @item MAX_INT_TYPE_SIZE | |
1145 | Maximum number for the size in bits of the type @code{int} on the target | |
1146 | machine. If this is undefined, the default is @code{INT_TYPE_SIZE}. | |
1147 | Otherwise, it is the constant value that is the largest value that | |
1148 | @code{INT_TYPE_SIZE} can have at run-time. This is used in @code{cpp}. | |
1149 | ||
1150 | @findex SHORT_TYPE_SIZE | |
1151 | @item SHORT_TYPE_SIZE | |
1152 | A C expression for the size in bits of the type @code{short} on the | |
1153 | target machine. If you don't define this, the default is half a word. | |
1154 | (If this would be less than one storage unit, it is rounded up to one | |
1155 | unit.) | |
1156 | ||
1157 | @findex LONG_TYPE_SIZE | |
1158 | @item LONG_TYPE_SIZE | |
1159 | A C expression for the size in bits of the type @code{long} on the | |
1160 | target machine. If you don't define this, the default is one word. | |
1161 | ||
1162 | @findex MAX_LONG_TYPE_SIZE | |
1163 | @item MAX_LONG_TYPE_SIZE | |
1164 | Maximum number for the size in bits of the type @code{long} on the | |
1165 | target machine. If this is undefined, the default is | |
1166 | @code{LONG_TYPE_SIZE}. Otherwise, it is the constant value that is the | |
1167 | largest value that @code{LONG_TYPE_SIZE} can have at run-time. This is | |
1168 | used in @code{cpp}. | |
1169 | ||
1170 | @findex LONG_LONG_TYPE_SIZE | |
1171 | @item LONG_LONG_TYPE_SIZE | |
1172 | A C expression for the size in bits of the type @code{long long} on the | |
1173 | target machine. If you don't define this, the default is two | |
1174 | words. If you want to support GNU Ada on your machine, the value of | |
1175 | macro must be at least 64. | |
1176 | ||
1177 | @findex CHAR_TYPE_SIZE | |
1178 | @item CHAR_TYPE_SIZE | |
1179 | A C expression for the size in bits of the type @code{char} on the | |
c294bd99 HPN |
1180 | target machine. If you don't define this, the default is |
1181 | @code{BITS_PER_UNIT}. | |
feca2ed3 JW |
1182 | |
1183 | @findex MAX_CHAR_TYPE_SIZE | |
1184 | @item MAX_CHAR_TYPE_SIZE | |
1185 | Maximum number for the size in bits of the type @code{char} on the | |
1186 | target machine. If this is undefined, the default is | |
1187 | @code{CHAR_TYPE_SIZE}. Otherwise, it is the constant value that is the | |
1188 | largest value that @code{CHAR_TYPE_SIZE} can have at run-time. This is | |
1189 | used in @code{cpp}. | |
1190 | ||
1191 | @findex FLOAT_TYPE_SIZE | |
1192 | @item FLOAT_TYPE_SIZE | |
1193 | A C expression for the size in bits of the type @code{float} on the | |
1194 | target machine. If you don't define this, the default is one word. | |
1195 | ||
1196 | @findex DOUBLE_TYPE_SIZE | |
1197 | @item DOUBLE_TYPE_SIZE | |
1198 | A C expression for the size in bits of the type @code{double} on the | |
1199 | target machine. If you don't define this, the default is two | |
1200 | words. | |
1201 | ||
1202 | @findex LONG_DOUBLE_TYPE_SIZE | |
1203 | @item LONG_DOUBLE_TYPE_SIZE | |
1204 | A C expression for the size in bits of the type @code{long double} on | |
1205 | the target machine. If you don't define this, the default is two | |
1206 | words. | |
1207 | ||
e9a25f70 JL |
1208 | @findex WIDEST_HARDWARE_FP_SIZE |
1209 | @item WIDEST_HARDWARE_FP_SIZE | |
1210 | A C expression for the size in bits of the widest floating-point format | |
1211 | supported by the hardware. If you define this macro, you must specify a | |
1212 | value less than or equal to the value of @code{LONG_DOUBLE_TYPE_SIZE}. | |
1213 | If you do not define this macro, the value of @code{LONG_DOUBLE_TYPE_SIZE} | |
1214 | is the default. | |
1215 | ||
feca2ed3 JW |
1216 | @findex DEFAULT_SIGNED_CHAR |
1217 | @item DEFAULT_SIGNED_CHAR | |
1218 | An expression whose value is 1 or 0, according to whether the type | |
1219 | @code{char} should be signed or unsigned by default. The user can | |
1220 | always override this default with the options @samp{-fsigned-char} | |
1221 | and @samp{-funsigned-char}. | |
1222 | ||
1223 | @findex DEFAULT_SHORT_ENUMS | |
1224 | @item DEFAULT_SHORT_ENUMS | |
1225 | A C expression to determine whether to give an @code{enum} type | |
1226 | only as many bytes as it takes to represent the range of possible values | |
1227 | of that type. A nonzero value means to do that; a zero value means all | |
1228 | @code{enum} types should be allocated like @code{int}. | |
1229 | ||
1230 | If you don't define the macro, the default is 0. | |
1231 | ||
1232 | @findex SIZE_TYPE | |
1233 | @item SIZE_TYPE | |
1234 | A C expression for a string describing the name of the data type to use | |
1235 | for size values. The typedef name @code{size_t} is defined using the | |
1236 | contents of the string. | |
1237 | ||
1238 | The string can contain more than one keyword. If so, separate them with | |
1239 | spaces, and write first any length keyword, then @code{unsigned} if | |
1240 | appropriate, and finally @code{int}. The string must exactly match one | |
1241 | of the data type names defined in the function | |
1242 | @code{init_decl_processing} in the file @file{c-decl.c}. You may not | |
1243 | omit @code{int} or change the order---that would cause the compiler to | |
1244 | crash on startup. | |
1245 | ||
1246 | If you don't define this macro, the default is @code{"long unsigned | |
1247 | int"}. | |
1248 | ||
1249 | @findex PTRDIFF_TYPE | |
1250 | @item PTRDIFF_TYPE | |
1251 | A C expression for a string describing the name of the data type to use | |
1252 | for the result of subtracting two pointers. The typedef name | |
1253 | @code{ptrdiff_t} is defined using the contents of the string. See | |
1254 | @code{SIZE_TYPE} above for more information. | |
1255 | ||
1256 | If you don't define this macro, the default is @code{"long int"}. | |
1257 | ||
1258 | @findex WCHAR_TYPE | |
1259 | @item WCHAR_TYPE | |
1260 | A C expression for a string describing the name of the data type to use | |
1261 | for wide characters. The typedef name @code{wchar_t} is defined using | |
1262 | the contents of the string. See @code{SIZE_TYPE} above for more | |
1263 | information. | |
1264 | ||
1265 | If you don't define this macro, the default is @code{"int"}. | |
1266 | ||
1267 | @findex WCHAR_TYPE_SIZE | |
1268 | @item WCHAR_TYPE_SIZE | |
1269 | A C expression for the size in bits of the data type for wide | |
1270 | characters. This is used in @code{cpp}, which cannot make use of | |
1271 | @code{WCHAR_TYPE}. | |
1272 | ||
1273 | @findex MAX_WCHAR_TYPE_SIZE | |
1274 | @item MAX_WCHAR_TYPE_SIZE | |
1275 | Maximum number for the size in bits of the data type for wide | |
1276 | characters. If this is undefined, the default is | |
1277 | @code{WCHAR_TYPE_SIZE}. Otherwise, it is the constant value that is the | |
1278 | largest value that @code{WCHAR_TYPE_SIZE} can have at run-time. This is | |
1279 | used in @code{cpp}. | |
1280 | ||
1281 | @findex OBJC_INT_SELECTORS | |
1282 | @item OBJC_INT_SELECTORS | |
1283 | Define this macro if the type of Objective C selectors should be | |
1284 | @code{int}. | |
1285 | ||
1286 | If this macro is not defined, then selectors should have the type | |
1287 | @code{struct objc_selector *}. | |
1288 | ||
1289 | @findex OBJC_SELECTORS_WITHOUT_LABELS | |
1290 | @item OBJC_SELECTORS_WITHOUT_LABELS | |
1291 | Define this macro if the compiler can group all the selectors together | |
1292 | into a vector and use just one label at the beginning of the vector. | |
1293 | Otherwise, the compiler must give each selector its own assembler | |
1294 | label. | |
1295 | ||
1296 | On certain machines, it is important to have a separate label for each | |
1297 | selector because this enables the linker to eliminate duplicate selectors. | |
1298 | ||
1299 | @findex TARGET_BELL | |
1300 | @item TARGET_BELL | |
1301 | A C constant expression for the integer value for escape sequence | |
1302 | @samp{\a}. | |
1303 | ||
1304 | @findex TARGET_TAB | |
1305 | @findex TARGET_BS | |
1306 | @findex TARGET_NEWLINE | |
1307 | @item TARGET_BS | |
1308 | @itemx TARGET_TAB | |
1309 | @itemx TARGET_NEWLINE | |
1310 | C constant expressions for the integer values for escape sequences | |
1311 | @samp{\b}, @samp{\t} and @samp{\n}. | |
1312 | ||
1313 | @findex TARGET_VT | |
1314 | @findex TARGET_FF | |
1315 | @findex TARGET_CR | |
1316 | @item TARGET_VT | |
1317 | @itemx TARGET_FF | |
1318 | @itemx TARGET_CR | |
1319 | C constant expressions for the integer values for escape sequences | |
1320 | @samp{\v}, @samp{\f} and @samp{\r}. | |
1321 | @end table | |
1322 | ||
1323 | @node Registers | |
1324 | @section Register Usage | |
1325 | @cindex register usage | |
1326 | ||
1327 | This section explains how to describe what registers the target machine | |
1328 | has, and how (in general) they can be used. | |
1329 | ||
1330 | The description of which registers a specific instruction can use is | |
1331 | done with register classes; see @ref{Register Classes}. For information | |
1332 | on using registers to access a stack frame, see @ref{Frame Registers}. | |
1333 | For passing values in registers, see @ref{Register Arguments}. | |
1334 | For returning values in registers, see @ref{Scalar Return}. | |
1335 | ||
1336 | @menu | |
1337 | * Register Basics:: Number and kinds of registers. | |
1338 | * Allocation Order:: Order in which registers are allocated. | |
1339 | * Values in Registers:: What kinds of values each reg can hold. | |
1340 | * Leaf Functions:: Renumbering registers for leaf functions. | |
1341 | * Stack Registers:: Handling a register stack such as 80387. | |
feca2ed3 JW |
1342 | @end menu |
1343 | ||
1344 | @node Register Basics | |
1345 | @subsection Basic Characteristics of Registers | |
1346 | ||
1347 | @c prevent bad page break with this line | |
1348 | Registers have various characteristics. | |
1349 | ||
1350 | @table @code | |
1351 | @findex FIRST_PSEUDO_REGISTER | |
1352 | @item FIRST_PSEUDO_REGISTER | |
1353 | Number of hardware registers known to the compiler. They receive | |
1354 | numbers 0 through @code{FIRST_PSEUDO_REGISTER-1}; thus, the first | |
1355 | pseudo register's number really is assigned the number | |
1356 | @code{FIRST_PSEUDO_REGISTER}. | |
1357 | ||
1358 | @item FIXED_REGISTERS | |
1359 | @findex FIXED_REGISTERS | |
1360 | @cindex fixed register | |
1361 | An initializer that says which registers are used for fixed purposes | |
1362 | all throughout the compiled code and are therefore not available for | |
1363 | general allocation. These would include the stack pointer, the frame | |
1364 | pointer (except on machines where that can be used as a general | |
1365 | register when no frame pointer is needed), the program counter on | |
1366 | machines where that is considered one of the addressable registers, | |
1367 | and any other numbered register with a standard use. | |
1368 | ||
1369 | This information is expressed as a sequence of numbers, separated by | |
1370 | commas and surrounded by braces. The @var{n}th number is 1 if | |
1371 | register @var{n} is fixed, 0 otherwise. | |
1372 | ||
1373 | The table initialized from this macro, and the table initialized by | |
1374 | the following one, may be overridden at run time either automatically, | |
1375 | by the actions of the macro @code{CONDITIONAL_REGISTER_USAGE}, or by | |
1376 | the user with the command options @samp{-ffixed-@var{reg}}, | |
1377 | @samp{-fcall-used-@var{reg}} and @samp{-fcall-saved-@var{reg}}. | |
1378 | ||
1379 | @findex CALL_USED_REGISTERS | |
1380 | @item CALL_USED_REGISTERS | |
1381 | @cindex call-used register | |
1382 | @cindex call-clobbered register | |
1383 | @cindex call-saved register | |
1384 | Like @code{FIXED_REGISTERS} but has 1 for each register that is | |
1385 | clobbered (in general) by function calls as well as for fixed | |
1386 | registers. This macro therefore identifies the registers that are not | |
1387 | available for general allocation of values that must live across | |
1388 | function calls. | |
1389 | ||
1390 | If a register has 0 in @code{CALL_USED_REGISTERS}, the compiler | |
1391 | automatically saves it on function entry and restores it on function | |
1392 | exit, if the register is used within the function. | |
1393 | ||
1e326708 MH |
1394 | @findex HARD_REGNO_CALL_PART_CLOBBERED |
1395 | @item HARD_REGNO_CALL_PART_CLOBBERED (@var{regno}, @var{mode}) | |
1396 | @cindex call-used register | |
1397 | @cindex call-clobbered register | |
1398 | @cindex call-saved register | |
1399 | A C expression that is non-zero if it is not permissible to store a | |
1400 | value of mode @var{mode} in hard register number @var{regno} across a | |
1401 | call without some part of it being clobbered. For most machines this | |
1402 | macro need not be defined. It is only required for machines that do not | |
1403 | preserve the entire contents of a register across a call. | |
1404 | ||
feca2ed3 JW |
1405 | @findex CONDITIONAL_REGISTER_USAGE |
1406 | @findex fixed_regs | |
1407 | @findex call_used_regs | |
1408 | @item CONDITIONAL_REGISTER_USAGE | |
910bc42d R |
1409 | Zero or more C statements that may conditionally modify four variables |
1410 | @code{fixed_regs}, @code{call_used_regs}, @code{global_regs} | |
1411 | (these three are of type @code{char []}) and @code{reg_class_contents} | |
1412 | (of type @code{HARD_REG_SET}). | |
1413 | Before the macro is called @code{fixed_regs}, @code{call_used_regs} | |
30ef624b | 1414 | and @code{reg_class_contents} have been initialized from |
910bc42d R |
1415 | @code{FIXED_REGISTERS}, @code{CALL_USED_REGISTERS} and |
1416 | @code{REG_CLASS_CONTENTS}, respectively, | |
1417 | @code{global_regs} has been cleared, and any @samp{-ffixed-@var{reg}}, | |
1418 | @samp{-fcall-used-@var{reg}} and @samp{-fcall-saved-@var{reg}} command | |
1419 | options have been applied. | |
feca2ed3 JW |
1420 | |
1421 | This is necessary in case the fixed or call-clobbered registers depend | |
1422 | on target flags. | |
1423 | ||
1424 | You need not define this macro if it has no work to do. | |
1425 | ||
1426 | @cindex disabling certain registers | |
1427 | @cindex controlling register usage | |
1428 | If the usage of an entire class of registers depends on the target | |
1429 | flags, you may indicate this to GCC by using this macro to modify | |
1430 | @code{fixed_regs} and @code{call_used_regs} to 1 for each of the | |
1431 | registers in the classes which should not be used by GCC. Also define | |
1432 | the macro @code{REG_CLASS_FROM_LETTER} to return @code{NO_REGS} if it | |
1433 | is called with a letter for a class that shouldn't be used. | |
1434 | ||
1435 | (However, if this class is not included in @code{GENERAL_REGS} and all | |
1436 | of the insn patterns whose constraints permit this class are | |
1437 | controlled by target switches, then GCC will automatically avoid using | |
1438 | these registers when the target switches are opposed to them.) | |
1439 | ||
1440 | @findex NON_SAVING_SETJMP | |
1441 | @item NON_SAVING_SETJMP | |
1442 | If this macro is defined and has a nonzero value, it means that | |
1443 | @code{setjmp} and related functions fail to save the registers, or that | |
1444 | @code{longjmp} fails to restore them. To compensate, the compiler | |
1445 | avoids putting variables in registers in functions that use | |
1446 | @code{setjmp}. | |
1447 | ||
1448 | @findex INCOMING_REGNO | |
1449 | @item INCOMING_REGNO (@var{out}) | |
1450 | Define this macro if the target machine has register windows. This C | |
1451 | expression returns the register number as seen by the called function | |
1452 | corresponding to the register number @var{out} as seen by the calling | |
1453 | function. Return @var{out} if register number @var{out} is not an | |
1454 | outbound register. | |
1455 | ||
1456 | @findex OUTGOING_REGNO | |
1457 | @item OUTGOING_REGNO (@var{in}) | |
1458 | Define this macro if the target machine has register windows. This C | |
1459 | expression returns the register number as seen by the calling function | |
1460 | corresponding to the register number @var{in} as seen by the called | |
1461 | function. Return @var{in} if register number @var{in} is not an inbound | |
1462 | register. | |
1463 | ||
1464 | @ignore | |
1465 | @findex PC_REGNUM | |
1466 | @item PC_REGNUM | |
1467 | If the program counter has a register number, define this as that | |
1468 | register number. Otherwise, do not define it. | |
1469 | @end ignore | |
1470 | @end table | |
1471 | ||
1472 | @node Allocation Order | |
1473 | @subsection Order of Allocation of Registers | |
1474 | @cindex order of register allocation | |
1475 | @cindex register allocation order | |
1476 | ||
1477 | @c prevent bad page break with this line | |
1478 | Registers are allocated in order. | |
1479 | ||
1480 | @table @code | |
1481 | @findex REG_ALLOC_ORDER | |
1482 | @item REG_ALLOC_ORDER | |
1483 | If defined, an initializer for a vector of integers, containing the | |
a3a15b4d | 1484 | numbers of hard registers in the order in which GCC should prefer |
feca2ed3 JW |
1485 | to use them (from most preferred to least). |
1486 | ||
1487 | If this macro is not defined, registers are used lowest numbered first | |
1488 | (all else being equal). | |
1489 | ||
1490 | One use of this macro is on machines where the highest numbered | |
1491 | registers must always be saved and the save-multiple-registers | |
1492 | instruction supports only sequences of consecutive registers. On such | |
1493 | machines, define @code{REG_ALLOC_ORDER} to be an initializer that lists | |
956d6950 | 1494 | the highest numbered allocable register first. |
feca2ed3 JW |
1495 | |
1496 | @findex ORDER_REGS_FOR_LOCAL_ALLOC | |
1497 | @item ORDER_REGS_FOR_LOCAL_ALLOC | |
1498 | A C statement (sans semicolon) to choose the order in which to allocate | |
1499 | hard registers for pseudo-registers local to a basic block. | |
1500 | ||
1501 | Store the desired register order in the array @code{reg_alloc_order}. | |
1502 | Element 0 should be the register to allocate first; element 1, the next | |
1503 | register; and so on. | |
1504 | ||
1505 | The macro body should not assume anything about the contents of | |
1506 | @code{reg_alloc_order} before execution of the macro. | |
1507 | ||
1508 | On most machines, it is not necessary to define this macro. | |
1509 | @end table | |
1510 | ||
1511 | @node Values in Registers | |
1512 | @subsection How Values Fit in Registers | |
1513 | ||
1514 | This section discusses the macros that describe which kinds of values | |
1515 | (specifically, which machine modes) each register can hold, and how many | |
1516 | consecutive registers are needed for a given mode. | |
1517 | ||
1518 | @table @code | |
1519 | @findex HARD_REGNO_NREGS | |
1520 | @item HARD_REGNO_NREGS (@var{regno}, @var{mode}) | |
1521 | A C expression for the number of consecutive hard registers, starting | |
1522 | at register number @var{regno}, required to hold a value of mode | |
1523 | @var{mode}. | |
1524 | ||
1525 | On a machine where all registers are exactly one word, a suitable | |
1526 | definition of this macro is | |
1527 | ||
1528 | @smallexample | |
1529 | #define HARD_REGNO_NREGS(REGNO, MODE) \ | |
1530 | ((GET_MODE_SIZE (MODE) + UNITS_PER_WORD - 1) \ | |
32bd3974 | 1531 | / UNITS_PER_WORD) |
feca2ed3 JW |
1532 | @end smallexample |
1533 | ||
ce4d78eb RH |
1534 | @findex ALTER_HARD_SUBREG |
1535 | @item ALTER_HARD_SUBREG (@var{tgt_mode}, @var{word}, @var{src_mode}, @var{regno}) | |
1536 | A C expression that returns an adjusted hard register number for | |
1537 | ||
1538 | @smallexample | |
1539 | (subreg:@var{tgt_mode} (reg:@var{src_mode} @var{regno}) @var{word}) | |
1540 | @end smallexample | |
1541 | ||
1542 | This may be needed if the target machine has mixed sized big-endian | |
1543 | registers, like Sparc v9. | |
1544 | ||
feca2ed3 JW |
1545 | @findex HARD_REGNO_MODE_OK |
1546 | @item HARD_REGNO_MODE_OK (@var{regno}, @var{mode}) | |
1547 | A C expression that is nonzero if it is permissible to store a value | |
1548 | of mode @var{mode} in hard register number @var{regno} (or in several | |
1549 | registers starting with that one). For a machine where all registers | |
1550 | are equivalent, a suitable definition is | |
1551 | ||
1552 | @smallexample | |
1553 | #define HARD_REGNO_MODE_OK(REGNO, MODE) 1 | |
1554 | @end smallexample | |
1555 | ||
e9a25f70 JL |
1556 | You need not include code to check for the numbers of fixed registers, |
1557 | because the allocation mechanism considers them to be always occupied. | |
feca2ed3 JW |
1558 | |
1559 | @cindex register pairs | |
1560 | On some machines, double-precision values must be kept in even/odd | |
e9a25f70 JL |
1561 | register pairs. You can implement that by defining this macro to reject |
1562 | odd register numbers for such modes. | |
feca2ed3 JW |
1563 | |
1564 | The minimum requirement for a mode to be OK in a register is that the | |
1565 | @samp{mov@var{mode}} instruction pattern support moves between the | |
e9a25f70 JL |
1566 | register and other hard register in the same class and that moving a |
1567 | value into the register and back out not alter it. | |
feca2ed3 | 1568 | |
e9a25f70 JL |
1569 | Since the same instruction used to move @code{word_mode} will work for |
1570 | all narrower integer modes, it is not necessary on any machine for | |
feca2ed3 JW |
1571 | @code{HARD_REGNO_MODE_OK} to distinguish between these modes, provided |
1572 | you define patterns @samp{movhi}, etc., to take advantage of this. This | |
1573 | is useful because of the interaction between @code{HARD_REGNO_MODE_OK} | |
1574 | and @code{MODES_TIEABLE_P}; it is very desirable for all integer modes | |
1575 | to be tieable. | |
1576 | ||
1577 | Many machines have special registers for floating point arithmetic. | |
1578 | Often people assume that floating point machine modes are allowed only | |
1579 | in floating point registers. This is not true. Any registers that | |
1580 | can hold integers can safely @emph{hold} a floating point machine | |
1581 | mode, whether or not floating arithmetic can be done on it in those | |
1582 | registers. Integer move instructions can be used to move the values. | |
1583 | ||
1584 | On some machines, though, the converse is true: fixed-point machine | |
1585 | modes may not go in floating registers. This is true if the floating | |
1586 | registers normalize any value stored in them, because storing a | |
1587 | non-floating value there would garble it. In this case, | |
1588 | @code{HARD_REGNO_MODE_OK} should reject fixed-point machine modes in | |
1589 | floating registers. But if the floating registers do not automatically | |
1590 | normalize, if you can store any bit pattern in one and retrieve it | |
1591 | unchanged without a trap, then any machine mode may go in a floating | |
1592 | register, so you can define this macro to say so. | |
1593 | ||
1594 | The primary significance of special floating registers is rather that | |
1595 | they are the registers acceptable in floating point arithmetic | |
1596 | instructions. However, this is of no concern to | |
1597 | @code{HARD_REGNO_MODE_OK}. You handle it by writing the proper | |
1598 | constraints for those instructions. | |
1599 | ||
1600 | On some machines, the floating registers are especially slow to access, | |
1601 | so that it is better to store a value in a stack frame than in such a | |
1602 | register if floating point arithmetic is not being done. As long as the | |
1603 | floating registers are not in class @code{GENERAL_REGS}, they will not | |
1604 | be used unless some pattern's constraint asks for one. | |
1605 | ||
1606 | @findex MODES_TIEABLE_P | |
1607 | @item MODES_TIEABLE_P (@var{mode1}, @var{mode2}) | |
e9a25f70 | 1608 | A C expression that is nonzero if a value of mode |
956d6950 | 1609 | @var{mode1} is accessible in mode @var{mode2} without copying. |
feca2ed3 JW |
1610 | |
1611 | If @code{HARD_REGNO_MODE_OK (@var{r}, @var{mode1})} and | |
e9a25f70 JL |
1612 | @code{HARD_REGNO_MODE_OK (@var{r}, @var{mode2})} are always the same for |
1613 | any @var{r}, then @code{MODES_TIEABLE_P (@var{mode1}, @var{mode2})} | |
1614 | should be nonzero. If they differ for any @var{r}, you should define | |
1615 | this macro to return zero unless some other mechanism ensures the | |
956d6950 | 1616 | accessibility of the value in a narrower mode. |
e9a25f70 JL |
1617 | |
1618 | You should define this macro to return nonzero in as many cases as | |
a3a15b4d | 1619 | possible since doing so will allow GCC to perform better register |
e9a25f70 | 1620 | allocation. |
7506f491 DE |
1621 | |
1622 | @findex AVOID_CCMODE_COPIES | |
1623 | @item AVOID_CCMODE_COPIES | |
1624 | Define this macro if the compiler should avoid copies to/from @code{CCmode} | |
a89608cb | 1625 | registers. You should only define this macro if support for copying to/from |
7506f491 | 1626 | @code{CCmode} is incomplete. |
feca2ed3 JW |
1627 | @end table |
1628 | ||
1629 | @node Leaf Functions | |
1630 | @subsection Handling Leaf Functions | |
1631 | ||
1632 | @cindex leaf functions | |
1633 | @cindex functions, leaf | |
1634 | On some machines, a leaf function (i.e., one which makes no calls) can run | |
1635 | more efficiently if it does not make its own register window. Often this | |
1636 | means it is required to receive its arguments in the registers where they | |
1637 | are passed by the caller, instead of the registers where they would | |
1638 | normally arrive. | |
1639 | ||
1640 | The special treatment for leaf functions generally applies only when | |
1641 | other conditions are met; for example, often they may use only those | |
1642 | registers for its own variables and temporaries. We use the term ``leaf | |
1643 | function'' to mean a function that is suitable for this special | |
1644 | handling, so that functions with no calls are not necessarily ``leaf | |
1645 | functions''. | |
1646 | ||
a3a15b4d | 1647 | GCC assigns register numbers before it knows whether the function is |
feca2ed3 JW |
1648 | suitable for leaf function treatment. So it needs to renumber the |
1649 | registers in order to output a leaf function. The following macros | |
1650 | accomplish this. | |
1651 | ||
1652 | @table @code | |
1653 | @findex LEAF_REGISTERS | |
1654 | @item LEAF_REGISTERS | |
7d167afd | 1655 | Name of a char vector, indexed by hard register number, which |
feca2ed3 JW |
1656 | contains 1 for a register that is allowable in a candidate for leaf |
1657 | function treatment. | |
1658 | ||
1659 | If leaf function treatment involves renumbering the registers, then the | |
1660 | registers marked here should be the ones before renumbering---those that | |
a3a15b4d | 1661 | GCC would ordinarily allocate. The registers which will actually be |
feca2ed3 JW |
1662 | used in the assembler code, after renumbering, should not be marked with 1 |
1663 | in this vector. | |
1664 | ||
1665 | Define this macro only if the target machine offers a way to optimize | |
1666 | the treatment of leaf functions. | |
1667 | ||
1668 | @findex LEAF_REG_REMAP | |
1669 | @item LEAF_REG_REMAP (@var{regno}) | |
1670 | A C expression whose value is the register number to which @var{regno} | |
1671 | should be renumbered, when a function is treated as a leaf function. | |
1672 | ||
1673 | If @var{regno} is a register number which should not appear in a leaf | |
1674 | function before renumbering, then the expression should yield -1, which | |
1675 | will cause the compiler to abort. | |
1676 | ||
1677 | Define this macro only if the target machine offers a way to optimize the | |
1678 | treatment of leaf functions, and registers need to be renumbered to do | |
1679 | this. | |
1680 | @end table | |
1681 | ||
54ff41b7 JW |
1682 | @findex current_function_is_leaf |
1683 | @findex current_function_uses_only_leaf_regs | |
feca2ed3 | 1684 | Normally, @code{FUNCTION_PROLOGUE} and @code{FUNCTION_EPILOGUE} must |
54ff41b7 JW |
1685 | treat leaf functions specially. They can test the C variable |
1686 | @code{current_function_is_leaf} which is nonzero for leaf functions. | |
1687 | @code{current_function_is_leaf} is set prior to local register allocation | |
1688 | and is valid for the remaining compiler passes. They can also test the C | |
1689 | variable @code{current_function_uses_only_leaf_regs} which is nonzero for | |
1690 | leaf functions which only use leaf registers. | |
1691 | @code{current_function_uses_only_leaf_regs} is valid after reload and is | |
1692 | only useful if @code{LEAF_REGISTERS} is defined. | |
feca2ed3 JW |
1693 | @c changed this to fix overfull. ALSO: why the "it" at the beginning |
1694 | @c of the next paragraph?! --mew 2feb93 | |
1695 | ||
1696 | @node Stack Registers | |
1697 | @subsection Registers That Form a Stack | |
1698 | ||
1699 | There are special features to handle computers where some of the | |
1700 | ``registers'' form a stack, as in the 80387 coprocessor for the 80386. | |
1701 | Stack registers are normally written by pushing onto the stack, and are | |
1702 | numbered relative to the top of the stack. | |
1703 | ||
a3a15b4d | 1704 | Currently, GCC can only handle one group of stack-like registers, and |
feca2ed3 JW |
1705 | they must be consecutively numbered. |
1706 | ||
1707 | @table @code | |
1708 | @findex STACK_REGS | |
1709 | @item STACK_REGS | |
1710 | Define this if the machine has any stack-like registers. | |
1711 | ||
1712 | @findex FIRST_STACK_REG | |
1713 | @item FIRST_STACK_REG | |
1714 | The number of the first stack-like register. This one is the top | |
1715 | of the stack. | |
1716 | ||
1717 | @findex LAST_STACK_REG | |
1718 | @item LAST_STACK_REG | |
1719 | The number of the last stack-like register. This one is the bottom of | |
1720 | the stack. | |
1721 | @end table | |
1722 | ||
feca2ed3 JW |
1723 | @node Register Classes |
1724 | @section Register Classes | |
1725 | @cindex register class definitions | |
1726 | @cindex class definitions, register | |
1727 | ||
1728 | On many machines, the numbered registers are not all equivalent. | |
1729 | For example, certain registers may not be allowed for indexed addressing; | |
1730 | certain registers may not be allowed in some instructions. These machine | |
1731 | restrictions are described to the compiler using @dfn{register classes}. | |
1732 | ||
1733 | You define a number of register classes, giving each one a name and saying | |
1734 | which of the registers belong to it. Then you can specify register classes | |
1735 | that are allowed as operands to particular instruction patterns. | |
1736 | ||
1737 | @findex ALL_REGS | |
1738 | @findex NO_REGS | |
1739 | In general, each register will belong to several classes. In fact, one | |
1740 | class must be named @code{ALL_REGS} and contain all the registers. Another | |
1741 | class must be named @code{NO_REGS} and contain no registers. Often the | |
1742 | union of two classes will be another class; however, this is not required. | |
1743 | ||
1744 | @findex GENERAL_REGS | |
1745 | One of the classes must be named @code{GENERAL_REGS}. There is nothing | |
1746 | terribly special about the name, but the operand constraint letters | |
1747 | @samp{r} and @samp{g} specify this class. If @code{GENERAL_REGS} is | |
1748 | the same as @code{ALL_REGS}, just define it as a macro which expands | |
1749 | to @code{ALL_REGS}. | |
1750 | ||
1751 | Order the classes so that if class @var{x} is contained in class @var{y} | |
1752 | then @var{x} has a lower class number than @var{y}. | |
1753 | ||
1754 | The way classes other than @code{GENERAL_REGS} are specified in operand | |
1755 | constraints is through machine-dependent operand constraint letters. | |
1756 | You can define such letters to correspond to various classes, then use | |
1757 | them in operand constraints. | |
1758 | ||
1759 | You should define a class for the union of two classes whenever some | |
1760 | instruction allows both classes. For example, if an instruction allows | |
1761 | either a floating point (coprocessor) register or a general register for a | |
1762 | certain operand, you should define a class @code{FLOAT_OR_GENERAL_REGS} | |
1763 | which includes both of them. Otherwise you will get suboptimal code. | |
1764 | ||
1765 | You must also specify certain redundant information about the register | |
1766 | classes: for each class, which classes contain it and which ones are | |
1767 | contained in it; for each pair of classes, the largest class contained | |
1768 | in their union. | |
1769 | ||
1770 | When a value occupying several consecutive registers is expected in a | |
1771 | certain class, all the registers used must belong to that class. | |
1772 | Therefore, register classes cannot be used to enforce a requirement for | |
1773 | a register pair to start with an even-numbered register. The way to | |
1774 | specify this requirement is with @code{HARD_REGNO_MODE_OK}. | |
1775 | ||
1776 | Register classes used for input-operands of bitwise-and or shift | |
1777 | instructions have a special requirement: each such class must have, for | |
1778 | each fixed-point machine mode, a subclass whose registers can transfer that | |
1779 | mode to or from memory. For example, on some machines, the operations for | |
1780 | single-byte values (@code{QImode}) are limited to certain registers. When | |
1781 | this is so, each register class that is used in a bitwise-and or shift | |
1782 | instruction must have a subclass consisting of registers from which | |
1783 | single-byte values can be loaded or stored. This is so that | |
1784 | @code{PREFERRED_RELOAD_CLASS} can always have a possible value to return. | |
1785 | ||
1786 | @table @code | |
1787 | @findex enum reg_class | |
1788 | @item enum reg_class | |
1789 | An enumeral type that must be defined with all the register class names | |
1790 | as enumeral values. @code{NO_REGS} must be first. @code{ALL_REGS} | |
1791 | must be the last register class, followed by one more enumeral value, | |
1792 | @code{LIM_REG_CLASSES}, which is not a register class but rather | |
1793 | tells how many classes there are. | |
1794 | ||
1795 | Each register class has a number, which is the value of casting | |
1796 | the class name to type @code{int}. The number serves as an index | |
1797 | in many of the tables described below. | |
1798 | ||
1799 | @findex N_REG_CLASSES | |
1800 | @item N_REG_CLASSES | |
1801 | The number of distinct register classes, defined as follows: | |
1802 | ||
1803 | @example | |
1804 | #define N_REG_CLASSES (int) LIM_REG_CLASSES | |
1805 | @end example | |
1806 | ||
1807 | @findex REG_CLASS_NAMES | |
1808 | @item REG_CLASS_NAMES | |
1809 | An initializer containing the names of the register classes as C string | |
1810 | constants. These names are used in writing some of the debugging dumps. | |
1811 | ||
1812 | @findex REG_CLASS_CONTENTS | |
1813 | @item REG_CLASS_CONTENTS | |
1814 | An initializer containing the contents of the register classes, as integers | |
1815 | which are bit masks. The @var{n}th integer specifies the contents of class | |
1816 | @var{n}. The way the integer @var{mask} is interpreted is that | |
1817 | register @var{r} is in the class if @code{@var{mask} & (1 << @var{r})} is 1. | |
1818 | ||
1819 | When the machine has more than 32 registers, an integer does not suffice. | |
1820 | Then the integers are replaced by sub-initializers, braced groupings containing | |
1821 | several integers. Each sub-initializer must be suitable as an initializer | |
1822 | for the type @code{HARD_REG_SET} which is defined in @file{hard-reg-set.h}. | |
1823 | ||
1824 | @findex REGNO_REG_CLASS | |
1825 | @item REGNO_REG_CLASS (@var{regno}) | |
1826 | A C expression whose value is a register class containing hard register | |
1827 | @var{regno}. In general there is more than one such class; choose a class | |
1828 | which is @dfn{minimal}, meaning that no smaller class also contains the | |
1829 | register. | |
1830 | ||
1831 | @findex BASE_REG_CLASS | |
1832 | @item BASE_REG_CLASS | |
1833 | A macro whose definition is the name of the class to which a valid | |
1834 | base register must belong. A base register is one used in an address | |
1835 | which is the register value plus a displacement. | |
1836 | ||
1837 | @findex INDEX_REG_CLASS | |
1838 | @item INDEX_REG_CLASS | |
1839 | A macro whose definition is the name of the class to which a valid | |
1840 | index register must belong. An index register is one used in an | |
1841 | address where its value is either multiplied by a scale factor or | |
1842 | added to another register (as well as added to a displacement). | |
1843 | ||
1844 | @findex REG_CLASS_FROM_LETTER | |
1845 | @item REG_CLASS_FROM_LETTER (@var{char}) | |
1846 | A C expression which defines the machine-dependent operand constraint | |
1847 | letters for register classes. If @var{char} is such a letter, the | |
1848 | value should be the register class corresponding to it. Otherwise, | |
1849 | the value should be @code{NO_REGS}. The register letter @samp{r}, | |
1850 | corresponding to class @code{GENERAL_REGS}, will not be passed | |
1851 | to this macro; you do not need to handle it. | |
1852 | ||
1853 | @findex REGNO_OK_FOR_BASE_P | |
1854 | @item REGNO_OK_FOR_BASE_P (@var{num}) | |
1855 | A C expression which is nonzero if register number @var{num} is | |
1856 | suitable for use as a base register in operand addresses. It may be | |
1857 | either a suitable hard register or a pseudo register that has been | |
1858 | allocated such a hard register. | |
1859 | ||
861bb6c1 JL |
1860 | @findex REGNO_MODE_OK_FOR_BASE_P |
1861 | @item REGNO_MODE_OK_FOR_BASE_P (@var{num}, @var{mode}) | |
1862 | A C expression that is just like @code{REGNO_OK_FOR_BASE_P}, except that | |
1863 | that expression may examine the mode of the memory reference in | |
1864 | @var{mode}. You should define this macro if the mode of the memory | |
1865 | reference affects whether a register may be used as a base register. If | |
1866 | you define this macro, the compiler will use it instead of | |
1867 | @code{REGNO_OK_FOR_BASE_P}. | |
1868 | ||
feca2ed3 JW |
1869 | @findex REGNO_OK_FOR_INDEX_P |
1870 | @item REGNO_OK_FOR_INDEX_P (@var{num}) | |
1871 | A C expression which is nonzero if register number @var{num} is | |
1872 | suitable for use as an index register in operand addresses. It may be | |
1873 | either a suitable hard register or a pseudo register that has been | |
1874 | allocated such a hard register. | |
1875 | ||
1876 | The difference between an index register and a base register is that | |
1877 | the index register may be scaled. If an address involves the sum of | |
1878 | two registers, neither one of them scaled, then either one may be | |
1879 | labeled the ``base'' and the other the ``index''; but whichever | |
1880 | labeling is used must fit the machine's constraints of which registers | |
1881 | may serve in each capacity. The compiler will try both labelings, | |
1882 | looking for one that is valid, and will reload one or both registers | |
1883 | only if neither labeling works. | |
1884 | ||
1885 | @findex PREFERRED_RELOAD_CLASS | |
1886 | @item PREFERRED_RELOAD_CLASS (@var{x}, @var{class}) | |
1887 | A C expression that places additional restrictions on the register class | |
1888 | to use when it is necessary to copy value @var{x} into a register in class | |
1889 | @var{class}. The value is a register class; perhaps @var{class}, or perhaps | |
1890 | another, smaller class. On many machines, the following definition is | |
1891 | safe: | |
1892 | ||
1893 | @example | |
1894 | #define PREFERRED_RELOAD_CLASS(X,CLASS) CLASS | |
1895 | @end example | |
1896 | ||
1897 | Sometimes returning a more restrictive class makes better code. For | |
1898 | example, on the 68000, when @var{x} is an integer constant that is in range | |
1899 | for a @samp{moveq} instruction, the value of this macro is always | |
1900 | @code{DATA_REGS} as long as @var{class} includes the data registers. | |
1901 | Requiring a data register guarantees that a @samp{moveq} will be used. | |
1902 | ||
1903 | If @var{x} is a @code{const_double}, by returning @code{NO_REGS} | |
1904 | you can force @var{x} into a memory constant. This is useful on | |
1905 | certain machines where immediate floating values cannot be loaded into | |
1906 | certain kinds of registers. | |
1907 | ||
1908 | @findex PREFERRED_OUTPUT_RELOAD_CLASS | |
1909 | @item PREFERRED_OUTPUT_RELOAD_CLASS (@var{x}, @var{class}) | |
1910 | Like @code{PREFERRED_RELOAD_CLASS}, but for output reloads instead of | |
1911 | input reloads. If you don't define this macro, the default is to use | |
1912 | @var{class}, unchanged. | |
1913 | ||
1914 | @findex LIMIT_RELOAD_CLASS | |
1915 | @item LIMIT_RELOAD_CLASS (@var{mode}, @var{class}) | |
1916 | A C expression that places additional restrictions on the register class | |
1917 | to use when it is necessary to be able to hold a value of mode | |
1918 | @var{mode} in a reload register for which class @var{class} would | |
1919 | ordinarily be used. | |
1920 | ||
1921 | Unlike @code{PREFERRED_RELOAD_CLASS}, this macro should be used when | |
1922 | there are certain modes that simply can't go in certain reload classes. | |
1923 | ||
1924 | The value is a register class; perhaps @var{class}, or perhaps another, | |
1925 | smaller class. | |
1926 | ||
1927 | Don't define this macro unless the target machine has limitations which | |
1928 | require the macro to do something nontrivial. | |
1929 | ||
1930 | @findex SECONDARY_RELOAD_CLASS | |
1931 | @findex SECONDARY_INPUT_RELOAD_CLASS | |
1932 | @findex SECONDARY_OUTPUT_RELOAD_CLASS | |
1933 | @item SECONDARY_RELOAD_CLASS (@var{class}, @var{mode}, @var{x}) | |
1934 | @itemx SECONDARY_INPUT_RELOAD_CLASS (@var{class}, @var{mode}, @var{x}) | |
1935 | @itemx SECONDARY_OUTPUT_RELOAD_CLASS (@var{class}, @var{mode}, @var{x}) | |
1936 | Many machines have some registers that cannot be copied directly to or | |
1937 | from memory or even from other types of registers. An example is the | |
1938 | @samp{MQ} register, which on most machines, can only be copied to or | |
1939 | from general registers, but not memory. Some machines allow copying all | |
1940 | registers to and from memory, but require a scratch register for stores | |
1941 | to some memory locations (e.g., those with symbolic address on the RT, | |
1942 | and those with certain symbolic address on the Sparc when compiling | |
1943 | PIC). In some cases, both an intermediate and a scratch register are | |
1944 | required. | |
1945 | ||
1946 | You should define these macros to indicate to the reload phase that it may | |
1947 | need to allocate at least one register for a reload in addition to the | |
1948 | register to contain the data. Specifically, if copying @var{x} to a | |
1949 | register @var{class} in @var{mode} requires an intermediate register, | |
1950 | you should define @code{SECONDARY_INPUT_RELOAD_CLASS} to return the | |
1951 | largest register class all of whose registers can be used as | |
1952 | intermediate registers or scratch registers. | |
1953 | ||
1954 | If copying a register @var{class} in @var{mode} to @var{x} requires an | |
1955 | intermediate or scratch register, @code{SECONDARY_OUTPUT_RELOAD_CLASS} | |
1956 | should be defined to return the largest register class required. If the | |
1957 | requirements for input and output reloads are the same, the macro | |
1958 | @code{SECONDARY_RELOAD_CLASS} should be used instead of defining both | |
1959 | macros identically. | |
1960 | ||
1961 | The values returned by these macros are often @code{GENERAL_REGS}. | |
1962 | Return @code{NO_REGS} if no spare register is needed; i.e., if @var{x} | |
1963 | can be directly copied to or from a register of @var{class} in | |
1964 | @var{mode} without requiring a scratch register. Do not define this | |
1965 | macro if it would always return @code{NO_REGS}. | |
1966 | ||
1967 | If a scratch register is required (either with or without an | |
1968 | intermediate register), you should define patterns for | |
1969 | @samp{reload_in@var{m}} or @samp{reload_out@var{m}}, as required | |
1970 | (@pxref{Standard Names}. These patterns, which will normally be | |
1971 | implemented with a @code{define_expand}, should be similar to the | |
1972 | @samp{mov@var{m}} patterns, except that operand 2 is the scratch | |
1973 | register. | |
1974 | ||
1975 | Define constraints for the reload register and scratch register that | |
1976 | contain a single register class. If the original reload register (whose | |
1977 | class is @var{class}) can meet the constraint given in the pattern, the | |
1978 | value returned by these macros is used for the class of the scratch | |
1979 | register. Otherwise, two additional reload registers are required. | |
1980 | Their classes are obtained from the constraints in the insn pattern. | |
1981 | ||
1982 | @var{x} might be a pseudo-register or a @code{subreg} of a | |
1983 | pseudo-register, which could either be in a hard register or in memory. | |
1984 | Use @code{true_regnum} to find out; it will return -1 if the pseudo is | |
1985 | in memory and the hard register number if it is in a register. | |
1986 | ||
1987 | These macros should not be used in the case where a particular class of | |
1988 | registers can only be copied to memory and not to another class of | |
1989 | registers. In that case, secondary reload registers are not needed and | |
1990 | would not be helpful. Instead, a stack location must be used to perform | |
1991 | the copy and the @code{mov@var{m}} pattern should use memory as a | |
1992 | intermediate storage. This case often occurs between floating-point and | |
1993 | general registers. | |
1994 | ||
1995 | @findex SECONDARY_MEMORY_NEEDED | |
1996 | @item SECONDARY_MEMORY_NEEDED (@var{class1}, @var{class2}, @var{m}) | |
1997 | Certain machines have the property that some registers cannot be copied | |
1998 | to some other registers without using memory. Define this macro on | |
1999 | those machines to be a C expression that is non-zero if objects of mode | |
2000 | @var{m} in registers of @var{class1} can only be copied to registers of | |
2001 | class @var{class2} by storing a register of @var{class1} into memory | |
2002 | and loading that memory location into a register of @var{class2}. | |
2003 | ||
2004 | Do not define this macro if its value would always be zero. | |
2005 | ||
2006 | @findex SECONDARY_MEMORY_NEEDED_RTX | |
2007 | @item SECONDARY_MEMORY_NEEDED_RTX (@var{mode}) | |
2008 | Normally when @code{SECONDARY_MEMORY_NEEDED} is defined, the compiler | |
2009 | allocates a stack slot for a memory location needed for register copies. | |
2010 | If this macro is defined, the compiler instead uses the memory location | |
2011 | defined by this macro. | |
2012 | ||
2013 | Do not define this macro if you do not define | |
2014 | @code{SECONDARY_MEMORY_NEEDED}. | |
2015 | ||
2016 | @findex SECONDARY_MEMORY_NEEDED_MODE | |
2017 | @item SECONDARY_MEMORY_NEEDED_MODE (@var{mode}) | |
2018 | When the compiler needs a secondary memory location to copy between two | |
2019 | registers of mode @var{mode}, it normally allocates sufficient memory to | |
2020 | hold a quantity of @code{BITS_PER_WORD} bits and performs the store and | |
2021 | load operations in a mode that many bits wide and whose class is the | |
2022 | same as that of @var{mode}. | |
2023 | ||
2024 | This is right thing to do on most machines because it ensures that all | |
2025 | bits of the register are copied and prevents accesses to the registers | |
2026 | in a narrower mode, which some machines prohibit for floating-point | |
2027 | registers. | |
2028 | ||
2029 | However, this default behavior is not correct on some machines, such as | |
2030 | the DEC Alpha, that store short integers in floating-point registers | |
2031 | differently than in integer registers. On those machines, the default | |
2032 | widening will not work correctly and you must define this macro to | |
2033 | suppress that widening in some cases. See the file @file{alpha.h} for | |
2034 | details. | |
2035 | ||
2036 | Do not define this macro if you do not define | |
2037 | @code{SECONDARY_MEMORY_NEEDED} or if widening @var{mode} to a mode that | |
2038 | is @code{BITS_PER_WORD} bits wide is correct for your machine. | |
2039 | ||
2040 | @findex SMALL_REGISTER_CLASSES | |
2041 | @item SMALL_REGISTER_CLASSES | |
faa9eb19 BS |
2042 | On some machines, it is risky to let hard registers live across arbitrary |
2043 | insns. Typically, these machines have instructions that require values | |
2044 | to be in specific registers (like an accumulator), and reload will fail | |
2045 | if the required hard register is used for another purpose across such an | |
2046 | insn. | |
feca2ed3 | 2047 | |
861bb6c1 JL |
2048 | Define @code{SMALL_REGISTER_CLASSES} to be an expression with a non-zero |
2049 | value on these machines. When this macro has a non-zero value, the | |
faa9eb19 | 2050 | compiler will try to minimize the lifetime of hard registers. |
feca2ed3 | 2051 | |
861bb6c1 JL |
2052 | It is always safe to define this macro with a non-zero value, but if you |
2053 | unnecessarily define it, you will reduce the amount of optimizations | |
2054 | that can be performed in some cases. If you do not define this macro | |
2055 | with a non-zero value when it is required, the compiler will run out of | |
2056 | spill registers and print a fatal error message. For most machines, you | |
2057 | should not define this macro at all. | |
feca2ed3 JW |
2058 | |
2059 | @findex CLASS_LIKELY_SPILLED_P | |
2060 | @item CLASS_LIKELY_SPILLED_P (@var{class}) | |
2061 | A C expression whose value is nonzero if pseudos that have been assigned | |
2062 | to registers of class @var{class} would likely be spilled because | |
2063 | registers of @var{class} are needed for spill registers. | |
2064 | ||
2065 | The default value of this macro returns 1 if @var{class} has exactly one | |
2066 | register and zero otherwise. On most machines, this default should be | |
40687a9e | 2067 | used. Only define this macro to some other expression if pseudos |
feca2ed3 JW |
2068 | allocated by @file{local-alloc.c} end up in memory because their hard |
2069 | registers were needed for spill registers. If this macro returns nonzero | |
2070 | for those classes, those pseudos will only be allocated by | |
2071 | @file{global.c}, which knows how to reallocate the pseudo to another | |
2072 | register. If there would not be another register available for | |
2073 | reallocation, you should not change the definition of this macro since | |
2074 | the only effect of such a definition would be to slow down register | |
2075 | allocation. | |
2076 | ||
2077 | @findex CLASS_MAX_NREGS | |
2078 | @item CLASS_MAX_NREGS (@var{class}, @var{mode}) | |
2079 | A C expression for the maximum number of consecutive registers | |
2080 | of class @var{class} needed to hold a value of mode @var{mode}. | |
2081 | ||
2082 | This is closely related to the macro @code{HARD_REGNO_NREGS}. In fact, | |
2083 | the value of the macro @code{CLASS_MAX_NREGS (@var{class}, @var{mode})} | |
2084 | should be the maximum value of @code{HARD_REGNO_NREGS (@var{regno}, | |
2085 | @var{mode})} for all @var{regno} values in the class @var{class}. | |
2086 | ||
2087 | This macro helps control the handling of multiple-word values | |
2088 | in the reload pass. | |
2089 | ||
2090 | @item CLASS_CANNOT_CHANGE_SIZE | |
2091 | If defined, a C expression for a class that contains registers which the | |
2092 | compiler must always access in a mode that is the same size as the mode | |
2093 | in which it loaded the register. | |
2094 | ||
2095 | For the example, loading 32-bit integer or floating-point objects into | |
2096 | floating-point registers on the Alpha extends them to 64-bits. | |
2097 | Therefore loading a 64-bit object and then storing it as a 32-bit object | |
2098 | does not store the low-order 32-bits, as would be the case for a normal | |
2099 | register. Therefore, @file{alpha.h} defines this macro as | |
2100 | @code{FLOAT_REGS}. | |
2101 | @end table | |
2102 | ||
2103 | Three other special macros describe which operands fit which constraint | |
2104 | letters. | |
2105 | ||
2106 | @table @code | |
2107 | @findex CONST_OK_FOR_LETTER_P | |
2108 | @item CONST_OK_FOR_LETTER_P (@var{value}, @var{c}) | |
e119b68c MM |
2109 | A C expression that defines the machine-dependent operand constraint |
2110 | letters (@samp{I}, @samp{J}, @samp{K}, @dots{} @samp{P}) that specify | |
2111 | particular ranges of integer values. If @var{c} is one of those | |
2112 | letters, the expression should check that @var{value}, an integer, is in | |
2113 | the appropriate range and return 1 if so, 0 otherwise. If @var{c} is | |
2114 | not one of those letters, the value should be 0 regardless of | |
2115 | @var{value}. | |
feca2ed3 JW |
2116 | |
2117 | @findex CONST_DOUBLE_OK_FOR_LETTER_P | |
2118 | @item CONST_DOUBLE_OK_FOR_LETTER_P (@var{value}, @var{c}) | |
2119 | A C expression that defines the machine-dependent operand constraint | |
e119b68c MM |
2120 | letters that specify particular ranges of @code{const_double} values |
2121 | (@samp{G} or @samp{H}). | |
feca2ed3 JW |
2122 | |
2123 | If @var{c} is one of those letters, the expression should check that | |
2124 | @var{value}, an RTX of code @code{const_double}, is in the appropriate | |
2125 | range and return 1 if so, 0 otherwise. If @var{c} is not one of those | |
2126 | letters, the value should be 0 regardless of @var{value}. | |
2127 | ||
2128 | @code{const_double} is used for all floating-point constants and for | |
2129 | @code{DImode} fixed-point constants. A given letter can accept either | |
2130 | or both kinds of values. It can use @code{GET_MODE} to distinguish | |
2131 | between these kinds. | |
2132 | ||
2133 | @findex EXTRA_CONSTRAINT | |
2134 | @item EXTRA_CONSTRAINT (@var{value}, @var{c}) | |
2135 | A C expression that defines the optional machine-dependent constraint | |
04afd9d6 | 2136 | letters (@samp{Q}, @samp{R}, @samp{S}, @samp{T}, @samp{U}) that can |
e119b68c MM |
2137 | be used to segregate specific types of operands, usually memory |
2138 | references, for the target machine. Normally this macro will not be | |
2139 | defined. If it is required for a particular target machine, it should | |
2140 | return 1 if @var{value} corresponds to the operand type represented by | |
2141 | the constraint letter @var{c}. If @var{c} is not defined as an extra | |
2142 | constraint, the value returned should be 0 regardless of @var{value}. | |
feca2ed3 JW |
2143 | |
2144 | For example, on the ROMP, load instructions cannot have their output in r0 if | |
2145 | the memory reference contains a symbolic address. Constraint letter | |
2146 | @samp{Q} is defined as representing a memory address that does | |
2147 | @emph{not} contain a symbolic address. An alternative is specified with | |
2148 | a @samp{Q} constraint on the input and @samp{r} on the output. The next | |
2149 | alternative specifies @samp{m} on the input and a register class that | |
2150 | does not include r0 on the output. | |
2151 | @end table | |
2152 | ||
2153 | @node Stack and Calling | |
2154 | @section Stack Layout and Calling Conventions | |
2155 | @cindex calling conventions | |
2156 | ||
2157 | @c prevent bad page break with this line | |
2158 | This describes the stack layout and calling conventions. | |
2159 | ||
2160 | @menu | |
2161 | * Frame Layout:: | |
861bb6c1 | 2162 | * Stack Checking:: |
feca2ed3 JW |
2163 | * Frame Registers:: |
2164 | * Elimination:: | |
2165 | * Stack Arguments:: | |
2166 | * Register Arguments:: | |
2167 | * Scalar Return:: | |
2168 | * Aggregate Return:: | |
2169 | * Caller Saves:: | |
2170 | * Function Entry:: | |
2171 | * Profiling:: | |
b36f4ed3 | 2172 | * Inlining:: |
feca2ed3 JW |
2173 | @end menu |
2174 | ||
2175 | @node Frame Layout | |
2176 | @subsection Basic Stack Layout | |
2177 | @cindex stack frame layout | |
2178 | @cindex frame layout | |
2179 | ||
2180 | @c prevent bad page break with this line | |
2181 | Here is the basic stack layout. | |
2182 | ||
2183 | @table @code | |
2184 | @findex STACK_GROWS_DOWNWARD | |
2185 | @item STACK_GROWS_DOWNWARD | |
2186 | Define this macro if pushing a word onto the stack moves the stack | |
2187 | pointer to a smaller address. | |
2188 | ||
2189 | When we say, ``define this macro if @dots{},'' it means that the | |
2190 | compiler checks this macro only with @code{#ifdef} so the precise | |
2191 | definition used does not matter. | |
2192 | ||
2193 | @findex FRAME_GROWS_DOWNWARD | |
2194 | @item FRAME_GROWS_DOWNWARD | |
2195 | Define this macro if the addresses of local variable slots are at negative | |
2196 | offsets from the frame pointer. | |
2197 | ||
2198 | @findex ARGS_GROW_DOWNWARD | |
2199 | @item ARGS_GROW_DOWNWARD | |
2200 | Define this macro if successive arguments to a function occupy decreasing | |
2201 | addresses on the stack. | |
2202 | ||
2203 | @findex STARTING_FRAME_OFFSET | |
2204 | @item STARTING_FRAME_OFFSET | |
2205 | Offset from the frame pointer to the first local variable slot to be allocated. | |
2206 | ||
2207 | If @code{FRAME_GROWS_DOWNWARD}, find the next slot's offset by | |
2208 | subtracting the first slot's length from @code{STARTING_FRAME_OFFSET}. | |
2209 | Otherwise, it is found by adding the length of the first slot to the | |
2210 | value @code{STARTING_FRAME_OFFSET}. | |
2211 | @c i'm not sure if the above is still correct.. had to change it to get | |
2212 | @c rid of an overfull. --mew 2feb93 | |
2213 | ||
2214 | @findex STACK_POINTER_OFFSET | |
2215 | @item STACK_POINTER_OFFSET | |
2216 | Offset from the stack pointer register to the first location at which | |
2217 | outgoing arguments are placed. If not specified, the default value of | |
2218 | zero is used. This is the proper value for most machines. | |
2219 | ||
2220 | If @code{ARGS_GROW_DOWNWARD}, this is the offset to the location above | |
2221 | the first location at which outgoing arguments are placed. | |
2222 | ||
2223 | @findex FIRST_PARM_OFFSET | |
2224 | @item FIRST_PARM_OFFSET (@var{fundecl}) | |
2225 | Offset from the argument pointer register to the first argument's | |
2226 | address. On some machines it may depend on the data type of the | |
2227 | function. | |
2228 | ||
2229 | If @code{ARGS_GROW_DOWNWARD}, this is the offset to the location above | |
2230 | the first argument's address. | |
2231 | ||
2232 | @findex STACK_DYNAMIC_OFFSET | |
2233 | @item STACK_DYNAMIC_OFFSET (@var{fundecl}) | |
2234 | Offset from the stack pointer register to an item dynamically allocated | |
2235 | on the stack, e.g., by @code{alloca}. | |
2236 | ||
2237 | The default value for this macro is @code{STACK_POINTER_OFFSET} plus the | |
2238 | length of the outgoing arguments. The default is correct for most | |
2239 | machines. See @file{function.c} for details. | |
2240 | ||
2241 | @findex DYNAMIC_CHAIN_ADDRESS | |
2242 | @item DYNAMIC_CHAIN_ADDRESS (@var{frameaddr}) | |
2243 | A C expression whose value is RTL representing the address in a stack | |
2244 | frame where the pointer to the caller's frame is stored. Assume that | |
2245 | @var{frameaddr} is an RTL expression for the address of the stack frame | |
2246 | itself. | |
2247 | ||
2248 | If you don't define this macro, the default is to return the value | |
2249 | of @var{frameaddr}---that is, the stack frame address is also the | |
2250 | address of the stack word that points to the previous frame. | |
2251 | ||
2252 | @findex SETUP_FRAME_ADDRESSES | |
0bc02db4 | 2253 | @item SETUP_FRAME_ADDRESSES |
feca2ed3 JW |
2254 | If defined, a C expression that produces the machine-specific code to |
2255 | setup the stack so that arbitrary frames can be accessed. For example, | |
2256 | on the Sparc, we must flush all of the register windows to the stack | |
0bc02db4 MS |
2257 | before we can access arbitrary stack frames. You will seldom need to |
2258 | define this macro. | |
2259 | ||
2260 | @findex BUILTIN_SETJMP_FRAME_VALUE | |
2261 | @item BUILTIN_SETJMP_FRAME_VALUE | |
2262 | If defined, a C expression that contains an rtx that is used to store | |
2263 | the address of the current frame into the built in @code{setjmp} buffer. | |
2264 | The default value, @code{virtual_stack_vars_rtx}, is correct for most | |
2265 | machines. One reason you may need to define this macro is if | |
2266 | @code{hard_frame_pointer_rtx} is the appropriate value on your machine. | |
feca2ed3 JW |
2267 | |
2268 | @findex RETURN_ADDR_RTX | |
2269 | @item RETURN_ADDR_RTX (@var{count}, @var{frameaddr}) | |
2270 | A C expression whose value is RTL representing the value of the return | |
861bb6c1 JL |
2271 | address for the frame @var{count} steps up from the current frame, after |
2272 | the prologue. @var{frameaddr} is the frame pointer of the @var{count} | |
2273 | frame, or the frame pointer of the @var{count} @minus{} 1 frame if | |
feca2ed3 JW |
2274 | @code{RETURN_ADDR_IN_PREVIOUS_FRAME} is defined. |
2275 | ||
e9a25f70 JL |
2276 | The value of the expression must always be the correct address when |
2277 | @var{count} is zero, but may be @code{NULL_RTX} if there is not way to | |
2278 | determine the return address of other frames. | |
2279 | ||
feca2ed3 JW |
2280 | @findex RETURN_ADDR_IN_PREVIOUS_FRAME |
2281 | @item RETURN_ADDR_IN_PREVIOUS_FRAME | |
2282 | Define this if the return address of a particular stack frame is accessed | |
2283 | from the frame pointer of the previous stack frame. | |
861bb6c1 JL |
2284 | |
2285 | @findex INCOMING_RETURN_ADDR_RTX | |
2286 | @item INCOMING_RETURN_ADDR_RTX | |
2287 | A C expression whose value is RTL representing the location of the | |
2288 | incoming return address at the beginning of any function, before the | |
2289 | prologue. This RTL is either a @code{REG}, indicating that the return | |
2290 | value is saved in @samp{REG}, or a @code{MEM} representing a location in | |
2291 | the stack. | |
2292 | ||
2293 | You only need to define this macro if you want to support call frame | |
2294 | debugging information like that provided by DWARF 2. | |
2295 | ||
2c849145 JM |
2296 | If this RTL is a @code{REG}, you should also define |
2297 | DWARF_FRAME_RETURN_COLUMN to @code{DWARF_FRAME_REGNUM (REGNO)}. | |
2298 | ||
861bb6c1 JL |
2299 | @findex INCOMING_FRAME_SP_OFFSET |
2300 | @item INCOMING_FRAME_SP_OFFSET | |
2301 | A C expression whose value is an integer giving the offset, in bytes, | |
2302 | from the value of the stack pointer register to the top of the stack | |
2303 | frame at the beginning of any function, before the prologue. The top of | |
2304 | the frame is defined to be the value of the stack pointer in the | |
2305 | previous frame, just before the call instruction. | |
2306 | ||
71038426 RH |
2307 | You only need to define this macro if you want to support call frame |
2308 | debugging information like that provided by DWARF 2. | |
2309 | ||
2310 | @findex ARG_POINTER_CFA_OFFSET | |
2c849145 | 2311 | @item ARG_POINTER_CFA_OFFSET (@var{fundecl}) |
71038426 RH |
2312 | A C expression whose value is an integer giving the offset, in bytes, |
2313 | from the argument pointer to the canonical frame address (cfa). The | |
2314 | final value should coincide with that calculated by | |
2315 | @code{INCOMING_FRAME_SP_OFFSET}. Which is unfortunately not usable | |
2316 | during virtual register instantiation. | |
2317 | ||
2c849145 JM |
2318 | The default value for this macro is @code{FIRST_PARM_OFFSET (fundecl)}, |
2319 | which is correct for most machines; in general, the arguments are found | |
208e52d9 JM |
2320 | immediately before the stack frame. Note that this is not the case on |
2321 | some targets that save registers into the caller's frame, such as SPARC | |
2322 | and rs6000, and so such targets need to define this macro. | |
2c849145 | 2323 | |
208e52d9 | 2324 | You only need to define this macro if the default is incorrect, and you |
2c849145 JM |
2325 | want to support call frame debugging information like that provided by |
2326 | DWARF 2. | |
512b62fb JM |
2327 | |
2328 | @findex SMALL_STACK | |
2329 | @item SMALL_STACK | |
2330 | Define this macro if the stack size for the target is very small. This | |
2331 | has the effect of disabling gcc's builtin @samp{alloca}, though | |
2332 | @samp{__builtin_alloca} is not affected. | |
861bb6c1 JL |
2333 | @end table |
2334 | ||
2335 | @node Stack Checking | |
2336 | @subsection Specifying How Stack Checking is Done | |
2337 | ||
a3a15b4d | 2338 | GCC will check that stack references are within the boundaries of |
861bb6c1 JL |
2339 | the stack, if the @samp{-fstack-check} is specified, in one of three ways: |
2340 | ||
2341 | @enumerate | |
2342 | @item | |
a3a15b4d | 2343 | If the value of the @code{STACK_CHECK_BUILTIN} macro is nonzero, GCC |
861bb6c1 JL |
2344 | will assume that you have arranged for stack checking to be done at |
2345 | appropriate places in the configuration files, e.g., in | |
a3a15b4d | 2346 | @code{FUNCTION_PROLOGUE}. GCC will do not other special processing. |
861bb6c1 JL |
2347 | |
2348 | @item | |
2349 | If @code{STACK_CHECK_BUILTIN} is zero and you defined a named pattern | |
a3a15b4d | 2350 | called @code{check_stack} in your @file{md} file, GCC will call that |
861bb6c1 JL |
2351 | pattern with one argument which is the address to compare the stack |
2352 | value against. You must arrange for this pattern to report an error if | |
2353 | the stack pointer is out of range. | |
2354 | ||
2355 | @item | |
a3a15b4d | 2356 | If neither of the above are true, GCC will generate code to periodically |
861bb6c1 JL |
2357 | ``probe'' the stack pointer using the values of the macros defined below. |
2358 | @end enumerate | |
2359 | ||
a3a15b4d | 2360 | Normally, you will use the default values of these macros, so GCC |
861bb6c1 JL |
2361 | will use the third approach. |
2362 | ||
2363 | @table @code | |
2364 | @findex STACK_CHECK_BUILTIN | |
2365 | @item STACK_CHECK_BUILTIN | |
2366 | A nonzero value if stack checking is done by the configuration files in a | |
2367 | machine-dependent manner. You should define this macro if stack checking | |
2368 | is require by the ABI of your machine or if you would like to have to stack | |
a3a15b4d | 2369 | checking in some more efficient way than GCC's portable approach. |
861bb6c1 JL |
2370 | The default value of this macro is zero. |
2371 | ||
2372 | @findex STACK_CHECK_PROBE_INTERVAL | |
2373 | @item STACK_CHECK_PROBE_INTERVAL | |
a3a15b4d | 2374 | An integer representing the interval at which GCC must generate stack |
861bb6c1 JL |
2375 | probe instructions. You will normally define this macro to be no larger |
2376 | than the size of the ``guard pages'' at the end of a stack area. The | |
2377 | default value of 4096 is suitable for most systems. | |
2378 | ||
2379 | @findex STACK_CHECK_PROBE_LOAD | |
2380 | @item STACK_CHECK_PROBE_LOAD | |
a3a15b4d JL |
2381 | A integer which is nonzero if GCC should perform the stack probe |
2382 | as a load instruction and zero if GCC should use a store instruction. | |
861bb6c1 JL |
2383 | The default is zero, which is the most efficient choice on most systems. |
2384 | ||
2385 | @findex STACK_CHECK_PROTECT | |
2386 | @item STACK_CHECK_PROTECT | |
2387 | The number of bytes of stack needed to recover from a stack overflow, | |
2388 | for languages where such a recovery is supported. The default value of | |
2389 | 75 words should be adequate for most machines. | |
2390 | ||
2391 | @findex STACK_CHECK_MAX_FRAME_SIZE | |
2392 | @item STACK_CHECK_MAX_FRAME_SIZE | |
a3a15b4d | 2393 | The maximum size of a stack frame, in bytes. GCC will generate probe |
861bb6c1 JL |
2394 | instructions in non-leaf functions to ensure at least this many bytes of |
2395 | stack are available. If a stack frame is larger than this size, stack | |
a3a15b4d JL |
2396 | checking will not be reliable and GCC will issue a warning. The |
2397 | default is chosen so that GCC only generates one instruction on most | |
861bb6c1 JL |
2398 | systems. You should normally not change the default value of this macro. |
2399 | ||
2400 | @findex STACK_CHECK_FIXED_FRAME_SIZE | |
2401 | @item STACK_CHECK_FIXED_FRAME_SIZE | |
a3a15b4d | 2402 | GCC uses this value to generate the above warning message. It |
861bb6c1 JL |
2403 | represents the amount of fixed frame used by a function, not including |
2404 | space for any callee-saved registers, temporaries and user variables. | |
2405 | You need only specify an upper bound for this amount and will normally | |
2406 | use the default of four words. | |
2407 | ||
2408 | @findex STACK_CHECK_MAX_VAR_SIZE | |
2409 | @item STACK_CHECK_MAX_VAR_SIZE | |
a3a15b4d | 2410 | The maximum size, in bytes, of an object that GCC will place in the |
861bb6c1 JL |
2411 | fixed area of the stack frame when the user specifies |
2412 | @samp{-fstack-check}. | |
a3a15b4d | 2413 | GCC computed the default from the values of the above macros and you will |
861bb6c1 | 2414 | normally not need to override that default. |
feca2ed3 JW |
2415 | @end table |
2416 | ||
2417 | @need 2000 | |
2418 | @node Frame Registers | |
2419 | @subsection Registers That Address the Stack Frame | |
2420 | ||
2421 | @c prevent bad page break with this line | |
2422 | This discusses registers that address the stack frame. | |
2423 | ||
2424 | @table @code | |
2425 | @findex STACK_POINTER_REGNUM | |
2426 | @item STACK_POINTER_REGNUM | |
2427 | The register number of the stack pointer register, which must also be a | |
2428 | fixed register according to @code{FIXED_REGISTERS}. On most machines, | |
2429 | the hardware determines which register this is. | |
2430 | ||
2431 | @findex FRAME_POINTER_REGNUM | |
2432 | @item FRAME_POINTER_REGNUM | |
2433 | The register number of the frame pointer register, which is used to | |
2434 | access automatic variables in the stack frame. On some machines, the | |
2435 | hardware determines which register this is. On other machines, you can | |
2436 | choose any register you wish for this purpose. | |
2437 | ||
2438 | @findex HARD_FRAME_POINTER_REGNUM | |
2439 | @item HARD_FRAME_POINTER_REGNUM | |
2440 | On some machines the offset between the frame pointer and starting | |
2441 | offset of the automatic variables is not known until after register | |
2442 | allocation has been done (for example, because the saved registers are | |
2443 | between these two locations). On those machines, define | |
2444 | @code{FRAME_POINTER_REGNUM} the number of a special, fixed register to | |
2445 | be used internally until the offset is known, and define | |
556e0f21 | 2446 | @code{HARD_FRAME_POINTER_REGNUM} to be the actual hard register number |
feca2ed3 JW |
2447 | used for the frame pointer. |
2448 | ||
2449 | You should define this macro only in the very rare circumstances when it | |
2450 | is not possible to calculate the offset between the frame pointer and | |
2451 | the automatic variables until after register allocation has been | |
2452 | completed. When this macro is defined, you must also indicate in your | |
2453 | definition of @code{ELIMINABLE_REGS} how to eliminate | |
2454 | @code{FRAME_POINTER_REGNUM} into either @code{HARD_FRAME_POINTER_REGNUM} | |
2455 | or @code{STACK_POINTER_REGNUM}. | |
2456 | ||
2457 | Do not define this macro if it would be the same as | |
2458 | @code{FRAME_POINTER_REGNUM}. | |
2459 | ||
2460 | @findex ARG_POINTER_REGNUM | |
2461 | @item ARG_POINTER_REGNUM | |
2462 | The register number of the arg pointer register, which is used to access | |
2463 | the function's argument list. On some machines, this is the same as the | |
2464 | frame pointer register. On some machines, the hardware determines which | |
2465 | register this is. On other machines, you can choose any register you | |
2466 | wish for this purpose. If this is not the same register as the frame | |
2467 | pointer register, then you must mark it as a fixed register according to | |
2468 | @code{FIXED_REGISTERS}, or arrange to be able to eliminate it | |
2469 | (@pxref{Elimination}). | |
2470 | ||
2471 | @findex RETURN_ADDRESS_POINTER_REGNUM | |
2472 | @item RETURN_ADDRESS_POINTER_REGNUM | |
2473 | The register number of the return address pointer register, which is used to | |
2474 | access the current function's return address from the stack. On some | |
2475 | machines, the return address is not at a fixed offset from the frame | |
2476 | pointer or stack pointer or argument pointer. This register can be defined | |
2477 | to point to the return address on the stack, and then be converted by | |
2478 | @code{ELIMINABLE_REGS} into either the frame pointer or stack pointer. | |
2479 | ||
2480 | Do not define this macro unless there is no other way to get the return | |
2481 | address from the stack. | |
2482 | ||
2483 | @findex STATIC_CHAIN_REGNUM | |
2484 | @findex STATIC_CHAIN_INCOMING_REGNUM | |
2485 | @item STATIC_CHAIN_REGNUM | |
2486 | @itemx STATIC_CHAIN_INCOMING_REGNUM | |
2487 | Register numbers used for passing a function's static chain pointer. If | |
2488 | register windows are used, the register number as seen by the called | |
2489 | function is @code{STATIC_CHAIN_INCOMING_REGNUM}, while the register | |
2490 | number as seen by the calling function is @code{STATIC_CHAIN_REGNUM}. If | |
2491 | these registers are the same, @code{STATIC_CHAIN_INCOMING_REGNUM} need | |
2492 | not be defined.@refill | |
2493 | ||
2494 | The static chain register need not be a fixed register. | |
2495 | ||
2496 | If the static chain is passed in memory, these macros should not be | |
2497 | defined; instead, the next two macros should be defined. | |
2498 | ||
2499 | @findex STATIC_CHAIN | |
2500 | @findex STATIC_CHAIN_INCOMING | |
2501 | @item STATIC_CHAIN | |
2502 | @itemx STATIC_CHAIN_INCOMING | |
2503 | If the static chain is passed in memory, these macros provide rtx giving | |
2504 | @code{mem} expressions that denote where they are stored. | |
2505 | @code{STATIC_CHAIN} and @code{STATIC_CHAIN_INCOMING} give the locations | |
2506 | as seen by the calling and called functions, respectively. Often the former | |
2507 | will be at an offset from the stack pointer and the latter at an offset from | |
2508 | the frame pointer.@refill | |
2509 | ||
2510 | @findex stack_pointer_rtx | |
2511 | @findex frame_pointer_rtx | |
2512 | @findex arg_pointer_rtx | |
2513 | The variables @code{stack_pointer_rtx}, @code{frame_pointer_rtx}, and | |
2514 | @code{arg_pointer_rtx} will have been initialized prior to the use of these | |
2515 | macros and should be used to refer to those items. | |
2516 | ||
2517 | If the static chain is passed in a register, the two previous macros should | |
2518 | be defined instead. | |
2519 | @end table | |
2520 | ||
2521 | @node Elimination | |
2522 | @subsection Eliminating Frame Pointer and Arg Pointer | |
2523 | ||
2524 | @c prevent bad page break with this line | |
2525 | This is about eliminating the frame pointer and arg pointer. | |
2526 | ||
2527 | @table @code | |
2528 | @findex FRAME_POINTER_REQUIRED | |
2529 | @item FRAME_POINTER_REQUIRED | |
2530 | A C expression which is nonzero if a function must have and use a frame | |
2531 | pointer. This expression is evaluated in the reload pass. If its value is | |
2532 | nonzero the function will have a frame pointer. | |
2533 | ||
2534 | The expression can in principle examine the current function and decide | |
2535 | according to the facts, but on most machines the constant 0 or the | |
2536 | constant 1 suffices. Use 0 when the machine allows code to be generated | |
2537 | with no frame pointer, and doing so saves some time or space. Use 1 | |
2538 | when there is no possible advantage to avoiding a frame pointer. | |
2539 | ||
2540 | In certain cases, the compiler does not know how to produce valid code | |
2541 | without a frame pointer. The compiler recognizes those cases and | |
2542 | automatically gives the function a frame pointer regardless of what | |
2543 | @code{FRAME_POINTER_REQUIRED} says. You don't need to worry about | |
2544 | them.@refill | |
2545 | ||
2546 | In a function that does not require a frame pointer, the frame pointer | |
2547 | register can be allocated for ordinary usage, unless you mark it as a | |
2548 | fixed register. See @code{FIXED_REGISTERS} for more information. | |
2549 | ||
2550 | @findex INITIAL_FRAME_POINTER_OFFSET | |
2551 | @findex get_frame_size | |
2552 | @item INITIAL_FRAME_POINTER_OFFSET (@var{depth-var}) | |
2553 | A C statement to store in the variable @var{depth-var} the difference | |
2554 | between the frame pointer and the stack pointer values immediately after | |
2555 | the function prologue. The value would be computed from information | |
2556 | such as the result of @code{get_frame_size ()} and the tables of | |
2557 | registers @code{regs_ever_live} and @code{call_used_regs}. | |
2558 | ||
2559 | If @code{ELIMINABLE_REGS} is defined, this macro will be not be used and | |
2560 | need not be defined. Otherwise, it must be defined even if | |
2561 | @code{FRAME_POINTER_REQUIRED} is defined to always be true; in that | |
2562 | case, you may set @var{depth-var} to anything. | |
2563 | ||
2564 | @findex ELIMINABLE_REGS | |
2565 | @item ELIMINABLE_REGS | |
2566 | If defined, this macro specifies a table of register pairs used to | |
2567 | eliminate unneeded registers that point into the stack frame. If it is not | |
2568 | defined, the only elimination attempted by the compiler is to replace | |
2569 | references to the frame pointer with references to the stack pointer. | |
2570 | ||
2571 | The definition of this macro is a list of structure initializations, each | |
2572 | of which specifies an original and replacement register. | |
2573 | ||
2574 | On some machines, the position of the argument pointer is not known until | |
2575 | the compilation is completed. In such a case, a separate hard register | |
2576 | must be used for the argument pointer. This register can be eliminated by | |
2577 | replacing it with either the frame pointer or the argument pointer, | |
2578 | depending on whether or not the frame pointer has been eliminated. | |
2579 | ||
2580 | In this case, you might specify: | |
2581 | @example | |
2582 | #define ELIMINABLE_REGS \ | |
2583 | @{@{ARG_POINTER_REGNUM, STACK_POINTER_REGNUM@}, \ | |
2584 | @{ARG_POINTER_REGNUM, FRAME_POINTER_REGNUM@}, \ | |
2585 | @{FRAME_POINTER_REGNUM, STACK_POINTER_REGNUM@}@} | |
2586 | @end example | |
2587 | ||
2588 | Note that the elimination of the argument pointer with the stack pointer is | |
2589 | specified first since that is the preferred elimination. | |
2590 | ||
2591 | @findex CAN_ELIMINATE | |
2592 | @item CAN_ELIMINATE (@var{from-reg}, @var{to-reg}) | |
2593 | A C expression that returns non-zero if the compiler is allowed to try | |
2594 | to replace register number @var{from-reg} with register number | |
2595 | @var{to-reg}. This macro need only be defined if @code{ELIMINABLE_REGS} | |
2596 | is defined, and will usually be the constant 1, since most of the cases | |
2597 | preventing register elimination are things that the compiler already | |
2598 | knows about. | |
2599 | ||
2600 | @findex INITIAL_ELIMINATION_OFFSET | |
2601 | @item INITIAL_ELIMINATION_OFFSET (@var{from-reg}, @var{to-reg}, @var{offset-var}) | |
2602 | This macro is similar to @code{INITIAL_FRAME_POINTER_OFFSET}. It | |
2603 | specifies the initial difference between the specified pair of | |
2604 | registers. This macro must be defined if @code{ELIMINABLE_REGS} is | |
2605 | defined. | |
2606 | ||
2607 | @findex LONGJMP_RESTORE_FROM_STACK | |
2608 | @item LONGJMP_RESTORE_FROM_STACK | |
2609 | Define this macro if the @code{longjmp} function restores registers from | |
2610 | the stack frames, rather than from those saved specifically by | |
2611 | @code{setjmp}. Certain quantities must not be kept in registers across | |
2612 | a call to @code{setjmp} on such machines. | |
2613 | @end table | |
2614 | ||
2615 | @node Stack Arguments | |
2616 | @subsection Passing Function Arguments on the Stack | |
2617 | @cindex arguments on stack | |
2618 | @cindex stack arguments | |
2619 | ||
2620 | The macros in this section control how arguments are passed | |
2621 | on the stack. See the following section for other macros that | |
2622 | control passing certain arguments in registers. | |
2623 | ||
2624 | @table @code | |
2625 | @findex PROMOTE_PROTOTYPES | |
2626 | @item PROMOTE_PROTOTYPES | |
7d473569 JJ |
2627 | A C expression whose value is nonzero if an argument declared in |
2628 | a prototype as an integral type smaller than @code{int} should | |
2629 | actually be passed as an @code{int}. In addition to avoiding | |
2630 | errors in certain cases of mismatch, it also makes for better | |
2631 | code on certain machines. If the macro is not defined in target | |
2632 | header files, it defaults to 0. | |
feca2ed3 | 2633 | |
f73ad30e JH |
2634 | @findex PUSH_ARGS |
2635 | @item PUSH_ARGS | |
2636 | A C expression. If nonzero, push insns will be used to pass | |
2637 | outgoing arguments. | |
2638 | If the target machine does not have a push instruction, set it to zero. | |
2639 | That directs GCC to use an alternate strategy: to | |
2640 | allocate the entire argument block and then store the arguments into | |
2641 | it. When PUSH_ARGS is nonzero, PUSH_ROUNDING must be defined too. | |
2642 | On some machines, the definition | |
2643 | ||
2644 | @findex PUSH_ROUNDING | |
2645 | @item PUSH_ROUNDING (@var{npushed}) | |
2646 | A C expression that is the number of bytes actually pushed onto the | |
2647 | stack when an instruction attempts to push @var{npushed} bytes. | |
feca2ed3 JW |
2648 | @findex PUSH_ROUNDING |
2649 | @item PUSH_ROUNDING (@var{npushed}) | |
2650 | A C expression that is the number of bytes actually pushed onto the | |
2651 | stack when an instruction attempts to push @var{npushed} bytes. | |
feca2ed3 JW |
2652 | |
2653 | On some machines, the definition | |
2654 | ||
2655 | @example | |
2656 | #define PUSH_ROUNDING(BYTES) (BYTES) | |
2657 | @end example | |
2658 | ||
2659 | @noindent | |
2660 | will suffice. But on other machines, instructions that appear | |
2661 | to push one byte actually push two bytes in an attempt to maintain | |
2662 | alignment. Then the definition should be | |
2663 | ||
2664 | @example | |
2665 | #define PUSH_ROUNDING(BYTES) (((BYTES) + 1) & ~1) | |
2666 | @end example | |
2667 | ||
2668 | @findex ACCUMULATE_OUTGOING_ARGS | |
2669 | @findex current_function_outgoing_args_size | |
2670 | @item ACCUMULATE_OUTGOING_ARGS | |
f73ad30e | 2671 | A C expression. If nonzero, the maximum amount of space required for outgoing arguments |
feca2ed3 JW |
2672 | will be computed and placed into the variable |
2673 | @code{current_function_outgoing_args_size}. No space will be pushed | |
2674 | onto the stack for each call; instead, the function prologue should | |
2675 | increase the stack frame size by this amount. | |
2676 | ||
f73ad30e | 2677 | Setting both @code{PUSH_ARGS} and @code{ACCUMULATE_OUTGOING_ARGS} |
feca2ed3 JW |
2678 | is not proper. |
2679 | ||
2680 | @findex REG_PARM_STACK_SPACE | |
2681 | @item REG_PARM_STACK_SPACE (@var{fndecl}) | |
2682 | Define this macro if functions should assume that stack space has been | |
2683 | allocated for arguments even when their values are passed in | |
2684 | registers. | |
2685 | ||
2686 | The value of this macro is the size, in bytes, of the area reserved for | |
ab87f8c8 | 2687 | arguments passed in registers for the function represented by @var{fndecl}, |
a3a15b4d | 2688 | which can be zero if GCC is calling a library function. |
feca2ed3 JW |
2689 | |
2690 | This space can be allocated by the caller, or be a part of the | |
2691 | machine-dependent stack frame: @code{OUTGOING_REG_PARM_STACK_SPACE} says | |
2692 | which. | |
2693 | @c above is overfull. not sure what to do. --mew 5feb93 did | |
2694 | @c something, not sure if it looks good. --mew 10feb93 | |
2695 | ||
2696 | @findex MAYBE_REG_PARM_STACK_SPACE | |
2697 | @findex FINAL_REG_PARM_STACK_SPACE | |
2698 | @item MAYBE_REG_PARM_STACK_SPACE | |
2699 | @itemx FINAL_REG_PARM_STACK_SPACE (@var{const_size}, @var{var_size}) | |
2700 | Define these macros in addition to the one above if functions might | |
2701 | allocate stack space for arguments even when their values are passed | |
2702 | in registers. These should be used when the stack space allocated | |
2703 | for arguments in registers is not a simple constant independent of the | |
2704 | function declaration. | |
2705 | ||
2706 | The value of the first macro is the size, in bytes, of the area that | |
2707 | we should initially assume would be reserved for arguments passed in registers. | |
2708 | ||
2709 | The value of the second macro is the actual size, in bytes, of the area | |
2710 | that will be reserved for arguments passed in registers. This takes two | |
2711 | arguments: an integer representing the number of bytes of fixed sized | |
2712 | arguments on the stack, and a tree representing the number of bytes of | |
2713 | variable sized arguments on the stack. | |
2714 | ||
2715 | When these macros are defined, @code{REG_PARM_STACK_SPACE} will only be | |
2716 | called for libcall functions, the current function, or for a function | |
2717 | being called when it is known that such stack space must be allocated. | |
2718 | In each case this value can be easily computed. | |
2719 | ||
2720 | When deciding whether a called function needs such stack space, and how | |
a3a15b4d | 2721 | much space to reserve, GCC uses these two macros instead of |
feca2ed3 JW |
2722 | @code{REG_PARM_STACK_SPACE}. |
2723 | ||
2724 | @findex OUTGOING_REG_PARM_STACK_SPACE | |
2725 | @item OUTGOING_REG_PARM_STACK_SPACE | |
2726 | Define this if it is the responsibility of the caller to allocate the area | |
2727 | reserved for arguments passed in registers. | |
2728 | ||
2729 | If @code{ACCUMULATE_OUTGOING_ARGS} is defined, this macro controls | |
2730 | whether the space for these arguments counts in the value of | |
2731 | @code{current_function_outgoing_args_size}. | |
2732 | ||
2733 | @findex STACK_PARMS_IN_REG_PARM_AREA | |
2734 | @item STACK_PARMS_IN_REG_PARM_AREA | |
2735 | Define this macro if @code{REG_PARM_STACK_SPACE} is defined, but the | |
2736 | stack parameters don't skip the area specified by it. | |
2737 | @c i changed this, makes more sens and it should have taken care of the | |
2738 | @c overfull.. not as specific, tho. --mew 5feb93 | |
2739 | ||
2740 | Normally, when a parameter is not passed in registers, it is placed on the | |
2741 | stack beyond the @code{REG_PARM_STACK_SPACE} area. Defining this macro | |
2742 | suppresses this behavior and causes the parameter to be passed on the | |
2743 | stack in its natural location. | |
2744 | ||
2745 | @findex RETURN_POPS_ARGS | |
2746 | @item RETURN_POPS_ARGS (@var{fundecl}, @var{funtype}, @var{stack-size}) | |
2747 | A C expression that should indicate the number of bytes of its own | |
2748 | arguments that a function pops on returning, or 0 if the | |
2749 | function pops no arguments and the caller must therefore pop them all | |
2750 | after the function returns. | |
2751 | ||
2752 | @var{fundecl} is a C variable whose value is a tree node that describes | |
2753 | the function in question. Normally it is a node of type | |
2754 | @code{FUNCTION_DECL} that describes the declaration of the function. | |
2755 | From this you can obtain the DECL_MACHINE_ATTRIBUTES of the function. | |
2756 | ||
2757 | @var{funtype} is a C variable whose value is a tree node that | |
2758 | describes the function in question. Normally it is a node of type | |
2759 | @code{FUNCTION_TYPE} that describes the data type of the function. | |
2760 | From this it is possible to obtain the data types of the value and | |
2761 | arguments (if known). | |
2762 | ||
861bb6c1 | 2763 | When a call to a library function is being considered, @var{fundecl} |
feca2ed3 JW |
2764 | will contain an identifier node for the library function. Thus, if |
2765 | you need to distinguish among various library functions, you can do so | |
2766 | by their names. Note that ``library function'' in this context means | |
2767 | a function used to perform arithmetic, whose name is known specially | |
2768 | in the compiler and was not mentioned in the C code being compiled. | |
2769 | ||
2770 | @var{stack-size} is the number of bytes of arguments passed on the | |
2771 | stack. If a variable number of bytes is passed, it is zero, and | |
2772 | argument popping will always be the responsibility of the calling function. | |
2773 | ||
2774 | On the Vax, all functions always pop their arguments, so the definition | |
2775 | of this macro is @var{stack-size}. On the 68000, using the standard | |
2776 | calling convention, no functions pop their arguments, so the value of | |
2777 | the macro is always 0 in this case. But an alternative calling | |
2778 | convention is available in which functions that take a fixed number of | |
2779 | arguments pop them but other functions (such as @code{printf}) pop | |
2780 | nothing (the caller pops all). When this convention is in use, | |
2781 | @var{funtype} is examined to determine whether a function takes a fixed | |
2782 | number of arguments. | |
2783 | @end table | |
2784 | ||
2785 | @node Register Arguments | |
2786 | @subsection Passing Arguments in Registers | |
2787 | @cindex arguments in registers | |
2788 | @cindex registers arguments | |
2789 | ||
2790 | This section describes the macros which let you control how various | |
2791 | types of arguments are passed in registers or how they are arranged in | |
2792 | the stack. | |
2793 | ||
2794 | @table @code | |
2795 | @findex FUNCTION_ARG | |
2796 | @item FUNCTION_ARG (@var{cum}, @var{mode}, @var{type}, @var{named}) | |
2797 | A C expression that controls whether a function argument is passed | |
2798 | in a register, and which register. | |
2799 | ||
2800 | The arguments are @var{cum}, which summarizes all the previous | |
2801 | arguments; @var{mode}, the machine mode of the argument; @var{type}, | |
2802 | the data type of the argument as a tree node or 0 if that is not known | |
2803 | (which happens for C support library functions); and @var{named}, | |
2804 | which is 1 for an ordinary argument and 0 for nameless arguments that | |
2805 | correspond to @samp{@dots{}} in the called function's prototype. | |
2806 | ||
2807 | The value of the expression is usually either a @code{reg} RTX for the | |
2808 | hard register in which to pass the argument, or zero to pass the | |
2809 | argument on the stack. | |
2810 | ||
2811 | For machines like the Vax and 68000, where normally all arguments are | |
2812 | pushed, zero suffices as a definition. | |
2813 | ||
2814 | The value of the expression can also be a @code{parallel} RTX. This is | |
2815 | used when an argument is passed in multiple locations. The mode of the | |
2816 | of the @code{parallel} should be the mode of the entire argument. The | |
2817 | @code{parallel} holds any number of @code{expr_list} pairs; each one | |
f797c10b NC |
2818 | describes where part of the argument is passed. In each |
2819 | @code{expr_list} the first operand must be a @code{reg} RTX for the hard | |
2820 | register in which to pass this part of the argument, and the mode of the | |
2821 | register RTX indicates how large this part of the argument is. The | |
2822 | second operand of the @code{expr_list} is a @code{const_int} which gives | |
2823 | the offset in bytes into the entire argument of where this part starts. | |
2824 | As a special exception the first @code{expr_list} in the @code{parallel} | |
c980b85b NC |
2825 | RTX may have a first operand of zero. This indicates that the entire |
2826 | argument is also stored on the stack. | |
feca2ed3 JW |
2827 | |
2828 | @cindex @file{stdarg.h} and register arguments | |
2829 | The usual way to make the ANSI library @file{stdarg.h} work on a machine | |
2830 | where some arguments are usually passed in registers, is to cause | |
2831 | nameless arguments to be passed on the stack instead. This is done | |
2832 | by making @code{FUNCTION_ARG} return 0 whenever @var{named} is 0. | |
2833 | ||
2834 | @cindex @code{MUST_PASS_IN_STACK}, and @code{FUNCTION_ARG} | |
2835 | @cindex @code{REG_PARM_STACK_SPACE}, and @code{FUNCTION_ARG} | |
2836 | You may use the macro @code{MUST_PASS_IN_STACK (@var{mode}, @var{type})} | |
2837 | in the definition of this macro to determine if this argument is of a | |
2838 | type that must be passed in the stack. If @code{REG_PARM_STACK_SPACE} | |
2839 | is not defined and @code{FUNCTION_ARG} returns non-zero for such an | |
2840 | argument, the compiler will abort. If @code{REG_PARM_STACK_SPACE} is | |
2841 | defined, the argument will be computed in the stack and then loaded into | |
2842 | a register. | |
2843 | ||
d9a4ee00 JL |
2844 | @findex MUST_PASS_IN_STACK |
2845 | @item MUST_PASS_IN_STACK (@var{mode}, @var{type}) | |
2846 | Define as a C expression that evaluates to nonzero if we do not know how | |
2847 | to pass TYPE solely in registers. The file @file{expr.h} defines a | |
2848 | definition that is usually appropriate, refer to @file{expr.h} for additional | |
2849 | documentation. | |
2850 | ||
feca2ed3 JW |
2851 | @findex FUNCTION_INCOMING_ARG |
2852 | @item FUNCTION_INCOMING_ARG (@var{cum}, @var{mode}, @var{type}, @var{named}) | |
2853 | Define this macro if the target machine has ``register windows'', so | |
2854 | that the register in which a function sees an arguments is not | |
2855 | necessarily the same as the one in which the caller passed the | |
2856 | argument. | |
2857 | ||
2858 | For such machines, @code{FUNCTION_ARG} computes the register in which | |
2859 | the caller passes the value, and @code{FUNCTION_INCOMING_ARG} should | |
2860 | be defined in a similar fashion to tell the function being called | |
2861 | where the arguments will arrive. | |
2862 | ||
2863 | If @code{FUNCTION_INCOMING_ARG} is not defined, @code{FUNCTION_ARG} | |
2864 | serves both purposes.@refill | |
2865 | ||
2866 | @findex FUNCTION_ARG_PARTIAL_NREGS | |
2867 | @item FUNCTION_ARG_PARTIAL_NREGS (@var{cum}, @var{mode}, @var{type}, @var{named}) | |
2868 | A C expression for the number of words, at the beginning of an | |
2869 | argument, must be put in registers. The value must be zero for | |
2870 | arguments that are passed entirely in registers or that are entirely | |
2871 | pushed on the stack. | |
2872 | ||
2873 | On some machines, certain arguments must be passed partially in | |
2874 | registers and partially in memory. On these machines, typically the | |
2875 | first @var{n} words of arguments are passed in registers, and the rest | |
2876 | on the stack. If a multi-word argument (a @code{double} or a | |
2877 | structure) crosses that boundary, its first few words must be passed | |
2878 | in registers and the rest must be pushed. This macro tells the | |
2879 | compiler when this occurs, and how many of the words should go in | |
2880 | registers. | |
2881 | ||
2882 | @code{FUNCTION_ARG} for these arguments should return the first | |
2883 | register to be used by the caller for this argument; likewise | |
2884 | @code{FUNCTION_INCOMING_ARG}, for the called function. | |
2885 | ||
2886 | @findex FUNCTION_ARG_PASS_BY_REFERENCE | |
2887 | @item FUNCTION_ARG_PASS_BY_REFERENCE (@var{cum}, @var{mode}, @var{type}, @var{named}) | |
2888 | A C expression that indicates when an argument must be passed by reference. | |
2889 | If nonzero for an argument, a copy of that argument is made in memory and a | |
2890 | pointer to the argument is passed instead of the argument itself. | |
2891 | The pointer is passed in whatever way is appropriate for passing a pointer | |
2892 | to that type. | |
2893 | ||
2894 | On machines where @code{REG_PARM_STACK_SPACE} is not defined, a suitable | |
2895 | definition of this macro might be | |
2896 | @smallexample | |
2897 | #define FUNCTION_ARG_PASS_BY_REFERENCE\ | |
2898 | (CUM, MODE, TYPE, NAMED) \ | |
2899 | MUST_PASS_IN_STACK (MODE, TYPE) | |
2900 | @end smallexample | |
2901 | @c this is *still* too long. --mew 5feb93 | |
2902 | ||
2903 | @findex FUNCTION_ARG_CALLEE_COPIES | |
2904 | @item FUNCTION_ARG_CALLEE_COPIES (@var{cum}, @var{mode}, @var{type}, @var{named}) | |
2905 | If defined, a C expression that indicates when it is the called function's | |
2906 | responsibility to make a copy of arguments passed by invisible reference. | |
2907 | Normally, the caller makes a copy and passes the address of the copy to the | |
2908 | routine being called. When FUNCTION_ARG_CALLEE_COPIES is defined and is | |
2909 | nonzero, the caller does not make a copy. Instead, it passes a pointer to the | |
2910 | ``live'' value. The called function must not modify this value. If it can be | |
2911 | determined that the value won't be modified, it need not make a copy; | |
2912 | otherwise a copy must be made. | |
2913 | ||
2914 | @findex CUMULATIVE_ARGS | |
2915 | @item CUMULATIVE_ARGS | |
2916 | A C type for declaring a variable that is used as the first argument of | |
2917 | @code{FUNCTION_ARG} and other related values. For some target machines, | |
2918 | the type @code{int} suffices and can hold the number of bytes of | |
2919 | argument so far. | |
2920 | ||
2921 | There is no need to record in @code{CUMULATIVE_ARGS} anything about the | |
2922 | arguments that have been passed on the stack. The compiler has other | |
2923 | variables to keep track of that. For target machines on which all | |
2924 | arguments are passed on the stack, there is no need to store anything in | |
2925 | @code{CUMULATIVE_ARGS}; however, the data structure must exist and | |
2926 | should not be empty, so use @code{int}. | |
2927 | ||
2928 | @findex INIT_CUMULATIVE_ARGS | |
2929 | @item INIT_CUMULATIVE_ARGS (@var{cum}, @var{fntype}, @var{libname}, @var{indirect}) | |
2930 | A C statement (sans semicolon) for initializing the variable @var{cum} | |
2931 | for the state at the beginning of the argument list. The variable has | |
2932 | type @code{CUMULATIVE_ARGS}. The value of @var{fntype} is the tree node | |
2933 | for the data type of the function which will receive the args, or 0 | |
2934 | if the args are to a compiler support library function. The value of | |
2935 | @var{indirect} is nonzero when processing an indirect call, for example | |
2936 | a call through a function pointer. The value of @var{indirect} is zero | |
2937 | for a call to an explicitly named function, a library function call, or when | |
2938 | @code{INIT_CUMULATIVE_ARGS} is used to find arguments for the function | |
2939 | being compiled. | |
2940 | ||
2941 | When processing a call to a compiler support library function, | |
2942 | @var{libname} identifies which one. It is a @code{symbol_ref} rtx which | |
2943 | contains the name of the function, as a string. @var{libname} is 0 when | |
2944 | an ordinary C function call is being processed. Thus, each time this | |
2945 | macro is called, either @var{libname} or @var{fntype} is nonzero, but | |
2946 | never both of them at once. | |
2947 | ||
2948 | @findex INIT_CUMULATIVE_INCOMING_ARGS | |
2949 | @item INIT_CUMULATIVE_INCOMING_ARGS (@var{cum}, @var{fntype}, @var{libname}) | |
2950 | Like @code{INIT_CUMULATIVE_ARGS} but overrides it for the purposes of | |
2951 | finding the arguments for the function being compiled. If this macro is | |
2952 | undefined, @code{INIT_CUMULATIVE_ARGS} is used instead. | |
2953 | ||
2954 | The value passed for @var{libname} is always 0, since library routines | |
a3a15b4d | 2955 | with special calling conventions are never compiled with GCC. The |
feca2ed3 JW |
2956 | argument @var{libname} exists for symmetry with |
2957 | @code{INIT_CUMULATIVE_ARGS}. | |
2958 | @c could use "this macro" in place of @code{INIT_CUMULATIVE_ARGS}, maybe. | |
2959 | @c --mew 5feb93 i switched the order of the sentences. --mew 10feb93 | |
2960 | ||
2961 | @findex FUNCTION_ARG_ADVANCE | |
2962 | @item FUNCTION_ARG_ADVANCE (@var{cum}, @var{mode}, @var{type}, @var{named}) | |
2963 | A C statement (sans semicolon) to update the summarizer variable | |
2964 | @var{cum} to advance past an argument in the argument list. The | |
2965 | values @var{mode}, @var{type} and @var{named} describe that argument. | |
2966 | Once this is done, the variable @var{cum} is suitable for analyzing | |
2967 | the @emph{following} argument with @code{FUNCTION_ARG}, etc.@refill | |
2968 | ||
2969 | This macro need not do anything if the argument in question was passed | |
2970 | on the stack. The compiler knows how to track the amount of stack space | |
2971 | used for arguments without any special help. | |
2972 | ||
2973 | @findex FUNCTION_ARG_PADDING | |
2974 | @item FUNCTION_ARG_PADDING (@var{mode}, @var{type}) | |
2975 | If defined, a C expression which determines whether, and in which direction, | |
2976 | to pad out an argument with extra space. The value should be of type | |
2977 | @code{enum direction}: either @code{upward} to pad above the argument, | |
2978 | @code{downward} to pad below, or @code{none} to inhibit padding. | |
2979 | ||
2980 | The @emph{amount} of padding is always just enough to reach the next | |
2981 | multiple of @code{FUNCTION_ARG_BOUNDARY}; this macro does not control | |
2982 | it. | |
2983 | ||
2984 | This macro has a default definition which is right for most systems. | |
2985 | For little-endian machines, the default is to pad upward. For | |
2986 | big-endian machines, the default is to pad downward for an argument of | |
2987 | constant size shorter than an @code{int}, and upward otherwise. | |
2988 | ||
5e4f6244 CP |
2989 | @findex PAD_VARARGS_DOWN |
2990 | @item PAD_VARARGS_DOWN | |
2991 | If defined, a C expression which determines whether the default | |
2992 | implementation of va_arg will attempt to pad down before reading the | |
2993 | next argument, if that argument is smaller than its aligned space as | |
2994 | controlled by @code{PARM_BOUNDARY}. If this macro is not defined, all such | |
2995 | arguments are padded down if @code{BYTES_BIG_ENDIAN} is true. | |
2996 | ||
feca2ed3 JW |
2997 | @findex FUNCTION_ARG_BOUNDARY |
2998 | @item FUNCTION_ARG_BOUNDARY (@var{mode}, @var{type}) | |
2999 | If defined, a C expression that gives the alignment boundary, in bits, | |
3000 | of an argument with the specified mode and type. If it is not defined, | |
3001 | @code{PARM_BOUNDARY} is used for all arguments. | |
3002 | ||
3003 | @findex FUNCTION_ARG_REGNO_P | |
3004 | @item FUNCTION_ARG_REGNO_P (@var{regno}) | |
3005 | A C expression that is nonzero if @var{regno} is the number of a hard | |
3006 | register in which function arguments are sometimes passed. This does | |
3007 | @emph{not} include implicit arguments such as the static chain and | |
3008 | the structure-value address. On many machines, no registers can be | |
3009 | used for this purpose since all function arguments are pushed on the | |
3010 | stack. | |
bb1b857a GK |
3011 | |
3012 | @findex LOAD_ARGS_REVERSED | |
3013 | @item LOAD_ARGS_REVERSED | |
3014 | If defined, the order in which arguments are loaded into their | |
3015 | respective argument registers is reversed so that the last | |
4e5f1329 | 3016 | argument is loaded first. This macro only affects arguments |
bb1b857a GK |
3017 | passed in registers. |
3018 | ||
feca2ed3 JW |
3019 | @end table |
3020 | ||
3021 | @node Scalar Return | |
3022 | @subsection How Scalar Function Values Are Returned | |
3023 | @cindex return values in registers | |
3024 | @cindex values, returned by functions | |
3025 | @cindex scalars, returned as values | |
3026 | ||
3027 | This section discusses the macros that control returning scalars as | |
3028 | values---values that can fit in registers. | |
3029 | ||
3030 | @table @code | |
3031 | @findex TRADITIONAL_RETURN_FLOAT | |
3032 | @item TRADITIONAL_RETURN_FLOAT | |
3033 | Define this macro if @samp{-traditional} should not cause functions | |
3034 | declared to return @code{float} to convert the value to @code{double}. | |
3035 | ||
3036 | @findex FUNCTION_VALUE | |
3037 | @item FUNCTION_VALUE (@var{valtype}, @var{func}) | |
3038 | A C expression to create an RTX representing the place where a | |
3039 | function returns a value of data type @var{valtype}. @var{valtype} is | |
3040 | a tree node representing a data type. Write @code{TYPE_MODE | |
3041 | (@var{valtype})} to get the machine mode used to represent that type. | |
3042 | On many machines, only the mode is relevant. (Actually, on most | |
3043 | machines, scalar values are returned in the same place regardless of | |
3044 | mode).@refill | |
3045 | ||
3046 | The value of the expression is usually a @code{reg} RTX for the hard | |
3047 | register where the return value is stored. The value can also be a | |
3048 | @code{parallel} RTX, if the return value is in multiple places. See | |
3049 | @code{FUNCTION_ARG} for an explanation of the @code{parallel} form. | |
3050 | ||
3051 | If @code{PROMOTE_FUNCTION_RETURN} is defined, you must apply the same | |
3052 | promotion rules specified in @code{PROMOTE_MODE} if @var{valtype} is a | |
3053 | scalar type. | |
3054 | ||
3055 | If the precise function being called is known, @var{func} is a tree | |
3056 | node (@code{FUNCTION_DECL}) for it; otherwise, @var{func} is a null | |
3057 | pointer. This makes it possible to use a different value-returning | |
3058 | convention for specific functions when all their calls are | |
3059 | known.@refill | |
3060 | ||
3061 | @code{FUNCTION_VALUE} is not used for return vales with aggregate data | |
3062 | types, because these are returned in another way. See | |
3063 | @code{STRUCT_VALUE_REGNUM} and related macros, below. | |
3064 | ||
3065 | @findex FUNCTION_OUTGOING_VALUE | |
3066 | @item FUNCTION_OUTGOING_VALUE (@var{valtype}, @var{func}) | |
3067 | Define this macro if the target machine has ``register windows'' | |
3068 | so that the register in which a function returns its value is not | |
3069 | the same as the one in which the caller sees the value. | |
3070 | ||
3071 | For such machines, @code{FUNCTION_VALUE} computes the register in which | |
3072 | the caller will see the value. @code{FUNCTION_OUTGOING_VALUE} should be | |
3073 | defined in a similar fashion to tell the function where to put the | |
3074 | value.@refill | |
3075 | ||
3076 | If @code{FUNCTION_OUTGOING_VALUE} is not defined, | |
3077 | @code{FUNCTION_VALUE} serves both purposes.@refill | |
3078 | ||
3079 | @code{FUNCTION_OUTGOING_VALUE} is not used for return vales with | |
3080 | aggregate data types, because these are returned in another way. See | |
3081 | @code{STRUCT_VALUE_REGNUM} and related macros, below. | |
3082 | ||
3083 | @findex LIBCALL_VALUE | |
3084 | @item LIBCALL_VALUE (@var{mode}) | |
3085 | A C expression to create an RTX representing the place where a library | |
3086 | function returns a value of mode @var{mode}. If the precise function | |
3087 | being called is known, @var{func} is a tree node | |
3088 | (@code{FUNCTION_DECL}) for it; otherwise, @var{func} is a null | |
3089 | pointer. This makes it possible to use a different value-returning | |
3090 | convention for specific functions when all their calls are | |
3091 | known.@refill | |
3092 | ||
3093 | Note that ``library function'' in this context means a compiler | |
3094 | support routine, used to perform arithmetic, whose name is known | |
3095 | specially by the compiler and was not mentioned in the C code being | |
3096 | compiled. | |
3097 | ||
3098 | The definition of @code{LIBRARY_VALUE} need not be concerned aggregate | |
3099 | data types, because none of the library functions returns such types. | |
3100 | ||
3101 | @findex FUNCTION_VALUE_REGNO_P | |
3102 | @item FUNCTION_VALUE_REGNO_P (@var{regno}) | |
3103 | A C expression that is nonzero if @var{regno} is the number of a hard | |
3104 | register in which the values of called function may come back. | |
3105 | ||
3106 | A register whose use for returning values is limited to serving as the | |
3107 | second of a pair (for a value of type @code{double}, say) need not be | |
3108 | recognized by this macro. So for most machines, this definition | |
3109 | suffices: | |
3110 | ||
3111 | @example | |
3112 | #define FUNCTION_VALUE_REGNO_P(N) ((N) == 0) | |
3113 | @end example | |
3114 | ||
3115 | If the machine has register windows, so that the caller and the called | |
3116 | function use different registers for the return value, this macro | |
3117 | should recognize only the caller's register numbers. | |
3118 | ||
3119 | @findex APPLY_RESULT_SIZE | |
3120 | @item APPLY_RESULT_SIZE | |
3121 | Define this macro if @samp{untyped_call} and @samp{untyped_return} | |
3122 | need more space than is implied by @code{FUNCTION_VALUE_REGNO_P} for | |
3123 | saving and restoring an arbitrary return value. | |
3124 | @end table | |
3125 | ||
3126 | @node Aggregate Return | |
3127 | @subsection How Large Values Are Returned | |
3128 | @cindex aggregates as return values | |
3129 | @cindex large return values | |
3130 | @cindex returning aggregate values | |
3131 | @cindex structure value address | |
3132 | ||
3133 | When a function value's mode is @code{BLKmode} (and in some other | |
3134 | cases), the value is not returned according to @code{FUNCTION_VALUE} | |
3135 | (@pxref{Scalar Return}). Instead, the caller passes the address of a | |
3136 | block of memory in which the value should be stored. This address | |
3137 | is called the @dfn{structure value address}. | |
3138 | ||
3139 | This section describes how to control returning structure values in | |
3140 | memory. | |
3141 | ||
3142 | @table @code | |
3143 | @findex RETURN_IN_MEMORY | |
3144 | @item RETURN_IN_MEMORY (@var{type}) | |
3145 | A C expression which can inhibit the returning of certain function | |
3146 | values in registers, based on the type of value. A nonzero value says | |
3147 | to return the function value in memory, just as large structures are | |
3148 | always returned. Here @var{type} will be a C expression of type | |
3149 | @code{tree}, representing the data type of the value. | |
3150 | ||
3151 | Note that values of mode @code{BLKmode} must be explicitly handled | |
3152 | by this macro. Also, the option @samp{-fpcc-struct-return} | |
3153 | takes effect regardless of this macro. On most systems, it is | |
3154 | possible to leave the macro undefined; this causes a default | |
3155 | definition to be used, whose value is the constant 1 for @code{BLKmode} | |
3156 | values, and 0 otherwise. | |
3157 | ||
3158 | Do not use this macro to indicate that structures and unions should always | |
3159 | be returned in memory. You should instead use @code{DEFAULT_PCC_STRUCT_RETURN} | |
3160 | to indicate this. | |
3161 | ||
3162 | @findex DEFAULT_PCC_STRUCT_RETURN | |
3163 | @item DEFAULT_PCC_STRUCT_RETURN | |
3164 | Define this macro to be 1 if all structure and union return values must be | |
3165 | in memory. Since this results in slower code, this should be defined | |
3166 | only if needed for compatibility with other compilers or with an ABI. | |
3167 | If you define this macro to be 0, then the conventions used for structure | |
3168 | and union return values are decided by the @code{RETURN_IN_MEMORY} macro. | |
3169 | ||
3170 | If not defined, this defaults to the value 1. | |
3171 | ||
3172 | @findex STRUCT_VALUE_REGNUM | |
3173 | @item STRUCT_VALUE_REGNUM | |
3174 | If the structure value address is passed in a register, then | |
3175 | @code{STRUCT_VALUE_REGNUM} should be the number of that register. | |
3176 | ||
3177 | @findex STRUCT_VALUE | |
3178 | @item STRUCT_VALUE | |
3179 | If the structure value address is not passed in a register, define | |
3180 | @code{STRUCT_VALUE} as an expression returning an RTX for the place | |
3181 | where the address is passed. If it returns 0, the address is passed as | |
3182 | an ``invisible'' first argument. | |
3183 | ||
3184 | @findex STRUCT_VALUE_INCOMING_REGNUM | |
3185 | @item STRUCT_VALUE_INCOMING_REGNUM | |
3186 | On some architectures the place where the structure value address | |
3187 | is found by the called function is not the same place that the | |
3188 | caller put it. This can be due to register windows, or it could | |
3189 | be because the function prologue moves it to a different place. | |
3190 | ||
3191 | If the incoming location of the structure value address is in a | |
3192 | register, define this macro as the register number. | |
3193 | ||
3194 | @findex STRUCT_VALUE_INCOMING | |
3195 | @item STRUCT_VALUE_INCOMING | |
3196 | If the incoming location is not a register, then you should define | |
3197 | @code{STRUCT_VALUE_INCOMING} as an expression for an RTX for where the | |
3198 | called function should find the value. If it should find the value on | |
3199 | the stack, define this to create a @code{mem} which refers to the frame | |
3200 | pointer. A definition of 0 means that the address is passed as an | |
3201 | ``invisible'' first argument. | |
3202 | ||
3203 | @findex PCC_STATIC_STRUCT_RETURN | |
3204 | @item PCC_STATIC_STRUCT_RETURN | |
3205 | Define this macro if the usual system convention on the target machine | |
3206 | for returning structures and unions is for the called function to return | |
3207 | the address of a static variable containing the value. | |
3208 | ||
3209 | Do not define this if the usual system convention is for the caller to | |
3210 | pass an address to the subroutine. | |
3211 | ||
3212 | This macro has effect in @samp{-fpcc-struct-return} mode, but it does | |
3213 | nothing when you use @samp{-freg-struct-return} mode. | |
3214 | @end table | |
3215 | ||
3216 | @node Caller Saves | |
3217 | @subsection Caller-Saves Register Allocation | |
3218 | ||
a3a15b4d | 3219 | If you enable it, GCC can save registers around function calls. This |
feca2ed3 JW |
3220 | makes it possible to use call-clobbered registers to hold variables that |
3221 | must live across calls. | |
3222 | ||
3223 | @table @code | |
3224 | @findex DEFAULT_CALLER_SAVES | |
3225 | @item DEFAULT_CALLER_SAVES | |
3226 | Define this macro if function calls on the target machine do not preserve | |
3227 | any registers; in other words, if @code{CALL_USED_REGISTERS} has 1 | |
81610a0d HPN |
3228 | for all registers. When defined, this macro enables @samp{-fcaller-saves} |
3229 | by default for all optimization levels. It has no effect for optimization | |
3230 | levels 2 and higher, where @samp{-fcaller-saves} is the default. | |
feca2ed3 JW |
3231 | |
3232 | @findex CALLER_SAVE_PROFITABLE | |
3233 | @item CALLER_SAVE_PROFITABLE (@var{refs}, @var{calls}) | |
3234 | A C expression to determine whether it is worthwhile to consider placing | |
3235 | a pseudo-register in a call-clobbered hard register and saving and | |
3236 | restoring it around each function call. The expression should be 1 when | |
3237 | this is worth doing, and 0 otherwise. | |
3238 | ||
3239 | If you don't define this macro, a default is used which is good on most | |
3240 | machines: @code{4 * @var{calls} < @var{refs}}. | |
8d5c8167 JL |
3241 | |
3242 | @findex HARD_REGNO_CALLER_SAVE_MODE | |
3243 | @item HARD_REGNO_CALLER_SAVE_MODE (@var{regno}, @var{nregs}) | |
3244 | A C expression specifying which mode is required for saving @var{nregs} | |
3245 | of a pseudo-register in call-clobbered hard register @var{regno}. If | |
3246 | @var{regno} is unsuitable for caller save, @code{VOIDmode} should be | |
3247 | returned. For most machines this macro need not be defined since GCC | |
3248 | will select the smallest suitable mode. | |
feca2ed3 JW |
3249 | @end table |
3250 | ||
3251 | @node Function Entry | |
3252 | @subsection Function Entry and Exit | |
3253 | @cindex function entry and exit | |
3254 | @cindex prologue | |
3255 | @cindex epilogue | |
3256 | ||
3257 | This section describes the macros that output function entry | |
3258 | (@dfn{prologue}) and exit (@dfn{epilogue}) code. | |
3259 | ||
3260 | @table @code | |
3261 | @findex FUNCTION_PROLOGUE | |
3262 | @item FUNCTION_PROLOGUE (@var{file}, @var{size}) | |
3263 | A C compound statement that outputs the assembler code for entry to a | |
3264 | function. The prologue is responsible for setting up the stack frame, | |
3265 | initializing the frame pointer register, saving registers that must be | |
3266 | saved, and allocating @var{size} additional bytes of storage for the | |
3267 | local variables. @var{size} is an integer. @var{file} is a stdio | |
3268 | stream to which the assembler code should be output. | |
3269 | ||
3270 | The label for the beginning of the function need not be output by this | |
3271 | macro. That has already been done when the macro is run. | |
3272 | ||
3273 | @findex regs_ever_live | |
3274 | To determine which registers to save, the macro can refer to the array | |
3275 | @code{regs_ever_live}: element @var{r} is nonzero if hard register | |
3276 | @var{r} is used anywhere within the function. This implies the function | |
3277 | prologue should save register @var{r}, provided it is not one of the | |
3278 | call-used registers. (@code{FUNCTION_EPILOGUE} must likewise use | |
3279 | @code{regs_ever_live}.) | |
3280 | ||
3281 | On machines that have ``register windows'', the function entry code does | |
3282 | not save on the stack the registers that are in the windows, even if | |
3283 | they are supposed to be preserved by function calls; instead it takes | |
3284 | appropriate steps to ``push'' the register stack, if any non-call-used | |
3285 | registers are used in the function. | |
3286 | ||
3287 | @findex frame_pointer_needed | |
3288 | On machines where functions may or may not have frame-pointers, the | |
3289 | function entry code must vary accordingly; it must set up the frame | |
3290 | pointer if one is wanted, and not otherwise. To determine whether a | |
3291 | frame pointer is in wanted, the macro can refer to the variable | |
3292 | @code{frame_pointer_needed}. The variable's value will be 1 at run | |
3293 | time in a function that needs a frame pointer. @xref{Elimination}. | |
3294 | ||
3295 | The function entry code is responsible for allocating any stack space | |
3296 | required for the function. This stack space consists of the regions | |
3297 | listed below. In most cases, these regions are allocated in the | |
3298 | order listed, with the last listed region closest to the top of the | |
3299 | stack (the lowest address if @code{STACK_GROWS_DOWNWARD} is defined, and | |
3300 | the highest address if it is not defined). You can use a different order | |
3301 | for a machine if doing so is more convenient or required for | |
3302 | compatibility reasons. Except in cases where required by standard | |
3303 | or by a debugger, there is no reason why the stack layout used by GCC | |
3304 | need agree with that used by other compilers for a machine. | |
3305 | ||
3306 | @itemize @bullet | |
3307 | @item | |
3308 | @findex current_function_pretend_args_size | |
3309 | A region of @code{current_function_pretend_args_size} bytes of | |
3310 | uninitialized space just underneath the first argument arriving on the | |
3311 | stack. (This may not be at the very start of the allocated stack region | |
3312 | if the calling sequence has pushed anything else since pushing the stack | |
3313 | arguments. But usually, on such machines, nothing else has been pushed | |
3314 | yet, because the function prologue itself does all the pushing.) This | |
3315 | region is used on machines where an argument may be passed partly in | |
3316 | registers and partly in memory, and, in some cases to support the | |
3317 | features in @file{varargs.h} and @file{stdargs.h}. | |
3318 | ||
3319 | @item | |
3320 | An area of memory used to save certain registers used by the function. | |
3321 | The size of this area, which may also include space for such things as | |
3322 | the return address and pointers to previous stack frames, is | |
3323 | machine-specific and usually depends on which registers have been used | |
3324 | in the function. Machines with register windows often do not require | |
3325 | a save area. | |
3326 | ||
3327 | @item | |
3328 | A region of at least @var{size} bytes, possibly rounded up to an allocation | |
3329 | boundary, to contain the local variables of the function. On some machines, | |
3330 | this region and the save area may occur in the opposite order, with the | |
3331 | save area closer to the top of the stack. | |
3332 | ||
3333 | @item | |
3334 | @cindex @code{ACCUMULATE_OUTGOING_ARGS} and stack frames | |
3335 | Optionally, when @code{ACCUMULATE_OUTGOING_ARGS} is defined, a region of | |
3336 | @code{current_function_outgoing_args_size} bytes to be used for outgoing | |
3337 | argument lists of the function. @xref{Stack Arguments}. | |
3338 | @end itemize | |
3339 | ||
3340 | Normally, it is necessary for the macros @code{FUNCTION_PROLOGUE} and | |
3341 | @code{FUNCTION_EPILOGUE} to treat leaf functions specially. The C | |
54ff41b7 | 3342 | variable @code{current_function_is_leaf} is nonzero for such a function. |
feca2ed3 JW |
3343 | |
3344 | @findex EXIT_IGNORE_STACK | |
3345 | @item EXIT_IGNORE_STACK | |
3346 | Define this macro as a C expression that is nonzero if the return | |
3347 | instruction or the function epilogue ignores the value of the stack | |
3348 | pointer; in other words, if it is safe to delete an instruction to | |
3349 | adjust the stack pointer before a return from the function. | |
3350 | ||
3351 | Note that this macro's value is relevant only for functions for which | |
3352 | frame pointers are maintained. It is never safe to delete a final | |
3353 | stack adjustment in a function that has no frame pointer, and the | |
3354 | compiler knows this regardless of @code{EXIT_IGNORE_STACK}. | |
3355 | ||
3356 | @findex EPILOGUE_USES | |
3357 | @item EPILOGUE_USES (@var{regno}) | |
8760eaae | 3358 | Define this macro as a C expression that is nonzero for registers that are |
feca2ed3 JW |
3359 | used by the epilogue or the @samp{return} pattern. The stack and frame |
3360 | pointer registers are already be assumed to be used as needed. | |
3361 | ||
3362 | @findex FUNCTION_EPILOGUE | |
3363 | @item FUNCTION_EPILOGUE (@var{file}, @var{size}) | |
3364 | A C compound statement that outputs the assembler code for exit from a | |
3365 | function. The epilogue is responsible for restoring the saved | |
3366 | registers and stack pointer to their values when the function was | |
3367 | called, and returning control to the caller. This macro takes the | |
3368 | same arguments as the macro @code{FUNCTION_PROLOGUE}, and the | |
3369 | registers to restore are determined from @code{regs_ever_live} and | |
3370 | @code{CALL_USED_REGISTERS} in the same way. | |
3371 | ||
3372 | On some machines, there is a single instruction that does all the work | |
3373 | of returning from the function. On these machines, give that | |
3374 | instruction the name @samp{return} and do not define the macro | |
3375 | @code{FUNCTION_EPILOGUE} at all. | |
3376 | ||
3377 | Do not define a pattern named @samp{return} if you want the | |
3378 | @code{FUNCTION_EPILOGUE} to be used. If you want the target switches | |
3379 | to control whether return instructions or epilogues are used, define a | |
3380 | @samp{return} pattern with a validity condition that tests the target | |
3381 | switches appropriately. If the @samp{return} pattern's validity | |
3382 | condition is false, epilogues will be used. | |
3383 | ||
3384 | On machines where functions may or may not have frame-pointers, the | |
3385 | function exit code must vary accordingly. Sometimes the code for these | |
3386 | two cases is completely different. To determine whether a frame pointer | |
3387 | is wanted, the macro can refer to the variable | |
3388 | @code{frame_pointer_needed}. The variable's value will be 1 when compiling | |
3389 | a function that needs a frame pointer. | |
3390 | ||
3391 | Normally, @code{FUNCTION_PROLOGUE} and @code{FUNCTION_EPILOGUE} must | |
54ff41b7 JW |
3392 | treat leaf functions specially. The C variable @code{current_function_is_leaf} |
3393 | is nonzero for such a function. @xref{Leaf Functions}. | |
feca2ed3 JW |
3394 | |
3395 | On some machines, some functions pop their arguments on exit while | |
3396 | others leave that for the caller to do. For example, the 68020 when | |
3397 | given @samp{-mrtd} pops arguments in functions that take a fixed | |
3398 | number of arguments. | |
3399 | ||
3400 | @findex current_function_pops_args | |
3401 | Your definition of the macro @code{RETURN_POPS_ARGS} decides which | |
3402 | functions pop their own arguments. @code{FUNCTION_EPILOGUE} needs to | |
3403 | know what was decided. The variable that is called | |
3404 | @code{current_function_pops_args} is the number of bytes of its | |
3405 | arguments that a function should pop. @xref{Scalar Return}. | |
3406 | @c what is the "its arguments" in the above sentence referring to, pray | |
3407 | @c tell? --mew 5feb93 | |
3408 | ||
3409 | @findex DELAY_SLOTS_FOR_EPILOGUE | |
3410 | @item DELAY_SLOTS_FOR_EPILOGUE | |
3411 | Define this macro if the function epilogue contains delay slots to which | |
3412 | instructions from the rest of the function can be ``moved''. The | |
3413 | definition should be a C expression whose value is an integer | |
3414 | representing the number of delay slots there. | |
3415 | ||
3416 | @findex ELIGIBLE_FOR_EPILOGUE_DELAY | |
3417 | @item ELIGIBLE_FOR_EPILOGUE_DELAY (@var{insn}, @var{n}) | |
3418 | A C expression that returns 1 if @var{insn} can be placed in delay | |
3419 | slot number @var{n} of the epilogue. | |
3420 | ||
3421 | The argument @var{n} is an integer which identifies the delay slot now | |
3422 | being considered (since different slots may have different rules of | |
3423 | eligibility). It is never negative and is always less than the number | |
3424 | of epilogue delay slots (what @code{DELAY_SLOTS_FOR_EPILOGUE} returns). | |
3425 | If you reject a particular insn for a given delay slot, in principle, it | |
3426 | may be reconsidered for a subsequent delay slot. Also, other insns may | |
3427 | (at least in principle) be considered for the so far unfilled delay | |
3428 | slot. | |
3429 | ||
3430 | @findex current_function_epilogue_delay_list | |
3431 | @findex final_scan_insn | |
3432 | The insns accepted to fill the epilogue delay slots are put in an RTL | |
3433 | list made with @code{insn_list} objects, stored in the variable | |
3434 | @code{current_function_epilogue_delay_list}. The insn for the first | |
3435 | delay slot comes first in the list. Your definition of the macro | |
3436 | @code{FUNCTION_EPILOGUE} should fill the delay slots by outputting the | |
3437 | insns in this list, usually by calling @code{final_scan_insn}. | |
3438 | ||
3439 | You need not define this macro if you did not define | |
3440 | @code{DELAY_SLOTS_FOR_EPILOGUE}. | |
3441 | ||
3442 | @findex ASM_OUTPUT_MI_THUNK | |
3443 | @item ASM_OUTPUT_MI_THUNK (@var{file}, @var{thunk_fndecl}, @var{delta}, @var{function}) | |
3444 | A C compound statement that outputs the assembler code for a thunk | |
3445 | function, used to implement C++ virtual function calls with multiple | |
3446 | inheritance. The thunk acts as a wrapper around a virtual function, | |
3447 | adjusting the implicit object parameter before handing control off to | |
3448 | the real function. | |
3449 | ||
3450 | First, emit code to add the integer @var{delta} to the location that | |
3451 | contains the incoming first argument. Assume that this argument | |
3452 | contains a pointer, and is the one used to pass the @code{this} pointer | |
3453 | in C++. This is the incoming argument @emph{before} the function prologue, | |
3454 | e.g. @samp{%o0} on a sparc. The addition must preserve the values of | |
3455 | all other incoming arguments. | |
3456 | ||
3457 | After the addition, emit code to jump to @var{function}, which is a | |
3458 | @code{FUNCTION_DECL}. This is a direct pure jump, not a call, and does | |
3459 | not touch the return address. Hence returning from @var{FUNCTION} will | |
3460 | return to whoever called the current @samp{thunk}. | |
3461 | ||
3462 | The effect must be as if @var{function} had been called directly with | |
3463 | the adjusted first argument. This macro is responsible for emitting all | |
3464 | of the code for a thunk function; @code{FUNCTION_PROLOGUE} and | |
3465 | @code{FUNCTION_EPILOGUE} are not invoked. | |
3466 | ||
3467 | The @var{thunk_fndecl} is redundant. (@var{delta} and @var{function} | |
3468 | have already been extracted from it.) It might possibly be useful on | |
3469 | some targets, but probably not. | |
3470 | ||
861bb6c1 JL |
3471 | If you do not define this macro, the target-independent code in the C++ |
3472 | frontend will generate a less efficient heavyweight thunk that calls | |
3473 | @var{function} instead of jumping to it. The generic approach does | |
3474 | not support varargs. | |
feca2ed3 JW |
3475 | @end table |
3476 | ||
3477 | @node Profiling | |
3478 | @subsection Generating Code for Profiling | |
3479 | @cindex profiling, code generation | |
3480 | ||
3481 | These macros will help you generate code for profiling. | |
3482 | ||
3483 | @table @code | |
3484 | @findex FUNCTION_PROFILER | |
3485 | @item FUNCTION_PROFILER (@var{file}, @var{labelno}) | |
3486 | A C statement or compound statement to output to @var{file} some | |
3487 | assembler code to call the profiling subroutine @code{mcount}. | |
3488 | Before calling, the assembler code must load the address of a | |
3489 | counter variable into a register where @code{mcount} expects to | |
3490 | find the address. The name of this variable is @samp{LP} followed | |
3491 | by the number @var{labelno}, so you would generate the name using | |
3492 | @samp{LP%d} in a @code{fprintf}. | |
3493 | ||
3494 | @findex mcount | |
3495 | The details of how the address should be passed to @code{mcount} are | |
a3a15b4d | 3496 | determined by your operating system environment, not by GCC. To |
feca2ed3 JW |
3497 | figure them out, compile a small program for profiling using the |
3498 | system's installed C compiler and look at the assembler code that | |
3499 | results. | |
3500 | ||
3501 | @findex PROFILE_BEFORE_PROLOGUE | |
3502 | @item PROFILE_BEFORE_PROLOGUE | |
3503 | Define this macro if the code for function profiling should come before | |
3504 | the function prologue. Normally, the profiling code comes after. | |
3505 | ||
3506 | @findex FUNCTION_BLOCK_PROFILER | |
3507 | @vindex profile_block_flag | |
3508 | @item FUNCTION_BLOCK_PROFILER (@var{file}, @var{labelno}) | |
3509 | A C statement or compound statement to output to @var{file} some | |
3510 | assembler code to initialize basic-block profiling for the current | |
3511 | object module. The global compile flag @code{profile_block_flag} | |
956d6950 | 3512 | distinguishes two profile modes. |
feca2ed3 JW |
3513 | |
3514 | @table @code | |
3515 | @findex __bb_init_func | |
3516 | @item profile_block_flag != 2 | |
3517 | Output code to call the subroutine @code{__bb_init_func} once per | |
3518 | object module, passing it as its sole argument the address of a block | |
3519 | allocated in the object module. | |
3520 | ||
3521 | The name of the block is a local symbol made with this statement: | |
3522 | ||
3523 | @smallexample | |
3524 | ASM_GENERATE_INTERNAL_LABEL (@var{buffer}, "LPBX", 0); | |
3525 | @end smallexample | |
3526 | ||
3527 | Of course, since you are writing the definition of | |
3528 | @code{ASM_GENERATE_INTERNAL_LABEL} as well as that of this macro, you | |
3529 | can take a short cut in the definition of this macro and use the name | |
3530 | that you know will result. | |
3531 | ||
3532 | The first word of this block is a flag which will be nonzero if the | |
3533 | object module has already been initialized. So test this word first, | |
3534 | and do not call @code{__bb_init_func} if the flag is | |
3535 | nonzero. BLOCK_OR_LABEL contains a unique number which may be used to | |
3536 | generate a label as a branch destination when @code{__bb_init_func} | |
3537 | will not be called. | |
3538 | ||
3539 | Described in assembler language, the code to be output looks like: | |
3540 | ||
3541 | @example | |
3542 | cmp (LPBX0),0 | |
3543 | bne local_label | |
3544 | parameter1 <- LPBX0 | |
3545 | call __bb_init_func | |
3546 | local_label: | |
3547 | @end example | |
3548 | ||
3549 | @findex __bb_init_trace_func | |
3550 | @item profile_block_flag == 2 | |
3551 | Output code to call the subroutine @code{__bb_init_trace_func} | |
3552 | and pass two parameters to it. The first parameter is the same as | |
3553 | for @code{__bb_init_func}. The second parameter is the number of the | |
3554 | first basic block of the function as given by BLOCK_OR_LABEL. Note | |
3555 | that @code{__bb_init_trace_func} has to be called, even if the object | |
3556 | module has been initialized already. | |
3557 | ||
3558 | Described in assembler language, the code to be output looks like: | |
3559 | @example | |
3560 | parameter1 <- LPBX0 | |
3561 | parameter2 <- BLOCK_OR_LABEL | |
3562 | call __bb_init_trace_func | |
3563 | @end example | |
3564 | @end table | |
3565 | ||
3566 | @findex BLOCK_PROFILER | |
3567 | @vindex profile_block_flag | |
3568 | @item BLOCK_PROFILER (@var{file}, @var{blockno}) | |
3569 | A C statement or compound statement to output to @var{file} some | |
3570 | assembler code to increment the count associated with the basic | |
3571 | block number @var{blockno}. The global compile flag | |
956d6950 | 3572 | @code{profile_block_flag} distinguishes two profile modes. |
feca2ed3 JW |
3573 | |
3574 | @table @code | |
3575 | @item profile_block_flag != 2 | |
3576 | Output code to increment the counter directly. Basic blocks are | |
3577 | numbered separately from zero within each compilation. The count | |
3578 | associated with block number @var{blockno} is at index | |
3579 | @var{blockno} in a vector of words; the name of this array is a local | |
3580 | symbol made with this statement: | |
3581 | ||
3582 | @smallexample | |
3583 | ASM_GENERATE_INTERNAL_LABEL (@var{buffer}, "LPBX", 2); | |
3584 | @end smallexample | |
3585 | ||
3586 | @c This paragraph is the same as one a few paragraphs up. | |
3587 | @c That is not an error. | |
3588 | Of course, since you are writing the definition of | |
3589 | @code{ASM_GENERATE_INTERNAL_LABEL} as well as that of this macro, you | |
3590 | can take a short cut in the definition of this macro and use the name | |
3591 | that you know will result. | |
3592 | ||
3593 | Described in assembler language, the code to be output looks like: | |
3594 | ||
3595 | @smallexample | |
3596 | inc (LPBX2+4*BLOCKNO) | |
3597 | @end smallexample | |
3598 | ||
3599 | @vindex __bb | |
3600 | @findex __bb_trace_func | |
3601 | @item profile_block_flag == 2 | |
3602 | Output code to initialize the global structure @code{__bb} and | |
3603 | call the function @code{__bb_trace_func}, which will increment the | |
3604 | counter. | |
3605 | ||
3606 | @code{__bb} consists of two words. In the first word, the current | |
3607 | basic block number, as given by BLOCKNO, has to be stored. In | |
3608 | the second word, the address of a block allocated in the object | |
3609 | module has to be stored. The address is given by the label created | |
3610 | with this statement: | |
3611 | ||
3612 | @smallexample | |
3613 | ASM_GENERATE_INTERNAL_LABEL (@var{buffer}, "LPBX", 0); | |
3614 | @end smallexample | |
3615 | ||
3616 | Described in assembler language, the code to be output looks like: | |
3617 | @example | |
3618 | move BLOCKNO -> (__bb) | |
3619 | move LPBX0 -> (__bb+4) | |
3620 | call __bb_trace_func | |
3621 | @end example | |
3622 | @end table | |
3623 | ||
3624 | @findex FUNCTION_BLOCK_PROFILER_EXIT | |
3625 | @findex __bb_trace_ret | |
3626 | @vindex profile_block_flag | |
3627 | @item FUNCTION_BLOCK_PROFILER_EXIT (@var{file}) | |
3628 | A C statement or compound statement to output to @var{file} | |
3629 | assembler code to call function @code{__bb_trace_ret}. The | |
3630 | assembler code should only be output | |
3631 | if the global compile flag @code{profile_block_flag} == 2. This | |
3632 | macro has to be used at every place where code for returning from | |
3633 | a function is generated (e.g. @code{FUNCTION_EPILOGUE}). Although | |
3634 | you have to write the definition of @code{FUNCTION_EPILOGUE} | |
3635 | as well, you have to define this macro to tell the compiler, that | |
3636 | the proper call to @code{__bb_trace_ret} is produced. | |
3637 | ||
3638 | @findex MACHINE_STATE_SAVE | |
3639 | @findex __bb_init_trace_func | |
3640 | @findex __bb_trace_func | |
3641 | @findex __bb_trace_ret | |
3642 | @item MACHINE_STATE_SAVE (@var{id}) | |
3643 | A C statement or compound statement to save all registers, which may | |
3644 | be clobbered by a function call, including condition codes. The | |
3645 | @code{asm} statement will be mostly likely needed to handle this | |
3646 | task. Local labels in the assembler code can be concatenated with the | |
8760eaae | 3647 | string @var{id}, to obtain a unique label name. |
feca2ed3 JW |
3648 | |
3649 | Registers or condition codes clobbered by @code{FUNCTION_PROLOGUE} or | |
3650 | @code{FUNCTION_EPILOGUE} must be saved in the macros | |
3651 | @code{FUNCTION_BLOCK_PROFILER}, @code{FUNCTION_BLOCK_PROFILER_EXIT} and | |
3652 | @code{BLOCK_PROFILER} prior calling @code{__bb_init_trace_func}, | |
3653 | @code{__bb_trace_ret} and @code{__bb_trace_func} respectively. | |
3654 | ||
3655 | @findex MACHINE_STATE_RESTORE | |
3656 | @findex __bb_init_trace_func | |
3657 | @findex __bb_trace_func | |
3658 | @findex __bb_trace_ret | |
3659 | @item MACHINE_STATE_RESTORE (@var{id}) | |
3660 | A C statement or compound statement to restore all registers, including | |
3661 | condition codes, saved by @code{MACHINE_STATE_SAVE}. | |
3662 | ||
3663 | Registers or condition codes clobbered by @code{FUNCTION_PROLOGUE} or | |
3664 | @code{FUNCTION_EPILOGUE} must be restored in the macros | |
3665 | @code{FUNCTION_BLOCK_PROFILER}, @code{FUNCTION_BLOCK_PROFILER_EXIT} and | |
3666 | @code{BLOCK_PROFILER} after calling @code{__bb_init_trace_func}, | |
3667 | @code{__bb_trace_ret} and @code{__bb_trace_func} respectively. | |
3668 | ||
3669 | @findex BLOCK_PROFILER_CODE | |
3670 | @item BLOCK_PROFILER_CODE | |
3671 | A C function or functions which are needed in the library to | |
3672 | support block profiling. | |
3673 | @end table | |
3674 | ||
b36f4ed3 NC |
3675 | @node Inlining |
3676 | @subsection Permitting inlining of functions with attributes | |
3677 | @cindex inlining | |
3678 | ||
3679 | By default if a function has a target specific attribute attached to it, | |
3680 | it will not be inlined. This behaviour can be overridden if the target | |
3681 | defines the @samp{FUNCTION_ATTRIBUTE_INLINABLE_P} macro. This macro | |
3682 | takes one argument, a @samp{DECL} describing the function. It should | |
3683 | return non-zero if the function can be inlined, otherwise it should | |
3684 | return 0. | |
3685 | ||
feca2ed3 JW |
3686 | @node Varargs |
3687 | @section Implementing the Varargs Macros | |
3688 | @cindex varargs implementation | |
3689 | ||
a3a15b4d | 3690 | GCC comes with an implementation of @file{varargs.h} and |
feca2ed3 JW |
3691 | @file{stdarg.h} that work without change on machines that pass arguments |
3692 | on the stack. Other machines require their own implementations of | |
3693 | varargs, and the two machine independent header files must have | |
3694 | conditionals to include it. | |
3695 | ||
3696 | ANSI @file{stdarg.h} differs from traditional @file{varargs.h} mainly in | |
3697 | the calling convention for @code{va_start}. The traditional | |
3698 | implementation takes just one argument, which is the variable in which | |
3699 | to store the argument pointer. The ANSI implementation of | |
3700 | @code{va_start} takes an additional second argument. The user is | |
3701 | supposed to write the last named argument of the function here. | |
3702 | ||
3703 | However, @code{va_start} should not use this argument. The way to find | |
3704 | the end of the named arguments is with the built-in functions described | |
3705 | below. | |
3706 | ||
3707 | @table @code | |
3708 | @findex __builtin_saveregs | |
3709 | @item __builtin_saveregs () | |
3710 | Use this built-in function to save the argument registers in memory so | |
3711 | that the varargs mechanism can access them. Both ANSI and traditional | |
3712 | versions of @code{va_start} must use @code{__builtin_saveregs}, unless | |
3713 | you use @code{SETUP_INCOMING_VARARGS} (see below) instead. | |
3714 | ||
3715 | On some machines, @code{__builtin_saveregs} is open-coded under the | |
3716 | control of the macro @code{EXPAND_BUILTIN_SAVEREGS}. On other machines, | |
3717 | it calls a routine written in assembler language, found in | |
3718 | @file{libgcc2.c}. | |
3719 | ||
3720 | Code generated for the call to @code{__builtin_saveregs} appears at the | |
3721 | beginning of the function, as opposed to where the call to | |
3722 | @code{__builtin_saveregs} is written, regardless of what the code is. | |
3723 | This is because the registers must be saved before the function starts | |
3724 | to use them for its own purposes. | |
3725 | @c i rewrote the first sentence above to fix an overfull hbox. --mew | |
3726 | @c 10feb93 | |
3727 | ||
3728 | @findex __builtin_args_info | |
3729 | @item __builtin_args_info (@var{category}) | |
3730 | Use this built-in function to find the first anonymous arguments in | |
3731 | registers. | |
3732 | ||
3733 | In general, a machine may have several categories of registers used for | |
3734 | arguments, each for a particular category of data types. (For example, | |
3735 | on some machines, floating-point registers are used for floating-point | |
3736 | arguments while other arguments are passed in the general registers.) | |
3737 | To make non-varargs functions use the proper calling convention, you | |
3738 | have defined the @code{CUMULATIVE_ARGS} data type to record how many | |
3739 | registers in each category have been used so far | |
3740 | ||
3741 | @code{__builtin_args_info} accesses the same data structure of type | |
3742 | @code{CUMULATIVE_ARGS} after the ordinary argument layout is finished | |
3743 | with it, with @var{category} specifying which word to access. Thus, the | |
3744 | value indicates the first unused register in a given category. | |
3745 | ||
3746 | Normally, you would use @code{__builtin_args_info} in the implementation | |
3747 | of @code{va_start}, accessing each category just once and storing the | |
3748 | value in the @code{va_list} object. This is because @code{va_list} will | |
3749 | have to update the values, and there is no way to alter the | |
3750 | values accessed by @code{__builtin_args_info}. | |
3751 | ||
3752 | @findex __builtin_next_arg | |
3753 | @item __builtin_next_arg (@var{lastarg}) | |
3754 | This is the equivalent of @code{__builtin_args_info}, for stack | |
3755 | arguments. It returns the address of the first anonymous stack | |
3756 | argument, as type @code{void *}. If @code{ARGS_GROW_DOWNWARD}, it | |
3757 | returns the address of the location above the first anonymous stack | |
3758 | argument. Use it in @code{va_start} to initialize the pointer for | |
3759 | fetching arguments from the stack. Also use it in @code{va_start} to | |
3760 | verify that the second parameter @var{lastarg} is the last named argument | |
3761 | of the current function. | |
3762 | ||
3763 | @findex __builtin_classify_type | |
3764 | @item __builtin_classify_type (@var{object}) | |
3765 | Since each machine has its own conventions for which data types are | |
3766 | passed in which kind of register, your implementation of @code{va_arg} | |
3767 | has to embody these conventions. The easiest way to categorize the | |
3768 | specified data type is to use @code{__builtin_classify_type} together | |
3769 | with @code{sizeof} and @code{__alignof__}. | |
3770 | ||
3771 | @code{__builtin_classify_type} ignores the value of @var{object}, | |
3772 | considering only its data type. It returns an integer describing what | |
3773 | kind of type that is---integer, floating, pointer, structure, and so on. | |
3774 | ||
3775 | The file @file{typeclass.h} defines an enumeration that you can use to | |
3776 | interpret the values of @code{__builtin_classify_type}. | |
3777 | @end table | |
3778 | ||
3779 | These machine description macros help implement varargs: | |
3780 | ||
3781 | @table @code | |
3782 | @findex EXPAND_BUILTIN_SAVEREGS | |
d3707adb | 3783 | @item EXPAND_BUILTIN_SAVEREGS () |
feca2ed3 JW |
3784 | If defined, is a C expression that produces the machine-specific code |
3785 | for a call to @code{__builtin_saveregs}. This code will be moved to the | |
3786 | very beginning of the function, before any parameter access are made. | |
3787 | The return value of this function should be an RTX that contains the | |
3788 | value to use as the return of @code{__builtin_saveregs}. | |
3789 | ||
feca2ed3 | 3790 | @findex SETUP_INCOMING_VARARGS |
59d40964 | 3791 | @item SETUP_INCOMING_VARARGS (@var{args_so_far}, @var{mode}, @var{type}, @var{pretend_args_size}, @var{second_time}) |
feca2ed3 JW |
3792 | This macro offers an alternative to using @code{__builtin_saveregs} and |
3793 | defining the macro @code{EXPAND_BUILTIN_SAVEREGS}. Use it to store the | |
3794 | anonymous register arguments into the stack so that all the arguments | |
3795 | appear to have been passed consecutively on the stack. Once this is | |
3796 | done, you can use the standard implementation of varargs that works for | |
3797 | machines that pass all their arguments on the stack. | |
3798 | ||
3799 | The argument @var{args_so_far} is the @code{CUMULATIVE_ARGS} data | |
8760eaae | 3800 | structure, containing the values that are obtained after processing the |
feca2ed3 JW |
3801 | named arguments. The arguments @var{mode} and @var{type} describe the |
3802 | last named argument---its machine mode and its data type as a tree node. | |
3803 | ||
3804 | The macro implementation should do two things: first, push onto the | |
3805 | stack all the argument registers @emph{not} used for the named | |
3806 | arguments, and second, store the size of the data thus pushed into the | |
3807 | @code{int}-valued variable whose name is supplied as the argument | |
3808 | @var{pretend_args_size}. The value that you store here will serve as | |
3809 | additional offset for setting up the stack frame. | |
3810 | ||
3811 | Because you must generate code to push the anonymous arguments at | |
3812 | compile time without knowing their data types, | |
3813 | @code{SETUP_INCOMING_VARARGS} is only useful on machines that have just | |
3814 | a single category of argument register and use it uniformly for all data | |
3815 | types. | |
3816 | ||
3817 | If the argument @var{second_time} is nonzero, it means that the | |
3818 | arguments of the function are being analyzed for the second time. This | |
3819 | happens for an inline function, which is not actually compiled until the | |
3820 | end of the source file. The macro @code{SETUP_INCOMING_VARARGS} should | |
3821 | not generate any instructions in this case. | |
3822 | ||
3823 | @findex STRICT_ARGUMENT_NAMING | |
3824 | @item STRICT_ARGUMENT_NAMING | |
e5e809f4 JL |
3825 | Define this macro to be a nonzero value if the location where a function |
3826 | argument is passed depends on whether or not it is a named argument. | |
feca2ed3 JW |
3827 | |
3828 | This macro controls how the @var{named} argument to @code{FUNCTION_ARG} | |
e5e809f4 JL |
3829 | is set for varargs and stdarg functions. If this macro returns a |
3830 | nonzero value, the @var{named} argument is always true for named | |
3831 | arguments, and false for unnamed arguments. If it returns a value of | |
3832 | zero, but @code{SETUP_INCOMING_VARARGS} is defined, then all arguments | |
3833 | are treated as named. Otherwise, all named arguments except the last | |
3834 | are treated as named. | |
3835 | ||
3836 | You need not define this macro if it always returns zero. | |
9ab70a9b R |
3837 | |
3838 | @findex PRETEND_OUTGOING_VARARGS_NAMED | |
3839 | @item PRETEND_OUTGOING_VARARGS_NAMED | |
3840 | If you need to conditionally change ABIs so that one works with | |
3841 | @code{SETUP_INCOMING_VARARGS}, but the other works like neither | |
3842 | @code{SETUP_INCOMING_VARARGS} nor @code{STRICT_ARGUMENT_NAMING} was | |
3843 | defined, then define this macro to return nonzero if | |
3844 | @code{SETUP_INCOMING_VARARGS} is used, zero otherwise. | |
3845 | Otherwise, you should not define this macro. | |
feca2ed3 JW |
3846 | @end table |
3847 | ||
3848 | @node Trampolines | |
3849 | @section Trampolines for Nested Functions | |
3850 | @cindex trampolines for nested functions | |
3851 | @cindex nested functions, trampolines for | |
3852 | ||
3853 | A @dfn{trampoline} is a small piece of code that is created at run time | |
3854 | when the address of a nested function is taken. It normally resides on | |
3855 | the stack, in the stack frame of the containing function. These macros | |
a3a15b4d | 3856 | tell GCC how to generate code to allocate and initialize a |
feca2ed3 JW |
3857 | trampoline. |
3858 | ||
3859 | The instructions in the trampoline must do two things: load a constant | |
3860 | address into the static chain register, and jump to the real address of | |
3861 | the nested function. On CISC machines such as the m68k, this requires | |
3862 | two instructions, a move immediate and a jump. Then the two addresses | |
3863 | exist in the trampoline as word-long immediate operands. On RISC | |
3864 | machines, it is often necessary to load each address into a register in | |
3865 | two parts. Then pieces of each address form separate immediate | |
3866 | operands. | |
3867 | ||
3868 | The code generated to initialize the trampoline must store the variable | |
3869 | parts---the static chain value and the function address---into the | |
3870 | immediate operands of the instructions. On a CISC machine, this is | |
3871 | simply a matter of copying each address to a memory reference at the | |
3872 | proper offset from the start of the trampoline. On a RISC machine, it | |
3873 | may be necessary to take out pieces of the address and store them | |
3874 | separately. | |
3875 | ||
3876 | @table @code | |
3877 | @findex TRAMPOLINE_TEMPLATE | |
3878 | @item TRAMPOLINE_TEMPLATE (@var{file}) | |
3879 | A C statement to output, on the stream @var{file}, assembler code for a | |
3880 | block of data that contains the constant parts of a trampoline. This | |
3881 | code should not include a label---the label is taken care of | |
3882 | automatically. | |
3883 | ||
3884 | If you do not define this macro, it means no template is needed | |
3885 | for the target. Do not define this macro on systems where the block move | |
3886 | code to copy the trampoline into place would be larger than the code | |
3887 | to generate it on the spot. | |
3888 | ||
3889 | @findex TRAMPOLINE_SECTION | |
3890 | @item TRAMPOLINE_SECTION | |
3891 | The name of a subroutine to switch to the section in which the | |
3892 | trampoline template is to be placed (@pxref{Sections}). The default is | |
3893 | a value of @samp{readonly_data_section}, which places the trampoline in | |
3894 | the section containing read-only data. | |
3895 | ||
3896 | @findex TRAMPOLINE_SIZE | |
3897 | @item TRAMPOLINE_SIZE | |
3898 | A C expression for the size in bytes of the trampoline, as an integer. | |
3899 | ||
3900 | @findex TRAMPOLINE_ALIGNMENT | |
3901 | @item TRAMPOLINE_ALIGNMENT | |
3902 | Alignment required for trampolines, in bits. | |
3903 | ||
3904 | If you don't define this macro, the value of @code{BIGGEST_ALIGNMENT} | |
3905 | is used for aligning trampolines. | |
3906 | ||
3907 | @findex INITIALIZE_TRAMPOLINE | |
3908 | @item INITIALIZE_TRAMPOLINE (@var{addr}, @var{fnaddr}, @var{static_chain}) | |
3909 | A C statement to initialize the variable parts of a trampoline. | |
3910 | @var{addr} is an RTX for the address of the trampoline; @var{fnaddr} is | |
3911 | an RTX for the address of the nested function; @var{static_chain} is an | |
3912 | RTX for the static chain value that should be passed to the function | |
3913 | when it is called. | |
3914 | ||
3915 | @findex ALLOCATE_TRAMPOLINE | |
3916 | @item ALLOCATE_TRAMPOLINE (@var{fp}) | |
3917 | A C expression to allocate run-time space for a trampoline. The | |
3918 | expression value should be an RTX representing a memory reference to the | |
3919 | space for the trampoline. | |
3920 | ||
3921 | @cindex @code{FUNCTION_EPILOGUE} and trampolines | |
3922 | @cindex @code{FUNCTION_PROLOGUE} and trampolines | |
3923 | If this macro is not defined, by default the trampoline is allocated as | |
3924 | a stack slot. This default is right for most machines. The exceptions | |
3925 | are machines where it is impossible to execute instructions in the stack | |
3926 | area. On such machines, you may have to implement a separate stack, | |
3927 | using this macro in conjunction with @code{FUNCTION_PROLOGUE} and | |
3928 | @code{FUNCTION_EPILOGUE}. | |
3929 | ||
3930 | @var{fp} points to a data structure, a @code{struct function}, which | |
3931 | describes the compilation status of the immediate containing function of | |
3932 | the function which the trampoline is for. Normally (when | |
3933 | @code{ALLOCATE_TRAMPOLINE} is not defined), the stack slot for the | |
3934 | trampoline is in the stack frame of this containing function. Other | |
3935 | allocation strategies probably must do something analogous with this | |
3936 | information. | |
3937 | @end table | |
3938 | ||
3939 | Implementing trampolines is difficult on many machines because they have | |
3940 | separate instruction and data caches. Writing into a stack location | |
3941 | fails to clear the memory in the instruction cache, so when the program | |
3942 | jumps to that location, it executes the old contents. | |
3943 | ||
3944 | Here are two possible solutions. One is to clear the relevant parts of | |
3945 | the instruction cache whenever a trampoline is set up. The other is to | |
3946 | make all trampolines identical, by having them jump to a standard | |
3947 | subroutine. The former technique makes trampoline execution faster; the | |
3948 | latter makes initialization faster. | |
3949 | ||
3950 | To clear the instruction cache when a trampoline is initialized, define | |
3951 | the following macros which describe the shape of the cache. | |
3952 | ||
3953 | @table @code | |
3954 | @findex INSN_CACHE_SIZE | |
3955 | @item INSN_CACHE_SIZE | |
3956 | The total size in bytes of the cache. | |
3957 | ||
3958 | @findex INSN_CACHE_LINE_WIDTH | |
3959 | @item INSN_CACHE_LINE_WIDTH | |
3960 | The length in bytes of each cache line. The cache is divided into cache | |
3961 | lines which are disjoint slots, each holding a contiguous chunk of data | |
3962 | fetched from memory. Each time data is brought into the cache, an | |
3963 | entire line is read at once. The data loaded into a cache line is | |
3964 | always aligned on a boundary equal to the line size. | |
3965 | ||
3966 | @findex INSN_CACHE_DEPTH | |
3967 | @item INSN_CACHE_DEPTH | |
3968 | The number of alternative cache lines that can hold any particular memory | |
3969 | location. | |
3970 | @end table | |
3971 | ||
3972 | Alternatively, if the machine has system calls or instructions to clear | |
3973 | the instruction cache directly, you can define the following macro. | |
3974 | ||
3975 | @table @code | |
3976 | @findex CLEAR_INSN_CACHE | |
3977 | @item CLEAR_INSN_CACHE (@var{BEG}, @var{END}) | |
3978 | If defined, expands to a C expression clearing the @emph{instruction | |
3979 | cache} in the specified interval. If it is not defined, and the macro | |
3980 | INSN_CACHE_SIZE is defined, some generic code is generated to clear the | |
3981 | cache. The definition of this macro would typically be a series of | |
3982 | @code{asm} statements. Both @var{BEG} and @var{END} are both pointer | |
3983 | expressions. | |
3984 | @end table | |
3985 | ||
3986 | To use a standard subroutine, define the following macro. In addition, | |
3987 | you must make sure that the instructions in a trampoline fill an entire | |
3988 | cache line with identical instructions, or else ensure that the | |
3989 | beginning of the trampoline code is always aligned at the same point in | |
3990 | its cache line. Look in @file{m68k.h} as a guide. | |
3991 | ||
3992 | @table @code | |
3993 | @findex TRANSFER_FROM_TRAMPOLINE | |
3994 | @item TRANSFER_FROM_TRAMPOLINE | |
3995 | Define this macro if trampolines need a special subroutine to do their | |
3996 | work. The macro should expand to a series of @code{asm} statements | |
a3a15b4d | 3997 | which will be compiled with GCC. They go in a library function named |
feca2ed3 JW |
3998 | @code{__transfer_from_trampoline}. |
3999 | ||
4000 | If you need to avoid executing the ordinary prologue code of a compiled | |
4001 | C function when you jump to the subroutine, you can do so by placing a | |
4002 | special label of your own in the assembler code. Use one @code{asm} | |
4003 | statement to generate an assembler label, and another to make the label | |
4004 | global. Then trampolines can use that label to jump directly to your | |
4005 | special assembler code. | |
4006 | @end table | |
4007 | ||
4008 | @node Library Calls | |
4009 | @section Implicit Calls to Library Routines | |
4010 | @cindex library subroutine names | |
4011 | @cindex @file{libgcc.a} | |
4012 | ||
4013 | @c prevent bad page break with this line | |
4014 | Here is an explanation of implicit calls to library routines. | |
4015 | ||
4016 | @table @code | |
4017 | @findex MULSI3_LIBCALL | |
4018 | @item MULSI3_LIBCALL | |
4019 | A C string constant giving the name of the function to call for | |
4020 | multiplication of one signed full-word by another. If you do not | |
4021 | define this macro, the default name is used, which is @code{__mulsi3}, | |
4022 | a function defined in @file{libgcc.a}. | |
4023 | ||
4024 | @findex DIVSI3_LIBCALL | |
4025 | @item DIVSI3_LIBCALL | |
4026 | A C string constant giving the name of the function to call for | |
4027 | division of one signed full-word by another. If you do not define | |
4028 | this macro, the default name is used, which is @code{__divsi3}, a | |
4029 | function defined in @file{libgcc.a}. | |
4030 | ||
4031 | @findex UDIVSI3_LIBCALL | |
4032 | @item UDIVSI3_LIBCALL | |
4033 | A C string constant giving the name of the function to call for | |
4034 | division of one unsigned full-word by another. If you do not define | |
4035 | this macro, the default name is used, which is @code{__udivsi3}, a | |
4036 | function defined in @file{libgcc.a}. | |
4037 | ||
4038 | @findex MODSI3_LIBCALL | |
4039 | @item MODSI3_LIBCALL | |
4040 | A C string constant giving the name of the function to call for the | |
4041 | remainder in division of one signed full-word by another. If you do | |
4042 | not define this macro, the default name is used, which is | |
4043 | @code{__modsi3}, a function defined in @file{libgcc.a}. | |
4044 | ||
4045 | @findex UMODSI3_LIBCALL | |
4046 | @item UMODSI3_LIBCALL | |
4047 | A C string constant giving the name of the function to call for the | |
4048 | remainder in division of one unsigned full-word by another. If you do | |
4049 | not define this macro, the default name is used, which is | |
4050 | @code{__umodsi3}, a function defined in @file{libgcc.a}. | |
4051 | ||
4052 | @findex MULDI3_LIBCALL | |
4053 | @item MULDI3_LIBCALL | |
4054 | A C string constant giving the name of the function to call for | |
4055 | multiplication of one signed double-word by another. If you do not | |
4056 | define this macro, the default name is used, which is @code{__muldi3}, | |
4057 | a function defined in @file{libgcc.a}. | |
4058 | ||
4059 | @findex DIVDI3_LIBCALL | |
4060 | @item DIVDI3_LIBCALL | |
4061 | A C string constant giving the name of the function to call for | |
4062 | division of one signed double-word by another. If you do not define | |
4063 | this macro, the default name is used, which is @code{__divdi3}, a | |
4064 | function defined in @file{libgcc.a}. | |
4065 | ||
4066 | @findex UDIVDI3_LIBCALL | |
4067 | @item UDIVDI3_LIBCALL | |
4068 | A C string constant giving the name of the function to call for | |
4069 | division of one unsigned full-word by another. If you do not define | |
4070 | this macro, the default name is used, which is @code{__udivdi3}, a | |
4071 | function defined in @file{libgcc.a}. | |
4072 | ||
4073 | @findex MODDI3_LIBCALL | |
4074 | @item MODDI3_LIBCALL | |
4075 | A C string constant giving the name of the function to call for the | |
4076 | remainder in division of one signed double-word by another. If you do | |
4077 | not define this macro, the default name is used, which is | |
4078 | @code{__moddi3}, a function defined in @file{libgcc.a}. | |
4079 | ||
4080 | @findex UMODDI3_LIBCALL | |
4081 | @item UMODDI3_LIBCALL | |
4082 | A C string constant giving the name of the function to call for the | |
4083 | remainder in division of one unsigned full-word by another. If you do | |
4084 | not define this macro, the default name is used, which is | |
4085 | @code{__umoddi3}, a function defined in @file{libgcc.a}. | |
4086 | ||
4087 | @findex INIT_TARGET_OPTABS | |
4088 | @item INIT_TARGET_OPTABS | |
4089 | Define this macro as a C statement that declares additional library | |
4090 | routines renames existing ones. @code{init_optabs} calls this macro after | |
4091 | initializing all the normal library routines. | |
4092 | ||
c5c60e15 BS |
4093 | @findex FLOAT_LIB_COMPARE_RETURNS_BOOL (@var{mode}, @var{comparison}) |
4094 | @item FLOAT_LIB_COMPARE_RETURNS_BOOL | |
4095 | Define this macro as a C statement that returns nonzero if a call to | |
4096 | the floating point comparison library function will return a boolean | |
4097 | value that indicates the result of the comparison. It should return | |
4098 | zero if one of gcc's own libgcc functions is called. | |
4099 | ||
4100 | Most ports don't need to define this macro. | |
4101 | ||
feca2ed3 JW |
4102 | @findex TARGET_EDOM |
4103 | @cindex @code{EDOM}, implicit usage | |
4104 | @item TARGET_EDOM | |
4105 | The value of @code{EDOM} on the target machine, as a C integer constant | |
a3a15b4d | 4106 | expression. If you don't define this macro, GCC does not attempt to |
feca2ed3 JW |
4107 | deposit the value of @code{EDOM} into @code{errno} directly. Look in |
4108 | @file{/usr/include/errno.h} to find the value of @code{EDOM} on your | |
4109 | system. | |
4110 | ||
4111 | If you do not define @code{TARGET_EDOM}, then compiled code reports | |
4112 | domain errors by calling the library function and letting it report the | |
4113 | error. If mathematical functions on your system use @code{matherr} when | |
4114 | there is an error, then you should leave @code{TARGET_EDOM} undefined so | |
4115 | that @code{matherr} is used normally. | |
4116 | ||
4117 | @findex GEN_ERRNO_RTX | |
4118 | @cindex @code{errno}, implicit usage | |
4119 | @item GEN_ERRNO_RTX | |
4120 | Define this macro as a C expression to create an rtl expression that | |
4121 | refers to the global ``variable'' @code{errno}. (On certain systems, | |
4122 | @code{errno} may not actually be a variable.) If you don't define this | |
4123 | macro, a reasonable default is used. | |
4124 | ||
4125 | @findex TARGET_MEM_FUNCTIONS | |
4126 | @cindex @code{bcopy}, implicit usage | |
4127 | @cindex @code{memcpy}, implicit usage | |
4128 | @cindex @code{bzero}, implicit usage | |
4129 | @cindex @code{memset}, implicit usage | |
4130 | @item TARGET_MEM_FUNCTIONS | |
a3a15b4d | 4131 | Define this macro if GCC should generate calls to the System V |
feca2ed3 JW |
4132 | (and ANSI C) library functions @code{memcpy} and @code{memset} |
4133 | rather than the BSD functions @code{bcopy} and @code{bzero}. | |
4134 | ||
4135 | @findex LIBGCC_NEEDS_DOUBLE | |
4136 | @item LIBGCC_NEEDS_DOUBLE | |
4137 | Define this macro if only @code{float} arguments cannot be passed to | |
4138 | library routines (so they must be converted to @code{double}). This | |
4139 | macro affects both how library calls are generated and how the library | |
4140 | routines in @file{libgcc1.c} accept their arguments. It is useful on | |
4141 | machines where floating and fixed point arguments are passed | |
4142 | differently, such as the i860. | |
4143 | ||
4144 | @findex FLOAT_ARG_TYPE | |
4145 | @item FLOAT_ARG_TYPE | |
4146 | Define this macro to override the type used by the library routines to | |
4147 | pick up arguments of type @code{float}. (By default, they use a union | |
4148 | of @code{float} and @code{int}.) | |
4149 | ||
4150 | The obvious choice would be @code{float}---but that won't work with | |
4151 | traditional C compilers that expect all arguments declared as @code{float} | |
4152 | to arrive as @code{double}. To avoid this conversion, the library routines | |
4153 | ask for the value as some other type and then treat it as a @code{float}. | |
4154 | ||
4155 | On some systems, no other type will work for this. For these systems, | |
4156 | you must use @code{LIBGCC_NEEDS_DOUBLE} instead, to force conversion of | |
4157 | the values @code{double} before they are passed. | |
4158 | ||
4159 | @findex FLOATIFY | |
4160 | @item FLOATIFY (@var{passed-value}) | |
4161 | Define this macro to override the way library routines redesignate a | |
4162 | @code{float} argument as a @code{float} instead of the type it was | |
4163 | passed as. The default is an expression which takes the @code{float} | |
4164 | field of the union. | |
4165 | ||
4166 | @findex FLOAT_VALUE_TYPE | |
4167 | @item FLOAT_VALUE_TYPE | |
4168 | Define this macro to override the type used by the library routines to | |
4169 | return values that ought to have type @code{float}. (By default, they | |
4170 | use @code{int}.) | |
4171 | ||
4172 | The obvious choice would be @code{float}---but that won't work with | |
4173 | traditional C compilers gratuitously convert values declared as | |
4174 | @code{float} into @code{double}. | |
4175 | ||
4176 | @findex INTIFY | |
4177 | @item INTIFY (@var{float-value}) | |
4178 | Define this macro to override the way the value of a | |
4179 | @code{float}-returning library routine should be packaged in order to | |
4180 | return it. These functions are actually declared to return type | |
4181 | @code{FLOAT_VALUE_TYPE} (normally @code{int}). | |
4182 | ||
4183 | These values can't be returned as type @code{float} because traditional | |
4184 | C compilers would gratuitously convert the value to a @code{double}. | |
4185 | ||
4186 | A local variable named @code{intify} is always available when the macro | |
4187 | @code{INTIFY} is used. It is a union of a @code{float} field named | |
4188 | @code{f} and a field named @code{i} whose type is | |
4189 | @code{FLOAT_VALUE_TYPE} or @code{int}. | |
4190 | ||
4191 | If you don't define this macro, the default definition works by copying | |
4192 | the value through that union. | |
4193 | ||
4194 | @findex nongcc_SI_type | |
4195 | @item nongcc_SI_type | |
4196 | Define this macro as the name of the data type corresponding to | |
4197 | @code{SImode} in the system's own C compiler. | |
4198 | ||
4199 | You need not define this macro if that type is @code{long int}, as it usually | |
4200 | is. | |
4201 | ||
4202 | @findex nongcc_word_type | |
4203 | @item nongcc_word_type | |
4204 | Define this macro as the name of the data type corresponding to the | |
4205 | word_mode in the system's own C compiler. | |
4206 | ||
4207 | You need not define this macro if that type is @code{long int}, as it usually | |
4208 | is. | |
4209 | ||
4210 | @findex perform_@dots{} | |
4211 | @item perform_@dots{} | |
4212 | Define these macros to supply explicit C statements to carry out various | |
4213 | arithmetic operations on types @code{float} and @code{double} in the | |
4214 | library routines in @file{libgcc1.c}. See that file for a full list | |
4215 | of these macros and their arguments. | |
4216 | ||
4217 | On most machines, you don't need to define any of these macros, because | |
4218 | the C compiler that comes with the system takes care of doing them. | |
4219 | ||
4220 | @findex NEXT_OBJC_RUNTIME | |
4221 | @item NEXT_OBJC_RUNTIME | |
4222 | Define this macro to generate code for Objective C message sending using | |
4223 | the calling convention of the NeXT system. This calling convention | |
4224 | involves passing the object, the selector and the method arguments all | |
4225 | at once to the method-lookup library function. | |
4226 | ||
4227 | The default calling convention passes just the object and the selector | |
4228 | to the lookup function, which returns a pointer to the method. | |
4229 | @end table | |
4230 | ||
4231 | @node Addressing Modes | |
4232 | @section Addressing Modes | |
4233 | @cindex addressing modes | |
4234 | ||
4235 | @c prevent bad page break with this line | |
4236 | This is about addressing modes. | |
4237 | ||
4238 | @table @code | |
4239 | @findex HAVE_POST_INCREMENT | |
4240 | @item HAVE_POST_INCREMENT | |
940da324 | 4241 | A C expression that is nonzero the machine supports post-increment addressing. |
feca2ed3 JW |
4242 | |
4243 | @findex HAVE_PRE_INCREMENT | |
4244 | @findex HAVE_POST_DECREMENT | |
4245 | @findex HAVE_PRE_DECREMENT | |
4246 | @item HAVE_PRE_INCREMENT | |
4247 | @itemx HAVE_POST_DECREMENT | |
4248 | @itemx HAVE_PRE_DECREMENT | |
4249 | Similar for other kinds of addressing. | |
4250 | ||
4251 | @findex CONSTANT_ADDRESS_P | |
4252 | @item CONSTANT_ADDRESS_P (@var{x}) | |
4253 | A C expression that is 1 if the RTX @var{x} is a constant which | |
4254 | is a valid address. On most machines, this can be defined as | |
4255 | @code{CONSTANT_P (@var{x})}, but a few machines are more restrictive | |
4256 | in which constant addresses are supported. | |
4257 | ||
4258 | @findex CONSTANT_P | |
4259 | @code{CONSTANT_P} accepts integer-values expressions whose values are | |
4260 | not explicitly known, such as @code{symbol_ref}, @code{label_ref}, and | |
4261 | @code{high} expressions and @code{const} arithmetic expressions, in | |
4262 | addition to @code{const_int} and @code{const_double} expressions. | |
4263 | ||
4264 | @findex MAX_REGS_PER_ADDRESS | |
4265 | @item MAX_REGS_PER_ADDRESS | |
4266 | A number, the maximum number of registers that can appear in a valid | |
4267 | memory address. Note that it is up to you to specify a value equal to | |
4268 | the maximum number that @code{GO_IF_LEGITIMATE_ADDRESS} would ever | |
4269 | accept. | |
4270 | ||
4271 | @findex GO_IF_LEGITIMATE_ADDRESS | |
4272 | @item GO_IF_LEGITIMATE_ADDRESS (@var{mode}, @var{x}, @var{label}) | |
4273 | A C compound statement with a conditional @code{goto @var{label};} | |
4274 | executed if @var{x} (an RTX) is a legitimate memory address on the | |
4275 | target machine for a memory operand of mode @var{mode}. | |
4276 | ||
4277 | It usually pays to define several simpler macros to serve as | |
4278 | subroutines for this one. Otherwise it may be too complicated to | |
4279 | understand. | |
4280 | ||
4281 | This macro must exist in two variants: a strict variant and a | |
4282 | non-strict one. The strict variant is used in the reload pass. It | |
4283 | must be defined so that any pseudo-register that has not been | |
4284 | allocated a hard register is considered a memory reference. In | |
4285 | contexts where some kind of register is required, a pseudo-register | |
4286 | with no hard register must be rejected. | |
4287 | ||
4288 | The non-strict variant is used in other passes. It must be defined to | |
4289 | accept all pseudo-registers in every context where some kind of | |
4290 | register is required. | |
4291 | ||
4292 | @findex REG_OK_STRICT | |
4293 | Compiler source files that want to use the strict variant of this | |
4294 | macro define the macro @code{REG_OK_STRICT}. You should use an | |
4295 | @code{#ifdef REG_OK_STRICT} conditional to define the strict variant | |
4296 | in that case and the non-strict variant otherwise. | |
4297 | ||
4298 | Subroutines to check for acceptable registers for various purposes (one | |
4299 | for base registers, one for index registers, and so on) are typically | |
4300 | among the subroutines used to define @code{GO_IF_LEGITIMATE_ADDRESS}. | |
4301 | Then only these subroutine macros need have two variants; the higher | |
4302 | levels of macros may be the same whether strict or not.@refill | |
4303 | ||
4304 | Normally, constant addresses which are the sum of a @code{symbol_ref} | |
4305 | and an integer are stored inside a @code{const} RTX to mark them as | |
4306 | constant. Therefore, there is no need to recognize such sums | |
4307 | specifically as legitimate addresses. Normally you would simply | |
4308 | recognize any @code{const} as legitimate. | |
4309 | ||
4310 | Usually @code{PRINT_OPERAND_ADDRESS} is not prepared to handle constant | |
4311 | sums that are not marked with @code{const}. It assumes that a naked | |
4312 | @code{plus} indicates indexing. If so, then you @emph{must} reject such | |
4313 | naked constant sums as illegitimate addresses, so that none of them will | |
4314 | be given to @code{PRINT_OPERAND_ADDRESS}. | |
4315 | ||
4316 | @cindex @code{ENCODE_SECTION_INFO} and address validation | |
4317 | On some machines, whether a symbolic address is legitimate depends on | |
4318 | the section that the address refers to. On these machines, define the | |
4319 | macro @code{ENCODE_SECTION_INFO} to store the information into the | |
4320 | @code{symbol_ref}, and then check for it here. When you see a | |
4321 | @code{const}, you will have to look inside it to find the | |
4322 | @code{symbol_ref} in order to determine the section. @xref{Assembler | |
4323 | Format}. | |
4324 | ||
4325 | @findex saveable_obstack | |
4326 | The best way to modify the name string is by adding text to the | |
4327 | beginning, with suitable punctuation to prevent any ambiguity. Allocate | |
4328 | the new name in @code{saveable_obstack}. You will have to modify | |
4329 | @code{ASM_OUTPUT_LABELREF} to remove and decode the added text and | |
4330 | output the name accordingly, and define @code{STRIP_NAME_ENCODING} to | |
4331 | access the original name string. | |
4332 | ||
4333 | You can check the information stored here into the @code{symbol_ref} in | |
4334 | the definitions of the macros @code{GO_IF_LEGITIMATE_ADDRESS} and | |
4335 | @code{PRINT_OPERAND_ADDRESS}. | |
4336 | ||
4337 | @findex REG_OK_FOR_BASE_P | |
4338 | @item REG_OK_FOR_BASE_P (@var{x}) | |
4339 | A C expression that is nonzero if @var{x} (assumed to be a @code{reg} | |
4340 | RTX) is valid for use as a base register. For hard registers, it | |
4341 | should always accept those which the hardware permits and reject the | |
4342 | others. Whether the macro accepts or rejects pseudo registers must be | |
4343 | controlled by @code{REG_OK_STRICT} as described above. This usually | |
4344 | requires two variant definitions, of which @code{REG_OK_STRICT} | |
4345 | controls the one actually used. | |
4346 | ||
861bb6c1 JL |
4347 | @findex REG_MODE_OK_FOR_BASE_P |
4348 | @item REG_MODE_OK_FOR_BASE_P (@var{x}, @var{mode}) | |
4349 | A C expression that is just like @code{REG_OK_FOR_BASE_P}, except that | |
4350 | that expression may examine the mode of the memory reference in | |
4351 | @var{mode}. You should define this macro if the mode of the memory | |
4352 | reference affects whether a register may be used as a base register. If | |
4353 | you define this macro, the compiler will use it instead of | |
4354 | @code{REG_OK_FOR_BASE_P}. | |
4355 | ||
feca2ed3 JW |
4356 | @findex REG_OK_FOR_INDEX_P |
4357 | @item REG_OK_FOR_INDEX_P (@var{x}) | |
4358 | A C expression that is nonzero if @var{x} (assumed to be a @code{reg} | |
4359 | RTX) is valid for use as an index register. | |
4360 | ||
4361 | The difference between an index register and a base register is that | |
4362 | the index register may be scaled. If an address involves the sum of | |
4363 | two registers, neither one of them scaled, then either one may be | |
4364 | labeled the ``base'' and the other the ``index''; but whichever | |
4365 | labeling is used must fit the machine's constraints of which registers | |
4366 | may serve in each capacity. The compiler will try both labelings, | |
4367 | looking for one that is valid, and will reload one or both registers | |
4368 | only if neither labeling works. | |
4369 | ||
4370 | @findex LEGITIMIZE_ADDRESS | |
4371 | @item LEGITIMIZE_ADDRESS (@var{x}, @var{oldx}, @var{mode}, @var{win}) | |
4372 | A C compound statement that attempts to replace @var{x} with a valid | |
4373 | memory address for an operand of mode @var{mode}. @var{win} will be a | |
4374 | C statement label elsewhere in the code; the macro definition may use | |
4375 | ||
4376 | @example | |
4377 | GO_IF_LEGITIMATE_ADDRESS (@var{mode}, @var{x}, @var{win}); | |
4378 | @end example | |
4379 | ||
4380 | @noindent | |
4381 | to avoid further processing if the address has become legitimate. | |
4382 | ||
4383 | @findex break_out_memory_refs | |
4384 | @var{x} will always be the result of a call to @code{break_out_memory_refs}, | |
4385 | and @var{oldx} will be the operand that was given to that function to produce | |
4386 | @var{x}. | |
4387 | ||
4388 | The code generated by this macro should not alter the substructure of | |
4389 | @var{x}. If it transforms @var{x} into a more legitimate form, it | |
4390 | should assign @var{x} (which will always be a C variable) a new value. | |
4391 | ||
4392 | It is not necessary for this macro to come up with a legitimate | |
4393 | address. The compiler has standard ways of doing so in all cases. In | |
4394 | fact, it is safe for this macro to do nothing. But often a | |
4395 | machine-dependent strategy can generate better code. | |
4396 | ||
a9a2595b JR |
4397 | @findex LEGITIMIZE_RELOAD_ADDRESS |
4398 | @item LEGITIMIZE_RELOAD_ADDRESS (@var{x}, @var{mode}, @var{opnum}, @var{type}, @var{ind_levels}, @var{win}) | |
4399 | A C compound statement that attempts to replace @var{x}, which is an address | |
4400 | that needs reloading, with a valid memory address for an operand of mode | |
4401 | @var{mode}. @var{win} will be a C statement label elsewhere in the code. | |
4402 | It is not necessary to define this macro, but it might be useful for | |
4403 | performance reasons. | |
4404 | ||
4405 | For example, on the i386, it is sometimes possible to use a single | |
4406 | reload register instead of two by reloading a sum of two pseudo | |
4407 | registers into a register. On the other hand, for number of RISC | |
4408 | processors offsets are limited so that often an intermediate address | |
4409 | needs to be generated in order to address a stack slot. By defining | |
4410 | LEGITIMIZE_RELOAD_ADDRESS appropriately, the intermediate addresses | |
4411 | generated for adjacent some stack slots can be made identical, and thus | |
4412 | be shared. | |
4413 | ||
39bdfaa0 RH |
4414 | @emph{Note}: This macro should be used with caution. It is necessary |
4415 | to know something of how reload works in order to effectively use this, | |
4416 | and it is quite easy to produce macros that build in too much knowledge | |
4417 | of reload internals. | |
a9a2595b | 4418 | |
5f0c590d JL |
4419 | @emph{Note}: This macro must be able to reload an address created by a |
4420 | previous invocation of this macro. If it fails to handle such addresses | |
4421 | then the compiler may generate incorrect code or abort. | |
4422 | ||
a9a2595b | 4423 | @findex push_reload |
39bdfaa0 RH |
4424 | The macro definition should use @code{push_reload} to indicate parts that |
4425 | need reloading; @var{opnum}, @var{type} and @var{ind_levels} are usually | |
4426 | suitable to be passed unaltered to @code{push_reload}. | |
a9a2595b | 4427 | |
39bdfaa0 | 4428 | The code generated by this macro must not alter the substructure of |
a9a2595b JR |
4429 | @var{x}. If it transforms @var{x} into a more legitimate form, it |
4430 | should assign @var{x} (which will always be a C variable) a new value. | |
4431 | This also applies to parts that you change indirectly by calling | |
4432 | @code{push_reload}. | |
4433 | ||
39bdfaa0 RH |
4434 | @findex strict_memory_address_p |
4435 | The macro definition may use @code{strict_memory_address_p} to test if | |
4436 | the address has become legitimate. | |
4437 | ||
a9a2595b JR |
4438 | @findex copy_rtx |
4439 | If you want to change only a part of @var{x}, one standard way of doing | |
4440 | this is to use @code{copy_rtx}. Note, however, that is unshares only a | |
4441 | single level of rtl. Thus, if the part to be changed is not at the | |
4442 | top level, you'll need to replace first the top leve | |
4443 | It is not necessary for this macro to come up with a legitimate | |
4444 | address; but often a machine-dependent strategy can generate better code. | |
4445 | ||
feca2ed3 JW |
4446 | @findex GO_IF_MODE_DEPENDENT_ADDRESS |
4447 | @item GO_IF_MODE_DEPENDENT_ADDRESS (@var{addr}, @var{label}) | |
4448 | A C statement or compound statement with a conditional @code{goto | |
4449 | @var{label};} executed if memory address @var{x} (an RTX) can have | |
4450 | different meanings depending on the machine mode of the memory | |
4451 | reference it is used for or if the address is valid for some modes | |
4452 | but not others. | |
4453 | ||
4454 | Autoincrement and autodecrement addresses typically have mode-dependent | |
4455 | effects because the amount of the increment or decrement is the size | |
4456 | of the operand being addressed. Some machines have other mode-dependent | |
4457 | addresses. Many RISC machines have no mode-dependent addresses. | |
4458 | ||
4459 | You may assume that @var{addr} is a valid address for the machine. | |
4460 | ||
4461 | @findex LEGITIMATE_CONSTANT_P | |
4462 | @item LEGITIMATE_CONSTANT_P (@var{x}) | |
4463 | A C expression that is nonzero if @var{x} is a legitimate constant for | |
4464 | an immediate operand on the target machine. You can assume that | |
4465 | @var{x} satisfies @code{CONSTANT_P}, so you need not check this. In fact, | |
4466 | @samp{1} is a suitable definition for this macro on machines where | |
4467 | anything @code{CONSTANT_P} is valid.@refill | |
4468 | @end table | |
4469 | ||
4470 | @node Condition Code | |
4471 | @section Condition Code Status | |
4472 | @cindex condition code status | |
4473 | ||
4474 | @c prevent bad page break with this line | |
4475 | This describes the condition code status. | |
4476 | ||
4477 | @findex cc_status | |
4478 | The file @file{conditions.h} defines a variable @code{cc_status} to | |
4479 | describe how the condition code was computed (in case the interpretation of | |
4480 | the condition code depends on the instruction that it was set by). This | |
4481 | variable contains the RTL expressions on which the condition code is | |
4482 | currently based, and several standard flags. | |
4483 | ||
4484 | Sometimes additional machine-specific flags must be defined in the machine | |
4485 | description header file. It can also add additional machine-specific | |
4486 | information by defining @code{CC_STATUS_MDEP}. | |
4487 | ||
4488 | @table @code | |
4489 | @findex CC_STATUS_MDEP | |
4490 | @item CC_STATUS_MDEP | |
4491 | C code for a data type which is used for declaring the @code{mdep} | |
4492 | component of @code{cc_status}. It defaults to @code{int}. | |
4493 | ||
4494 | This macro is not used on machines that do not use @code{cc0}. | |
4495 | ||
4496 | @findex CC_STATUS_MDEP_INIT | |
4497 | @item CC_STATUS_MDEP_INIT | |
4498 | A C expression to initialize the @code{mdep} field to ``empty''. | |
4499 | The default definition does nothing, since most machines don't use | |
4500 | the field anyway. If you want to use the field, you should probably | |
4501 | define this macro to initialize it. | |
4502 | ||
4503 | This macro is not used on machines that do not use @code{cc0}. | |
4504 | ||
4505 | @findex NOTICE_UPDATE_CC | |
4506 | @item NOTICE_UPDATE_CC (@var{exp}, @var{insn}) | |
4507 | A C compound statement to set the components of @code{cc_status} | |
4508 | appropriately for an insn @var{insn} whose body is @var{exp}. It is | |
4509 | this macro's responsibility to recognize insns that set the condition | |
4510 | code as a byproduct of other activity as well as those that explicitly | |
4511 | set @code{(cc0)}. | |
4512 | ||
4513 | This macro is not used on machines that do not use @code{cc0}. | |
4514 | ||
4515 | If there are insns that do not set the condition code but do alter | |
4516 | other machine registers, this macro must check to see whether they | |
4517 | invalidate the expressions that the condition code is recorded as | |
4518 | reflecting. For example, on the 68000, insns that store in address | |
4519 | registers do not set the condition code, which means that usually | |
4520 | @code{NOTICE_UPDATE_CC} can leave @code{cc_status} unaltered for such | |
4521 | insns. But suppose that the previous insn set the condition code | |
4522 | based on location @samp{a4@@(102)} and the current insn stores a new | |
4523 | value in @samp{a4}. Although the condition code is not changed by | |
4524 | this, it will no longer be true that it reflects the contents of | |
4525 | @samp{a4@@(102)}. Therefore, @code{NOTICE_UPDATE_CC} must alter | |
4526 | @code{cc_status} in this case to say that nothing is known about the | |
4527 | condition code value. | |
4528 | ||
4529 | The definition of @code{NOTICE_UPDATE_CC} must be prepared to deal | |
4530 | with the results of peephole optimization: insns whose patterns are | |
4531 | @code{parallel} RTXs containing various @code{reg}, @code{mem} or | |
4532 | constants which are just the operands. The RTL structure of these | |
4533 | insns is not sufficient to indicate what the insns actually do. What | |
4534 | @code{NOTICE_UPDATE_CC} should do when it sees one is just to run | |
4535 | @code{CC_STATUS_INIT}. | |
4536 | ||
4537 | A possible definition of @code{NOTICE_UPDATE_CC} is to call a function | |
4538 | that looks at an attribute (@pxref{Insn Attributes}) named, for example, | |
4539 | @samp{cc}. This avoids having detailed information about patterns in | |
4540 | two places, the @file{md} file and in @code{NOTICE_UPDATE_CC}. | |
4541 | ||
4542 | @findex EXTRA_CC_MODES | |
4543 | @item EXTRA_CC_MODES | |
aa0b4465 ZW |
4544 | A list of additional modes for condition code values in registers |
4545 | (@pxref{Jump Patterns}). This macro should expand to a sequence of | |
4546 | calls of the macro @code{CC} separated by white space. @code{CC} takes | |
4547 | two arguments. The first is the enumeration name of the mode, which | |
4548 | should begin with @samp{CC} and end with @samp{mode}. The second is a C | |
4549 | string giving the printable name of the mode; it should be the same as | |
4550 | the first argument, but with the trailing @samp{mode} removed. | |
feca2ed3 | 4551 | |
aa0b4465 | 4552 | You should only define this macro if additional modes are required. |
feca2ed3 | 4553 | |
aa0b4465 | 4554 | A sample definition of @code{EXTRA_CC_MODES} is: |
feca2ed3 | 4555 | @smallexample |
aa0b4465 ZW |
4556 | #define EXTRA_CC_MODES \ |
4557 | CC(CC_NOOVmode, "CC_NOOV") \ | |
4558 | CC(CCFPmode, "CCFP") \ | |
4559 | CC(CCFPEmode, "CCFPE") | |
feca2ed3 JW |
4560 | @end smallexample |
4561 | ||
feca2ed3 JW |
4562 | @findex SELECT_CC_MODE |
4563 | @item SELECT_CC_MODE (@var{op}, @var{x}, @var{y}) | |
4564 | Returns a mode from class @code{MODE_CC} to be used when comparison | |
4565 | operation code @var{op} is applied to rtx @var{x} and @var{y}. For | |
4566 | example, on the Sparc, @code{SELECT_CC_MODE} is defined as (see | |
4567 | @pxref{Jump Patterns} for a description of the reason for this | |
4568 | definition) | |
4569 | ||
4570 | @smallexample | |
4571 | #define SELECT_CC_MODE(OP,X,Y) \ | |
4572 | (GET_MODE_CLASS (GET_MODE (X)) == MODE_FLOAT \ | |
4573 | ? ((OP == EQ || OP == NE) ? CCFPmode : CCFPEmode) \ | |
4574 | : ((GET_CODE (X) == PLUS || GET_CODE (X) == MINUS \ | |
4575 | || GET_CODE (X) == NEG) \ | |
4576 | ? CC_NOOVmode : CCmode)) | |
4577 | @end smallexample | |
4578 | ||
4579 | You need not define this macro if @code{EXTRA_CC_MODES} is not defined. | |
4580 | ||
4581 | @findex CANONICALIZE_COMPARISON | |
4582 | @item CANONICALIZE_COMPARISON (@var{code}, @var{op0}, @var{op1}) | |
8760eaae | 4583 | On some machines not all possible comparisons are defined, but you can |
feca2ed3 JW |
4584 | convert an invalid comparison into a valid one. For example, the Alpha |
4585 | does not have a @code{GT} comparison, but you can use an @code{LT} | |
4586 | comparison instead and swap the order of the operands. | |
4587 | ||
4588 | On such machines, define this macro to be a C statement to do any | |
4589 | required conversions. @var{code} is the initial comparison code | |
4590 | and @var{op0} and @var{op1} are the left and right operands of the | |
4591 | comparison, respectively. You should modify @var{code}, @var{op0}, and | |
4592 | @var{op1} as required. | |
4593 | ||
a3a15b4d | 4594 | GCC will not assume that the comparison resulting from this macro is |
feca2ed3 JW |
4595 | valid but will see if the resulting insn matches a pattern in the |
4596 | @file{md} file. | |
4597 | ||
4598 | You need not define this macro if it would never change the comparison | |
4599 | code or operands. | |
4600 | ||
4601 | @findex REVERSIBLE_CC_MODE | |
4602 | @item REVERSIBLE_CC_MODE (@var{mode}) | |
4603 | A C expression whose value is one if it is always safe to reverse a | |
4604 | comparison whose mode is @var{mode}. If @code{SELECT_CC_MODE} | |
4605 | can ever return @var{mode} for a floating-point inequality comparison, | |
4606 | then @code{REVERSIBLE_CC_MODE (@var{mode})} must be zero. | |
4607 | ||
4608 | You need not define this macro if it would always returns zero or if the | |
4609 | floating-point format is anything other than @code{IEEE_FLOAT_FORMAT}. | |
4610 | For example, here is the definition used on the Sparc, where floating-point | |
4611 | inequality comparisons are always given @code{CCFPEmode}: | |
4612 | ||
4613 | @smallexample | |
4614 | #define REVERSIBLE_CC_MODE(MODE) ((MODE) != CCFPEmode) | |
4615 | @end smallexample | |
4616 | ||
4617 | @end table | |
4618 | ||
4619 | @node Costs | |
4620 | @section Describing Relative Costs of Operations | |
4621 | @cindex costs of instructions | |
4622 | @cindex relative costs | |
4623 | @cindex speed of instructions | |
4624 | ||
4625 | These macros let you describe the relative speed of various operations | |
4626 | on the target machine. | |
4627 | ||
4628 | @table @code | |
4629 | @findex CONST_COSTS | |
4630 | @item CONST_COSTS (@var{x}, @var{code}, @var{outer_code}) | |
4631 | A part of a C @code{switch} statement that describes the relative costs | |
4632 | of constant RTL expressions. It must contain @code{case} labels for | |
4633 | expression codes @code{const_int}, @code{const}, @code{symbol_ref}, | |
4634 | @code{label_ref} and @code{const_double}. Each case must ultimately | |
4635 | reach a @code{return} statement to return the relative cost of the use | |
4636 | of that kind of constant value in an expression. The cost may depend on | |
4637 | the precise value of the constant, which is available for examination in | |
4638 | @var{x}, and the rtx code of the expression in which it is contained, | |
4639 | found in @var{outer_code}. | |
4640 | ||
4641 | @var{code} is the expression code---redundant, since it can be | |
4642 | obtained with @code{GET_CODE (@var{x})}. | |
4643 | ||
4644 | @findex RTX_COSTS | |
4645 | @findex COSTS_N_INSNS | |
4646 | @item RTX_COSTS (@var{x}, @var{code}, @var{outer_code}) | |
4647 | Like @code{CONST_COSTS} but applies to nonconstant RTL expressions. | |
4648 | This can be used, for example, to indicate how costly a multiply | |
4649 | instruction is. In writing this macro, you can use the construct | |
4650 | @code{COSTS_N_INSNS (@var{n})} to specify a cost equal to @var{n} fast | |
4651 | instructions. @var{outer_code} is the code of the expression in which | |
4652 | @var{x} is contained. | |
4653 | ||
4654 | This macro is optional; do not define it if the default cost assumptions | |
4655 | are adequate for the target machine. | |
4656 | ||
8625fab5 KG |
4657 | @findex DEFAULT_RTX_COSTS |
4658 | @item DEFAULT_RTX_COSTS (@var{x}, @var{code}, @var{outer_code}) | |
4659 | This macro, if defined, is called for any case not handled by the | |
4660 | @code{RTX_COSTS} or @code{CONST_COSTS} macros. This eliminates the need | |
4661 | to put case labels into the macro, but the code, or any functions it | |
4662 | calls, must assume that the RTL in @var{x} could be of any type that has | |
4663 | not already been handled. The arguments are the same as for | |
4664 | @code{RTX_COSTS}, and the macro should execute a return statement giving | |
4665 | the cost of any RTL expressions that it can handle. The default cost | |
4666 | calculation is used for any RTL for which this macro does not return a | |
4667 | value. | |
4668 | ||
4669 | This macro is optional; do not define it if the default cost assumptions | |
4670 | are adequate for the target machine. | |
4671 | ||
feca2ed3 JW |
4672 | @findex ADDRESS_COST |
4673 | @item ADDRESS_COST (@var{address}) | |
4674 | An expression giving the cost of an addressing mode that contains | |
4675 | @var{address}. If not defined, the cost is computed from | |
4676 | the @var{address} expression and the @code{CONST_COSTS} values. | |
4677 | ||
4678 | For most CISC machines, the default cost is a good approximation of the | |
4679 | true cost of the addressing mode. However, on RISC machines, all | |
4680 | instructions normally have the same length and execution time. Hence | |
4681 | all addresses will have equal costs. | |
4682 | ||
4683 | In cases where more than one form of an address is known, the form with | |
4684 | the lowest cost will be used. If multiple forms have the same, lowest, | |
4685 | cost, the one that is the most complex will be used. | |
4686 | ||
4687 | For example, suppose an address that is equal to the sum of a register | |
4688 | and a constant is used twice in the same basic block. When this macro | |
4689 | is not defined, the address will be computed in a register and memory | |
4690 | references will be indirect through that register. On machines where | |
4691 | the cost of the addressing mode containing the sum is no higher than | |
4692 | that of a simple indirect reference, this will produce an additional | |
4693 | instruction and possibly require an additional register. Proper | |
4694 | specification of this macro eliminates this overhead for such machines. | |
4695 | ||
4696 | Similar use of this macro is made in strength reduction of loops. | |
4697 | ||
4698 | @var{address} need not be valid as an address. In such a case, the cost | |
4699 | is not relevant and can be any value; invalid addresses need not be | |
4700 | assigned a different cost. | |
4701 | ||
4702 | On machines where an address involving more than one register is as | |
4703 | cheap as an address computation involving only one register, defining | |
4704 | @code{ADDRESS_COST} to reflect this can cause two registers to be live | |
4705 | over a region of code where only one would have been if | |
4706 | @code{ADDRESS_COST} were not defined in that manner. This effect should | |
4707 | be considered in the definition of this macro. Equivalent costs should | |
4708 | probably only be given to addresses with different numbers of registers | |
4709 | on machines with lots of registers. | |
4710 | ||
4711 | This macro will normally either not be defined or be defined as a | |
4712 | constant. | |
4713 | ||
4714 | @findex REGISTER_MOVE_COST | |
4715 | @item REGISTER_MOVE_COST (@var{from}, @var{to}) | |
4716 | A C expression for the cost of moving data from a register in class | |
4717 | @var{from} to one in class @var{to}. The classes are expressed using | |
4718 | the enumeration values such as @code{GENERAL_REGS}. A value of 2 is the | |
4719 | default; other values are interpreted relative to that. | |
4720 | ||
4721 | It is not required that the cost always equal 2 when @var{from} is the | |
4722 | same as @var{to}; on some machines it is expensive to move between | |
4723 | registers if they are not general registers. | |
4724 | ||
4725 | If reload sees an insn consisting of a single @code{set} between two | |
4726 | hard registers, and if @code{REGISTER_MOVE_COST} applied to their | |
4727 | classes returns a value of 2, reload does not check to ensure that the | |
4728 | constraints of the insn are met. Setting a cost of other than 2 will | |
4729 | allow reload to verify that the constraints are met. You should do this | |
4730 | if the @samp{mov@var{m}} pattern's constraints do not allow such copying. | |
4731 | ||
4732 | @findex MEMORY_MOVE_COST | |
cbd5b9a2 KR |
4733 | @item MEMORY_MOVE_COST (@var{mode}, @var{class}, @var{in}) |
4734 | A C expression for the cost of moving data of mode @var{mode} between a | |
4735 | register of class @var{class} and memory; @var{in} is zero if the value | |
473fe49b KR |
4736 | is to be written to memory, non-zero if it is to be read in. This cost |
4737 | is relative to those in @code{REGISTER_MOVE_COST}. If moving between | |
4738 | registers and memory is more expensive than between two registers, you | |
4739 | should define this macro to express the relative cost. | |
4740 | ||
a3a15b4d | 4741 | If you do not define this macro, GCC uses a default cost of 4 plus |
38e01259 | 4742 | the cost of copying via a secondary reload register, if one is |
473fe49b KR |
4743 | needed. If your machine requires a secondary reload register to copy |
4744 | between memory and a register of @var{class} but the reload mechanism is | |
4745 | more complex than copying via an intermediate, define this macro to | |
4746 | reflect the actual cost of the move. | |
4747 | ||
a3a15b4d | 4748 | GCC defines the function @code{memory_move_secondary_cost} if |
473fe49b KR |
4749 | secondary reloads are needed. It computes the costs due to copying via |
4750 | a secondary register. If your machine copies from memory using a | |
4751 | secondary register in the conventional way but the default base value of | |
4752 | 4 is not correct for your machine, define this macro to add some other | |
4753 | value to the result of that function. The arguments to that function | |
4754 | are the same as to this macro. | |
cbd5b9a2 | 4755 | |
feca2ed3 JW |
4756 | @findex BRANCH_COST |
4757 | @item BRANCH_COST | |
4758 | A C expression for the cost of a branch instruction. A value of 1 is | |
4759 | the default; other values are interpreted relative to that. | |
4760 | @end table | |
4761 | ||
4762 | Here are additional macros which do not specify precise relative costs, | |
a3a15b4d | 4763 | but only that certain actions are more expensive than GCC would |
feca2ed3 JW |
4764 | ordinarily expect. |
4765 | ||
4766 | @table @code | |
4767 | @findex SLOW_BYTE_ACCESS | |
4768 | @item SLOW_BYTE_ACCESS | |
4769 | Define this macro as a C expression which is nonzero if accessing less | |
4770 | than a word of memory (i.e. a @code{char} or a @code{short}) is no | |
4771 | faster than accessing a word of memory, i.e., if such access | |
4772 | require more than one instruction or if there is no difference in cost | |
4773 | between byte and (aligned) word loads. | |
4774 | ||
4775 | When this macro is not defined, the compiler will access a field by | |
4776 | finding the smallest containing object; when it is defined, a fullword | |
4777 | load will be used if alignment permits. Unless bytes accesses are | |
4778 | faster than word accesses, using word accesses is preferable since it | |
4779 | may eliminate subsequent memory access if subsequent accesses occur to | |
4780 | other fields in the same word of the structure, but to different bytes. | |
4781 | ||
4782 | @findex SLOW_ZERO_EXTEND | |
4783 | @item SLOW_ZERO_EXTEND | |
4784 | Define this macro if zero-extension (of a @code{char} or @code{short} | |
4785 | to an @code{int}) can be done faster if the destination is a register | |
4786 | that is known to be zero. | |
4787 | ||
4788 | If you define this macro, you must have instruction patterns that | |
4789 | recognize RTL structures like this: | |
4790 | ||
4791 | @smallexample | |
4792 | (set (strict_low_part (subreg:QI (reg:SI @dots{}) 0)) @dots{}) | |
4793 | @end smallexample | |
4794 | ||
4795 | @noindent | |
4796 | and likewise for @code{HImode}. | |
4797 | ||
4798 | @findex SLOW_UNALIGNED_ACCESS | |
5fad8ebf DE |
4799 | @item SLOW_UNALIGNED_ACCESS (@var{mode}, @var{alignment}) |
4800 | Define this macro to be the value 1 if memory accesses described by the | |
4801 | @var{mode} and @var{alignment} parameters have a cost many times greater | |
4802 | than aligned accesses, for example if they are emulated in a trap | |
4803 | handler. | |
feca2ed3 JW |
4804 | |
4805 | When this macro is non-zero, the compiler will act as if | |
4806 | @code{STRICT_ALIGNMENT} were non-zero when generating code for block | |
4807 | moves. This can cause significantly more instructions to be produced. | |
4808 | Therefore, do not set this macro non-zero if unaligned accesses only add a | |
4809 | cycle or two to the time for a memory access. | |
4810 | ||
6be57663 DE |
4811 | If the value of this macro is always zero, it need not be defined. If |
4812 | this macro is defined, it should produce a non-zero value when | |
4813 | @code{STRICT_ALIGNMENT} is non-zero. | |
feca2ed3 JW |
4814 | |
4815 | @findex DONT_REDUCE_ADDR | |
4816 | @item DONT_REDUCE_ADDR | |
4817 | Define this macro to inhibit strength reduction of memory addresses. | |
4818 | (On some machines, such strength reduction seems to do harm rather | |
4819 | than good.) | |
4820 | ||
4821 | @findex MOVE_RATIO | |
4822 | @item MOVE_RATIO | |
9862dea9 | 4823 | The threshold of number of scalar memory-to-memory move insns, @emph{below} |
c5c76735 | 4824 | which a sequence of insns should be generated instead of a |
feca2ed3 JW |
4825 | string move insn or a library call. Increasing the value will always |
4826 | make code faster, but eventually incurs high cost in increased code size. | |
4827 | ||
c5c76735 JL |
4828 | Note that on machines where the corresponding move insn is a |
4829 | @code{define_expand} that emits a sequence of insns, this macro counts | |
4830 | the number of such sequences. | |
9862dea9 | 4831 | |
feca2ed3 JW |
4832 | If you don't define this, a reasonable default is used. |
4833 | ||
fbe1758d AM |
4834 | @findex MOVE_BY_PIECES_P |
4835 | @item MOVE_BY_PIECES_P (@var{size}, @var{alignment}) | |
4836 | A C expression used to determine whether @code{move_by_pieces} will be used to | |
4837 | copy a chunk of memory, or whether some other block move mechanism | |
6e01bd94 | 4838 | will be used. Defaults to 1 if @code{move_by_pieces_ninsns} returns less |
fbe1758d AM |
4839 | than @code{MOVE_RATIO}. |
4840 | ||
4841 | @findex MOVE_MAX_PIECES | |
4842 | @item MOVE_MAX_PIECES | |
4843 | A C expression used by @code{move_by_pieces} to determine the largest unit | |
6e01bd94 | 4844 | a load or store used to copy memory is. Defaults to @code{MOVE_MAX}. |
fbe1758d AM |
4845 | |
4846 | @findex USE_LOAD_POST_INCREMENT | |
4847 | @item USE_LOAD_POST_INCREMENT (@var{mode}) | |
6e01bd94 MH |
4848 | A C expression used to determine whether a load postincrement is a good |
4849 | thing to use for a given mode. Defaults to the value of | |
4850 | @code{HAVE_POST_INCREMENT}. | |
4851 | ||
4852 | @findex USE_LOAD_POST_DECREMENT | |
4853 | @item USE_LOAD_POST_DECREMENT (@var{mode}) | |
4854 | A C expression used to determine whether a load postdecrement is a good | |
4855 | thing to use for a given mode. Defaults to the value of | |
4856 | @code{HAVE_POST_DECREMENT}. | |
fbe1758d AM |
4857 | |
4858 | @findex USE_LOAD_PRE_INCREMENT | |
4859 | @item USE_LOAD_PRE_INCREMENT (@var{mode}) | |
6e01bd94 MH |
4860 | A C expression used to determine whether a load preincrement is a good |
4861 | thing to use for a given mode. Defaults to the value of | |
4862 | @code{HAVE_PRE_INCREMENT}. | |
4863 | ||
4864 | @findex USE_LOAD_PRE_DECREMENT | |
4865 | @item USE_LOAD_PRE_DECREMENT (@var{mode}) | |
4866 | A C expression used to determine whether a load predecrement is a good | |
4867 | thing to use for a given mode. Defaults to the value of | |
4868 | @code{HAVE_PRE_DECREMENT}. | |
fbe1758d AM |
4869 | |
4870 | @findex USE_STORE_POST_INCREMENT | |
4871 | @item USE_STORE_POST_INCREMENT (@var{mode}) | |
6e01bd94 MH |
4872 | A C expression used to determine whether a store postincrement is a good |
4873 | thing to use for a given mode. Defaults to the value of | |
4874 | @code{HAVE_POST_INCREMENT}. | |
4875 | ||
4876 | @findex USE_STORE_POST_DECREMENT | |
4877 | @item USE_STORE_POST_DECREMENT (@var{mode}) | |
4878 | A C expression used to determine whether a store postdeccrement is a good | |
4879 | thing to use for a given mode. Defaults to the value of | |
4880 | @code{HAVE_POST_DECREMENT}. | |
fbe1758d AM |
4881 | |
4882 | @findex USE_STORE_PRE_INCREMENT | |
4883 | @item USE_STORE_PRE_INCREMENT (@var{mode}) | |
6e01bd94 MH |
4884 | This macro is used to determine whether a store preincrement is a good |
4885 | thing to use for a given mode. Defaults to the value of | |
4886 | @code{HAVE_PRE_INCREMENT}. | |
4887 | ||
4888 | @findex USE_STORE_PRE_DECREMENT | |
4889 | @item USE_STORE_PRE_DECREMENT (@var{mode}) | |
4890 | This macro is used to determine whether a store predecrement is a good | |
4891 | thing to use for a given mode. Defaults to the value of | |
4892 | @code{HAVE_PRE_DECREMENT}. | |
fbe1758d | 4893 | |
feca2ed3 JW |
4894 | @findex NO_FUNCTION_CSE |
4895 | @item NO_FUNCTION_CSE | |
4896 | Define this macro if it is as good or better to call a constant | |
4897 | function address than to call an address kept in a register. | |
4898 | ||
4899 | @findex NO_RECURSIVE_FUNCTION_CSE | |
4900 | @item NO_RECURSIVE_FUNCTION_CSE | |
4901 | Define this macro if it is as good or better for a function to call | |
4902 | itself with an explicit address than to call an address kept in a | |
4903 | register. | |
4904 | ||
4905 | @findex ADJUST_COST | |
4906 | @item ADJUST_COST (@var{insn}, @var{link}, @var{dep_insn}, @var{cost}) | |
4907 | A C statement (sans semicolon) to update the integer variable @var{cost} | |
4908 | based on the relationship between @var{insn} that is dependent on | |
4909 | @var{dep_insn} through the dependence @var{link}. The default is to | |
4910 | make no adjustment to @var{cost}. This can be used for example to | |
4911 | specify to the scheduler that an output- or anti-dependence does not | |
4912 | incur the same cost as a data-dependence. | |
4913 | ||
4914 | @findex ADJUST_PRIORITY | |
4915 | @item ADJUST_PRIORITY (@var{insn}) | |
4916 | A C statement (sans semicolon) to update the integer scheduling | |
4917 | priority @code{INSN_PRIORITY(@var{insn})}. Reduce the priority | |
4918 | to execute the @var{insn} earlier, increase the priority to execute | |
4919 | @var{insn} later. Do not define this macro if you do not need to | |
4920 | adjust the scheduling priorities of insns. | |
4921 | @end table | |
4922 | ||
4923 | @node Sections | |
4924 | @section Dividing the Output into Sections (Texts, Data, @dots{}) | |
4925 | @c the above section title is WAY too long. maybe cut the part between | |
4926 | @c the (...)? --mew 10feb93 | |
4927 | ||
4928 | An object file is divided into sections containing different types of | |
4929 | data. In the most common case, there are three sections: the @dfn{text | |
4930 | section}, which holds instructions and read-only data; the @dfn{data | |
4931 | section}, which holds initialized writable data; and the @dfn{bss | |
4932 | section}, which holds uninitialized data. Some systems have other kinds | |
4933 | of sections. | |
4934 | ||
4935 | The compiler must tell the assembler when to switch sections. These | |
4936 | macros control what commands to output to tell the assembler this. You | |
4937 | can also define additional sections. | |
4938 | ||
4939 | @table @code | |
4940 | @findex TEXT_SECTION_ASM_OP | |
4941 | @item TEXT_SECTION_ASM_OP | |
4942 | A C expression whose value is a string containing the assembler | |
4943 | operation that should precede instructions and read-only data. Normally | |
4944 | @code{".text"} is right. | |
4945 | ||
4946 | @findex DATA_SECTION_ASM_OP | |
4947 | @item DATA_SECTION_ASM_OP | |
4948 | A C expression whose value is a string containing the assembler | |
4949 | operation to identify the following data as writable initialized data. | |
4950 | Normally @code{".data"} is right. | |
4951 | ||
4952 | @findex SHARED_SECTION_ASM_OP | |
4953 | @item SHARED_SECTION_ASM_OP | |
4954 | If defined, a C expression whose value is a string containing the | |
4955 | assembler operation to identify the following data as shared data. If | |
4956 | not defined, @code{DATA_SECTION_ASM_OP} will be used. | |
4957 | ||
4958 | @findex BSS_SECTION_ASM_OP | |
4959 | @item BSS_SECTION_ASM_OP | |
4960 | If defined, a C expression whose value is a string containing the | |
4961 | assembler operation to identify the following data as uninitialized global | |
4962 | data. If not defined, and neither @code{ASM_OUTPUT_BSS} nor | |
4963 | @code{ASM_OUTPUT_ALIGNED_BSS} are defined, uninitialized global data will be | |
4964 | output in the data section if @samp{-fno-common} is passed, otherwise | |
4965 | @code{ASM_OUTPUT_COMMON} will be used. | |
4966 | ||
4967 | @findex SHARED_BSS_SECTION_ASM_OP | |
4968 | @item SHARED_BSS_SECTION_ASM_OP | |
4969 | If defined, a C expression whose value is a string containing the | |
4970 | assembler operation to identify the following data as uninitialized global | |
4971 | shared data. If not defined, and @code{BSS_SECTION_ASM_OP} is, the latter | |
4972 | will be used. | |
4973 | ||
4974 | @findex INIT_SECTION_ASM_OP | |
4975 | @item INIT_SECTION_ASM_OP | |
4976 | If defined, a C expression whose value is a string containing the | |
4977 | assembler operation to identify the following data as initialization | |
a3a15b4d | 4978 | code. If not defined, GCC will assume such a section does not |
feca2ed3 JW |
4979 | exist. |
4980 | ||
4981 | @findex EXTRA_SECTIONS | |
4982 | @findex in_text | |
4983 | @findex in_data | |
4984 | @item EXTRA_SECTIONS | |
4985 | A list of names for sections other than the standard two, which are | |
4986 | @code{in_text} and @code{in_data}. You need not define this macro | |
4987 | on a system with no other sections (that GCC needs to use). | |
4988 | ||
4989 | @findex EXTRA_SECTION_FUNCTIONS | |
4990 | @findex text_section | |
4991 | @findex data_section | |
4992 | @item EXTRA_SECTION_FUNCTIONS | |
4993 | One or more functions to be defined in @file{varasm.c}. These | |
4994 | functions should do jobs analogous to those of @code{text_section} and | |
4995 | @code{data_section}, for your additional sections. Do not define this | |
4996 | macro if you do not define @code{EXTRA_SECTIONS}. | |
4997 | ||
4998 | @findex READONLY_DATA_SECTION | |
4999 | @item READONLY_DATA_SECTION | |
5000 | On most machines, read-only variables, constants, and jump tables are | |
5001 | placed in the text section. If this is not the case on your machine, | |
5002 | this macro should be defined to be the name of a function (either | |
5003 | @code{data_section} or a function defined in @code{EXTRA_SECTIONS}) that | |
5004 | switches to the section to be used for read-only items. | |
5005 | ||
5006 | If these items should be placed in the text section, this macro should | |
5007 | not be defined. | |
5008 | ||
5009 | @findex SELECT_SECTION | |
5010 | @item SELECT_SECTION (@var{exp}, @var{reloc}) | |
5011 | A C statement or statements to switch to the appropriate section for | |
5012 | output of @var{exp}. You can assume that @var{exp} is either a | |
5013 | @code{VAR_DECL} node or a constant of some sort. @var{reloc} | |
5014 | indicates whether the initial value of @var{exp} requires link-time | |
5015 | relocations. Select the section by calling @code{text_section} or one | |
5016 | of the alternatives for other sections. | |
5017 | ||
5018 | Do not define this macro if you put all read-only variables and | |
5019 | constants in the read-only data section (usually the text section). | |
5020 | ||
5021 | @findex SELECT_RTX_SECTION | |
5022 | @item SELECT_RTX_SECTION (@var{mode}, @var{rtx}) | |
5023 | A C statement or statements to switch to the appropriate section for | |
5024 | output of @var{rtx} in mode @var{mode}. You can assume that @var{rtx} | |
5025 | is some kind of constant in RTL. The argument @var{mode} is redundant | |
5026 | except in the case of a @code{const_int} rtx. Select the section by | |
5027 | calling @code{text_section} or one of the alternatives for other | |
5028 | sections. | |
5029 | ||
5030 | Do not define this macro if you put all constants in the read-only | |
5031 | data section. | |
5032 | ||
5033 | @findex JUMP_TABLES_IN_TEXT_SECTION | |
5034 | @item JUMP_TABLES_IN_TEXT_SECTION | |
75197b37 BS |
5035 | Define this macro to be an expression with a non-zero value if jump |
5036 | tables (for @code{tablejump} insns) should be output in the text | |
5037 | section, along with the assembler instructions. Otherwise, the | |
5038 | readonly data section is used. | |
feca2ed3 JW |
5039 | |
5040 | This macro is irrelevant if there is no separate readonly data section. | |
5041 | ||
5042 | @findex ENCODE_SECTION_INFO | |
5043 | @item ENCODE_SECTION_INFO (@var{decl}) | |
5044 | Define this macro if references to a symbol must be treated differently | |
5045 | depending on something about the variable or function named by the | |
5046 | symbol (such as what section it is in). | |
5047 | ||
5048 | The macro definition, if any, is executed immediately after the rtl for | |
5049 | @var{decl} has been created and stored in @code{DECL_RTL (@var{decl})}. | |
5050 | The value of the rtl will be a @code{mem} whose address is a | |
5051 | @code{symbol_ref}. | |
5052 | ||
5053 | @cindex @code{SYMBOL_REF_FLAG}, in @code{ENCODE_SECTION_INFO} | |
5054 | The usual thing for this macro to do is to record a flag in the | |
5055 | @code{symbol_ref} (such as @code{SYMBOL_REF_FLAG}) or to store a | |
5056 | modified name string in the @code{symbol_ref} (if one bit is not enough | |
5057 | information). | |
5058 | ||
5059 | @findex STRIP_NAME_ENCODING | |
5060 | @item STRIP_NAME_ENCODING (@var{var}, @var{sym_name}) | |
5061 | Decode @var{sym_name} and store the real name part in @var{var}, sans | |
5062 | the characters that encode section info. Define this macro if | |
5063 | @code{ENCODE_SECTION_INFO} alters the symbol's name string. | |
5064 | ||
e9a25f70 | 5065 | @findex UNIQUE_SECTION_P |
861bb6c1 JL |
5066 | @item UNIQUE_SECTION_P (@var{decl}) |
5067 | A C expression which evaluates to true if @var{decl} should be placed | |
5068 | into a unique section for some target-specific reason. If you do not | |
5069 | define this macro, the default is @samp{0}. Note that the flag | |
5070 | @samp{-ffunction-sections} will also cause functions to be placed into | |
5071 | unique sections. | |
5072 | ||
feca2ed3 | 5073 | @findex UNIQUE_SECTION |
861bb6c1 JL |
5074 | @item UNIQUE_SECTION (@var{decl}, @var{reloc}) |
5075 | A C statement to build up a unique section name, expressed as a | |
5076 | STRING_CST node, and assign it to @samp{DECL_SECTION_NAME (@var{decl})}. | |
5077 | @var{reloc} indicates whether the initial value of @var{exp} requires | |
a3a15b4d | 5078 | link-time relocations. If you do not define this macro, GCC will use |
a56e7c08 NC |
5079 | the symbol name prefixed by @samp{.} as the section name. Note - this |
5080 | macro can now be called for unitialised data items as well as | |
5081 | initialised data and functions. | |
feca2ed3 JW |
5082 | @end table |
5083 | ||
5084 | @node PIC | |
5085 | @section Position Independent Code | |
5086 | @cindex position independent code | |
5087 | @cindex PIC | |
5088 | ||
5089 | This section describes macros that help implement generation of position | |
5090 | independent code. Simply defining these macros is not enough to | |
5091 | generate valid PIC; you must also add support to the macros | |
5092 | @code{GO_IF_LEGITIMATE_ADDRESS} and @code{PRINT_OPERAND_ADDRESS}, as | |
5093 | well as @code{LEGITIMIZE_ADDRESS}. You must modify the definition of | |
5094 | @samp{movsi} to do something appropriate when the source operand | |
5095 | contains a symbolic address. You may also need to alter the handling of | |
5096 | switch statements so that they use relative addresses. | |
5097 | @c i rearranged the order of the macros above to try to force one of | |
5098 | @c them to the next line, to eliminate an overfull hbox. --mew 10feb93 | |
5099 | ||
5100 | @table @code | |
5101 | @findex PIC_OFFSET_TABLE_REGNUM | |
5102 | @item PIC_OFFSET_TABLE_REGNUM | |
5103 | The register number of the register used to address a table of static | |
5104 | data addresses in memory. In some cases this register is defined by a | |
5105 | processor's ``application binary interface'' (ABI). When this macro | |
5106 | is defined, RTL is generated for this register once, as with the stack | |
5107 | pointer and frame pointer registers. If this macro is not defined, it | |
5108 | is up to the machine-dependent files to allocate such a register (if | |
5109 | necessary). | |
5110 | ||
5111 | @findex PIC_OFFSET_TABLE_REG_CALL_CLOBBERED | |
5112 | @item PIC_OFFSET_TABLE_REG_CALL_CLOBBERED | |
5113 | Define this macro if the register defined by | |
5114 | @code{PIC_OFFSET_TABLE_REGNUM} is clobbered by calls. Do not define | |
ed4db1ee | 5115 | this macro if @code{PIC_OFFSET_TABLE_REGNUM} is not defined. |
feca2ed3 JW |
5116 | |
5117 | @findex FINALIZE_PIC | |
5118 | @item FINALIZE_PIC | |
5119 | By generating position-independent code, when two different programs (A | |
5120 | and B) share a common library (libC.a), the text of the library can be | |
5121 | shared whether or not the library is linked at the same address for both | |
5122 | programs. In some of these environments, position-independent code | |
5123 | requires not only the use of different addressing modes, but also | |
5124 | special code to enable the use of these addressing modes. | |
5125 | ||
5126 | The @code{FINALIZE_PIC} macro serves as a hook to emit these special | |
5127 | codes once the function is being compiled into assembly code, but not | |
5128 | before. (It is not done before, because in the case of compiling an | |
5129 | inline function, it would lead to multiple PIC prologues being | |
5130 | included in functions which used inline functions and were compiled to | |
5131 | assembly language.) | |
5132 | ||
5133 | @findex LEGITIMATE_PIC_OPERAND_P | |
5134 | @item LEGITIMATE_PIC_OPERAND_P (@var{x}) | |
5135 | A C expression that is nonzero if @var{x} is a legitimate immediate | |
5136 | operand on the target machine when generating position independent code. | |
5137 | You can assume that @var{x} satisfies @code{CONSTANT_P}, so you need not | |
5138 | check this. You can also assume @var{flag_pic} is true, so you need not | |
5139 | check it either. You need not define this macro if all constants | |
5140 | (including @code{SYMBOL_REF}) can be immediate operands when generating | |
5141 | position independent code. | |
5142 | @end table | |
5143 | ||
5144 | @node Assembler Format | |
5145 | @section Defining the Output Assembler Language | |
5146 | ||
5147 | This section describes macros whose principal purpose is to describe how | |
5148 | to write instructions in assembler language--rather than what the | |
5149 | instructions do. | |
5150 | ||
5151 | @menu | |
5152 | * File Framework:: Structural information for the assembler file. | |
5153 | * Data Output:: Output of constants (numbers, strings, addresses). | |
5154 | * Uninitialized Data:: Output of uninitialized variables. | |
5155 | * Label Output:: Output and generation of labels. | |
5156 | * Initialization:: General principles of initialization | |
5157 | and termination routines. | |
5158 | * Macros for Initialization:: | |
5159 | Specific macros that control the handling of | |
5160 | initialization and termination routines. | |
5161 | * Instruction Output:: Output of actual instructions. | |
5162 | * Dispatch Tables:: Output of jump tables. | |
5163 | * Exception Region Output:: Output of exception region code. | |
5164 | * Alignment Output:: Pseudo ops for alignment and skipping data. | |
5165 | @end menu | |
5166 | ||
5167 | @node File Framework | |
5168 | @subsection The Overall Framework of an Assembler File | |
5169 | @cindex assembler format | |
5170 | @cindex output of assembler code | |
5171 | ||
5172 | @c prevent bad page break with this line | |
5173 | This describes the overall framework of an assembler file. | |
5174 | ||
5175 | @table @code | |
5176 | @findex ASM_FILE_START | |
5177 | @item ASM_FILE_START (@var{stream}) | |
5178 | A C expression which outputs to the stdio stream @var{stream} | |
5179 | some appropriate text to go at the start of an assembler file. | |
5180 | ||
5181 | Normally this macro is defined to output a line containing | |
5182 | @samp{#NO_APP}, which is a comment that has no effect on most | |
5183 | assemblers but tells the GNU assembler that it can save time by not | |
5184 | checking for certain assembler constructs. | |
5185 | ||
5186 | On systems that use SDB, it is necessary to output certain commands; | |
5187 | see @file{attasm.h}. | |
5188 | ||
5189 | @findex ASM_FILE_END | |
5190 | @item ASM_FILE_END (@var{stream}) | |
5191 | A C expression which outputs to the stdio stream @var{stream} | |
5192 | some appropriate text to go at the end of an assembler file. | |
5193 | ||
5194 | If this macro is not defined, the default is to output nothing | |
5195 | special at the end of the file. Most systems don't require any | |
5196 | definition. | |
5197 | ||
5198 | On systems that use SDB, it is necessary to output certain commands; | |
5199 | see @file{attasm.h}. | |
5200 | ||
5201 | @findex ASM_IDENTIFY_GCC | |
5202 | @item ASM_IDENTIFY_GCC (@var{file}) | |
5203 | A C statement to output assembler commands which will identify | |
a3a15b4d | 5204 | the object file as having been compiled with GCC (or another |
feca2ed3 JW |
5205 | GNU compiler). |
5206 | ||
5207 | If you don't define this macro, the string @samp{gcc_compiled.:} | |
5208 | is output. This string is calculated to define a symbol which, | |
5209 | on BSD systems, will never be defined for any other reason. | |
5210 | GDB checks for the presence of this symbol when reading the | |
5211 | symbol table of an executable. | |
5212 | ||
5213 | On non-BSD systems, you must arrange communication with GDB in | |
5214 | some other fashion. If GDB is not used on your system, you can | |
5215 | define this macro with an empty body. | |
5216 | ||
5217 | @findex ASM_COMMENT_START | |
5218 | @item ASM_COMMENT_START | |
5219 | A C string constant describing how to begin a comment in the target | |
5220 | assembler language. The compiler assumes that the comment will end at | |
5221 | the end of the line. | |
5222 | ||
5223 | @findex ASM_APP_ON | |
5224 | @item ASM_APP_ON | |
5225 | A C string constant for text to be output before each @code{asm} | |
5226 | statement or group of consecutive ones. Normally this is | |
5227 | @code{"#APP"}, which is a comment that has no effect on most | |
5228 | assemblers but tells the GNU assembler that it must check the lines | |
5229 | that follow for all valid assembler constructs. | |
5230 | ||
5231 | @findex ASM_APP_OFF | |
5232 | @item ASM_APP_OFF | |
5233 | A C string constant for text to be output after each @code{asm} | |
5234 | statement or group of consecutive ones. Normally this is | |
5235 | @code{"#NO_APP"}, which tells the GNU assembler to resume making the | |
5236 | time-saving assumptions that are valid for ordinary compiler output. | |
5237 | ||
5238 | @findex ASM_OUTPUT_SOURCE_FILENAME | |
5239 | @item ASM_OUTPUT_SOURCE_FILENAME (@var{stream}, @var{name}) | |
5240 | A C statement to output COFF information or DWARF debugging information | |
5241 | which indicates that filename @var{name} is the current source file to | |
5242 | the stdio stream @var{stream}. | |
5243 | ||
5244 | This macro need not be defined if the standard form of output | |
5245 | for the file format in use is appropriate. | |
5246 | ||
e9a25f70 | 5247 | @findex OUTPUT_QUOTED_STRING |
8760eaae | 5248 | @item OUTPUT_QUOTED_STRING (@var{stream}, @var{string}) |
e9a25f70 JL |
5249 | A C statement to output the string @var{string} to the stdio stream |
5250 | @var{stream}. If you do not call the function @code{output_quoted_string} | |
a3a15b4d | 5251 | in your config files, GCC will only call it to output filenames to |
e9a25f70 JL |
5252 | the assembler source. So you can use it to canonicalize the format |
5253 | of the filename using this macro. | |
5254 | ||
feca2ed3 JW |
5255 | @findex ASM_OUTPUT_SOURCE_LINE |
5256 | @item ASM_OUTPUT_SOURCE_LINE (@var{stream}, @var{line}) | |
5257 | A C statement to output DBX or SDB debugging information before code | |
5258 | for line number @var{line} of the current source file to the | |
5259 | stdio stream @var{stream}. | |
5260 | ||
5261 | This macro need not be defined if the standard form of debugging | |
5262 | information for the debugger in use is appropriate. | |
5263 | ||
5264 | @findex ASM_OUTPUT_IDENT | |
5265 | @item ASM_OUTPUT_IDENT (@var{stream}, @var{string}) | |
5266 | A C statement to output something to the assembler file to handle a | |
5267 | @samp{#ident} directive containing the text @var{string}. If this | |
5268 | macro is not defined, nothing is output for a @samp{#ident} directive. | |
5269 | ||
5270 | @findex ASM_OUTPUT_SECTION_NAME | |
861bb6c1 | 5271 | @item ASM_OUTPUT_SECTION_NAME (@var{stream}, @var{decl}, @var{name}, @var{reloc}) |
feca2ed3 JW |
5272 | A C statement to output something to the assembler file to switch to section |
5273 | @var{name} for object @var{decl} which is either a @code{FUNCTION_DECL}, a | |
861bb6c1 JL |
5274 | @code{VAR_DECL} or @code{NULL_TREE}. @var{reloc} |
5275 | indicates whether the initial value of @var{exp} requires link-time | |
5276 | relocations. Some target formats do not support | |
feca2ed3 JW |
5277 | arbitrary sections. Do not define this macro in such cases. |
5278 | ||
5279 | At present this macro is only used to support section attributes. | |
5280 | When this macro is undefined, section attributes are disabled. | |
5281 | ||
5282 | @findex OBJC_PROLOGUE | |
5283 | @item OBJC_PROLOGUE | |
5284 | A C statement to output any assembler statements which are required to | |
5285 | precede any Objective C object definitions or message sending. The | |
5286 | statement is executed only when compiling an Objective C program. | |
5287 | @end table | |
5288 | ||
5289 | @need 2000 | |
5290 | @node Data Output | |
5291 | @subsection Output of Data | |
5292 | ||
5293 | @c prevent bad page break with this line | |
5294 | This describes data output. | |
5295 | ||
5296 | @table @code | |
5297 | @findex ASM_OUTPUT_LONG_DOUBLE | |
5298 | @findex ASM_OUTPUT_DOUBLE | |
5299 | @findex ASM_OUTPUT_FLOAT | |
5300 | @item ASM_OUTPUT_LONG_DOUBLE (@var{stream}, @var{value}) | |
5301 | @itemx ASM_OUTPUT_DOUBLE (@var{stream}, @var{value}) | |
5302 | @itemx ASM_OUTPUT_FLOAT (@var{stream}, @var{value}) | |
5303 | @itemx ASM_OUTPUT_THREE_QUARTER_FLOAT (@var{stream}, @var{value}) | |
5304 | @itemx ASM_OUTPUT_SHORT_FLOAT (@var{stream}, @var{value}) | |
5305 | @itemx ASM_OUTPUT_BYTE_FLOAT (@var{stream}, @var{value}) | |
5306 | A C statement to output to the stdio stream @var{stream} an assembler | |
5307 | instruction to assemble a floating-point constant of @code{TFmode}, | |
5308 | @code{DFmode}, @code{SFmode}, @code{TQFmode}, @code{HFmode}, or | |
5309 | @code{QFmode}, respectively, whose value is @var{value}. @var{value} | |
5310 | will be a C expression of type @code{REAL_VALUE_TYPE}. Macros such as | |
5311 | @code{REAL_VALUE_TO_TARGET_DOUBLE} are useful for writing these | |
5312 | definitions. | |
5313 | ||
5314 | @findex ASM_OUTPUT_QUADRUPLE_INT | |
5315 | @findex ASM_OUTPUT_DOUBLE_INT | |
5316 | @findex ASM_OUTPUT_INT | |
5317 | @findex ASM_OUTPUT_SHORT | |
5318 | @findex ASM_OUTPUT_CHAR | |
5319 | @findex output_addr_const | |
5320 | @item ASM_OUTPUT_QUADRUPLE_INT (@var{stream}, @var{exp}) | |
5321 | @itemx ASM_OUTPUT_DOUBLE_INT (@var{stream}, @var{exp}) | |
5322 | @itemx ASM_OUTPUT_INT (@var{stream}, @var{exp}) | |
5323 | @itemx ASM_OUTPUT_SHORT (@var{stream}, @var{exp}) | |
5324 | @itemx ASM_OUTPUT_CHAR (@var{stream}, @var{exp}) | |
5325 | A C statement to output to the stdio stream @var{stream} an assembler | |
5326 | instruction to assemble an integer of 16, 8, 4, 2 or 1 bytes, | |
5327 | respectively, whose value is @var{value}. The argument @var{exp} will | |
5328 | be an RTL expression which represents a constant value. Use | |
5329 | @samp{output_addr_const (@var{stream}, @var{exp})} to output this value | |
5330 | as an assembler expression.@refill | |
5331 | ||
5332 | For sizes larger than @code{UNITS_PER_WORD}, if the action of a macro | |
5333 | would be identical to repeatedly calling the macro corresponding to | |
5334 | a size of @code{UNITS_PER_WORD}, once for each word, you need not define | |
5335 | the macro. | |
5336 | ||
5337 | @findex ASM_OUTPUT_BYTE | |
5338 | @item ASM_OUTPUT_BYTE (@var{stream}, @var{value}) | |
5339 | A C statement to output to the stdio stream @var{stream} an assembler | |
5340 | instruction to assemble a single byte containing the number @var{value}. | |
5341 | ||
5342 | @findex ASM_BYTE_OP | |
5343 | @item ASM_BYTE_OP | |
5344 | A C string constant giving the pseudo-op to use for a sequence of | |
5345 | single-byte constants. If this macro is not defined, the default is | |
5346 | @code{"byte"}. | |
5347 | ||
5348 | @findex ASM_OUTPUT_ASCII | |
5349 | @item ASM_OUTPUT_ASCII (@var{stream}, @var{ptr}, @var{len}) | |
5350 | A C statement to output to the stdio stream @var{stream} an assembler | |
5351 | instruction to assemble a string constant containing the @var{len} | |
5352 | bytes at @var{ptr}. @var{ptr} will be a C expression of type | |
5353 | @code{char *} and @var{len} a C expression of type @code{int}. | |
5354 | ||
5355 | If the assembler has a @code{.ascii} pseudo-op as found in the | |
5356 | Berkeley Unix assembler, do not define the macro | |
5357 | @code{ASM_OUTPUT_ASCII}. | |
5358 | ||
861bb6c1 JL |
5359 | @findex CONSTANT_POOL_BEFORE_FUNCTION |
5360 | @item CONSTANT_POOL_BEFORE_FUNCTION | |
5361 | You may define this macro as a C expression. You should define the | |
a3a15b4d | 5362 | expression to have a non-zero value if GCC should output the constant |
861bb6c1 | 5363 | pool for a function before the code for the function, or a zero value if |
a3a15b4d JL |
5364 | GCC should output the constant pool after the function. If you do |
5365 | not define this macro, the usual case, GCC will output the constant | |
861bb6c1 JL |
5366 | pool before the function. |
5367 | ||
feca2ed3 | 5368 | @findex ASM_OUTPUT_POOL_PROLOGUE |
8760eaae | 5369 | @item ASM_OUTPUT_POOL_PROLOGUE (@var{file}, @var{funname}, @var{fundecl}, @var{size}) |
feca2ed3 JW |
5370 | A C statement to output assembler commands to define the start of the |
5371 | constant pool for a function. @var{funname} is a string giving | |
5372 | the name of the function. Should the return type of the function | |
5373 | be required, it can be obtained via @var{fundecl}. @var{size} | |
5374 | is the size, in bytes, of the constant pool that will be written | |
5375 | immediately after this call. | |
5376 | ||
5377 | If no constant-pool prefix is required, the usual case, this macro need | |
5378 | not be defined. | |
5379 | ||
5380 | @findex ASM_OUTPUT_SPECIAL_POOL_ENTRY | |
5381 | @item ASM_OUTPUT_SPECIAL_POOL_ENTRY (@var{file}, @var{x}, @var{mode}, @var{align}, @var{labelno}, @var{jumpto}) | |
5382 | A C statement (with or without semicolon) to output a constant in the | |
5383 | constant pool, if it needs special treatment. (This macro need not do | |
5384 | anything for RTL expressions that can be output normally.) | |
5385 | ||
5386 | The argument @var{file} is the standard I/O stream to output the | |
5387 | assembler code on. @var{x} is the RTL expression for the constant to | |
5388 | output, and @var{mode} is the machine mode (in case @var{x} is a | |
5389 | @samp{const_int}). @var{align} is the required alignment for the value | |
5390 | @var{x}; you should output an assembler directive to force this much | |
5391 | alignment. | |
5392 | ||
5393 | The argument @var{labelno} is a number to use in an internal label for | |
5394 | the address of this pool entry. The definition of this macro is | |
5395 | responsible for outputting the label definition at the proper place. | |
5396 | Here is how to do this: | |
5397 | ||
5398 | @example | |
5399 | ASM_OUTPUT_INTERNAL_LABEL (@var{file}, "LC", @var{labelno}); | |
5400 | @end example | |
5401 | ||
5402 | When you output a pool entry specially, you should end with a | |
5403 | @code{goto} to the label @var{jumpto}. This will prevent the same pool | |
5404 | entry from being output a second time in the usual manner. | |
5405 | ||
5406 | You need not define this macro if it would do nothing. | |
5407 | ||
861bb6c1 JL |
5408 | @findex CONSTANT_AFTER_FUNCTION_P |
5409 | @item CONSTANT_AFTER_FUNCTION_P (@var{exp}) | |
5410 | Define this macro as a C expression which is nonzero if the constant | |
5411 | @var{exp}, of type @code{tree}, should be output after the code for a | |
5412 | function. The compiler will normally output all constants before the | |
5413 | function; you need not define this macro if this is OK. | |
5414 | ||
5415 | @findex ASM_OUTPUT_POOL_EPILOGUE | |
5416 | @item ASM_OUTPUT_POOL_EPILOGUE (@var{file} @var{funname} @var{fundecl} @var{size}) | |
5417 | A C statement to output assembler commands to at the end of the constant | |
5418 | pool for a function. @var{funname} is a string giving the name of the | |
5419 | function. Should the return type of the function be required, you can | |
5420 | obtain it via @var{fundecl}. @var{size} is the size, in bytes, of the | |
a3a15b4d | 5421 | constant pool that GCC wrote immediately before this call. |
861bb6c1 JL |
5422 | |
5423 | If no constant-pool epilogue is required, the usual case, you need not | |
5424 | define this macro. | |
5425 | ||
feca2ed3 JW |
5426 | @findex IS_ASM_LOGICAL_LINE_SEPARATOR |
5427 | @item IS_ASM_LOGICAL_LINE_SEPARATOR (@var{C}) | |
5428 | Define this macro as a C expression which is nonzero if @var{C} is | |
5429 | used as a logical line separator by the assembler. | |
5430 | ||
5431 | If you do not define this macro, the default is that only | |
5432 | the character @samp{;} is treated as a logical line separator. | |
5433 | ||
5434 | ||
5435 | @findex ASM_OPEN_PAREN | |
5436 | @findex ASM_CLOSE_PAREN | |
5437 | @item ASM_OPEN_PAREN | |
5438 | @itemx ASM_CLOSE_PAREN | |
5439 | These macros are defined as C string constant, describing the syntax | |
5440 | in the assembler for grouping arithmetic expressions. The following | |
5441 | definitions are correct for most assemblers: | |
5442 | ||
5443 | @example | |
5444 | #define ASM_OPEN_PAREN "(" | |
5445 | #define ASM_CLOSE_PAREN ")" | |
5446 | @end example | |
5447 | @end table | |
5448 | ||
5449 | These macros are provided by @file{real.h} for writing the definitions | |
5450 | of @code{ASM_OUTPUT_DOUBLE} and the like: | |
5451 | ||
5452 | @table @code | |
5453 | @item REAL_VALUE_TO_TARGET_SINGLE (@var{x}, @var{l}) | |
5454 | @itemx REAL_VALUE_TO_TARGET_DOUBLE (@var{x}, @var{l}) | |
5455 | @itemx REAL_VALUE_TO_TARGET_LONG_DOUBLE (@var{x}, @var{l}) | |
5456 | @findex REAL_VALUE_TO_TARGET_SINGLE | |
5457 | @findex REAL_VALUE_TO_TARGET_DOUBLE | |
5458 | @findex REAL_VALUE_TO_TARGET_LONG_DOUBLE | |
5459 | These translate @var{x}, of type @code{REAL_VALUE_TYPE}, to the target's | |
5460 | floating point representation, and store its bit pattern in the array of | |
5461 | @code{long int} whose address is @var{l}. The number of elements in the | |
5462 | output array is determined by the size of the desired target floating | |
5463 | point data type: 32 bits of it go in each @code{long int} array | |
5464 | element. Each array element holds 32 bits of the result, even if | |
5465 | @code{long int} is wider than 32 bits on the host machine. | |
5466 | ||
5467 | The array element values are designed so that you can print them out | |
5468 | using @code{fprintf} in the order they should appear in the target | |
5469 | machine's memory. | |
5470 | ||
5471 | @item REAL_VALUE_TO_DECIMAL (@var{x}, @var{format}, @var{string}) | |
5472 | @findex REAL_VALUE_TO_DECIMAL | |
5473 | This macro converts @var{x}, of type @code{REAL_VALUE_TYPE}, to a | |
5474 | decimal number and stores it as a string into @var{string}. | |
5475 | You must pass, as @var{string}, the address of a long enough block | |
5476 | of space to hold the result. | |
5477 | ||
5478 | The argument @var{format} is a @code{printf}-specification that serves | |
5479 | as a suggestion for how to format the output string. | |
5480 | @end table | |
5481 | ||
5482 | @node Uninitialized Data | |
5483 | @subsection Output of Uninitialized Variables | |
5484 | ||
5485 | Each of the macros in this section is used to do the whole job of | |
5486 | outputting a single uninitialized variable. | |
5487 | ||
5488 | @table @code | |
5489 | @findex ASM_OUTPUT_COMMON | |
5490 | @item ASM_OUTPUT_COMMON (@var{stream}, @var{name}, @var{size}, @var{rounded}) | |
5491 | A C statement (sans semicolon) to output to the stdio stream | |
5492 | @var{stream} the assembler definition of a common-label named | |
5493 | @var{name} whose size is @var{size} bytes. The variable @var{rounded} | |
5494 | is the size rounded up to whatever alignment the caller wants. | |
5495 | ||
5496 | Use the expression @code{assemble_name (@var{stream}, @var{name})} to | |
5497 | output the name itself; before and after that, output the additional | |
5498 | assembler syntax for defining the name, and a newline. | |
5499 | ||
5500 | This macro controls how the assembler definitions of uninitialized | |
5501 | common global variables are output. | |
5502 | ||
5503 | @findex ASM_OUTPUT_ALIGNED_COMMON | |
5504 | @item ASM_OUTPUT_ALIGNED_COMMON (@var{stream}, @var{name}, @var{size}, @var{alignment}) | |
5505 | Like @code{ASM_OUTPUT_COMMON} except takes the required alignment as a | |
5506 | separate, explicit argument. If you define this macro, it is used in | |
5507 | place of @code{ASM_OUTPUT_COMMON}, and gives you more flexibility in | |
5508 | handling the required alignment of the variable. The alignment is specified | |
5509 | as the number of bits. | |
5510 | ||
e9a25f70 JL |
5511 | @findex ASM_OUTPUT_ALIGNED_DECL_COMMON |
5512 | @item ASM_OUTPUT_ALIGNED_DECL_COMMON (@var{stream}, @var{decl}, @var{name}, @var{size}, @var{alignment}) | |
5513 | Like @code{ASM_OUTPUT_ALIGNED_COMMON} except that @var{decl} of the | |
5514 | variable to be output, if there is one, or @code{NULL_TREE} if there | |
8760eaae | 5515 | is no corresponding variable. If you define this macro, GCC will use it |
e9a25f70 JL |
5516 | in place of both @code{ASM_OUTPUT_COMMON} and |
5517 | @code{ASM_OUTPUT_ALIGNED_COMMON}. Define this macro when you need to see | |
5518 | the variable's decl in order to chose what to output. | |
5519 | ||
feca2ed3 JW |
5520 | @findex ASM_OUTPUT_SHARED_COMMON |
5521 | @item ASM_OUTPUT_SHARED_COMMON (@var{stream}, @var{name}, @var{size}, @var{rounded}) | |
5522 | If defined, it is similar to @code{ASM_OUTPUT_COMMON}, except that it | |
5523 | is used when @var{name} is shared. If not defined, @code{ASM_OUTPUT_COMMON} | |
5524 | will be used. | |
5525 | ||
5526 | @findex ASM_OUTPUT_BSS | |
5527 | @item ASM_OUTPUT_BSS (@var{stream}, @var{decl}, @var{name}, @var{size}, @var{rounded}) | |
5528 | A C statement (sans semicolon) to output to the stdio stream | |
5529 | @var{stream} the assembler definition of uninitialized global @var{decl} named | |
5530 | @var{name} whose size is @var{size} bytes. The variable @var{rounded} | |
5531 | is the size rounded up to whatever alignment the caller wants. | |
5532 | ||
5533 | Try to use function @code{asm_output_bss} defined in @file{varasm.c} when | |
5534 | defining this macro. If unable, use the expression | |
5535 | @code{assemble_name (@var{stream}, @var{name})} to output the name itself; | |
5536 | before and after that, output the additional assembler syntax for defining | |
5537 | the name, and a newline. | |
5538 | ||
5539 | This macro controls how the assembler definitions of uninitialized global | |
5540 | variables are output. This macro exists to properly support languages like | |
5541 | @code{c++} which do not have @code{common} data. However, this macro currently | |
5542 | is not defined for all targets. If this macro and | |
5543 | @code{ASM_OUTPUT_ALIGNED_BSS} are not defined then @code{ASM_OUTPUT_COMMON} | |
e9a25f70 JL |
5544 | or @code{ASM_OUTPUT_ALIGNED_COMMON} or |
5545 | @code{ASM_OUTPUT_ALIGNED_DECL_COMMON} is used. | |
feca2ed3 JW |
5546 | |
5547 | @findex ASM_OUTPUT_ALIGNED_BSS | |
5548 | @item ASM_OUTPUT_ALIGNED_BSS (@var{stream}, @var{decl}, @var{name}, @var{size}, @var{alignment}) | |
5549 | Like @code{ASM_OUTPUT_BSS} except takes the required alignment as a | |
5550 | separate, explicit argument. If you define this macro, it is used in | |
5551 | place of @code{ASM_OUTPUT_BSS}, and gives you more flexibility in | |
5552 | handling the required alignment of the variable. The alignment is specified | |
5553 | as the number of bits. | |
5554 | ||
5555 | Try to use function @code{asm_output_aligned_bss} defined in file | |
5556 | @file{varasm.c} when defining this macro. | |
5557 | ||
5558 | @findex ASM_OUTPUT_SHARED_BSS | |
5559 | @item ASM_OUTPUT_SHARED_BSS (@var{stream}, @var{decl}, @var{name}, @var{size}, @var{rounded}) | |
5560 | If defined, it is similar to @code{ASM_OUTPUT_BSS}, except that it | |
5561 | is used when @var{name} is shared. If not defined, @code{ASM_OUTPUT_BSS} | |
5562 | will be used. | |
5563 | ||
5564 | @findex ASM_OUTPUT_LOCAL | |
5565 | @item ASM_OUTPUT_LOCAL (@var{stream}, @var{name}, @var{size}, @var{rounded}) | |
5566 | A C statement (sans semicolon) to output to the stdio stream | |
5567 | @var{stream} the assembler definition of a local-common-label named | |
5568 | @var{name} whose size is @var{size} bytes. The variable @var{rounded} | |
5569 | is the size rounded up to whatever alignment the caller wants. | |
5570 | ||
5571 | Use the expression @code{assemble_name (@var{stream}, @var{name})} to | |
5572 | output the name itself; before and after that, output the additional | |
5573 | assembler syntax for defining the name, and a newline. | |
5574 | ||
5575 | This macro controls how the assembler definitions of uninitialized | |
5576 | static variables are output. | |
5577 | ||
5578 | @findex ASM_OUTPUT_ALIGNED_LOCAL | |
5579 | @item ASM_OUTPUT_ALIGNED_LOCAL (@var{stream}, @var{name}, @var{size}, @var{alignment}) | |
5580 | Like @code{ASM_OUTPUT_LOCAL} except takes the required alignment as a | |
5581 | separate, explicit argument. If you define this macro, it is used in | |
5582 | place of @code{ASM_OUTPUT_LOCAL}, and gives you more flexibility in | |
5583 | handling the required alignment of the variable. The alignment is specified | |
5584 | as the number of bits. | |
5585 | ||
e9a25f70 JL |
5586 | @findex ASM_OUTPUT_ALIGNED_DECL_LOCAL |
5587 | @item ASM_OUTPUT_ALIGNED_DECL_LOCAL (@var{stream}, @var{decl}, @var{name}, @var{size}, @var{alignment}) | |
5588 | Like @code{ASM_OUTPUT_ALIGNED_DECL} except that @var{decl} of the | |
5589 | variable to be output, if there is one, or @code{NULL_TREE} if there | |
8760eaae | 5590 | is no corresponding variable. If you define this macro, GCC will use it |
e9a25f70 JL |
5591 | in place of both @code{ASM_OUTPUT_DECL} and |
5592 | @code{ASM_OUTPUT_ALIGNED_DECL}. Define this macro when you need to see | |
5593 | the variable's decl in order to chose what to output. | |
5594 | ||
feca2ed3 JW |
5595 | @findex ASM_OUTPUT_SHARED_LOCAL |
5596 | @item ASM_OUTPUT_SHARED_LOCAL (@var{stream}, @var{name}, @var{size}, @var{rounded}) | |
5597 | If defined, it is similar to @code{ASM_OUTPUT_LOCAL}, except that it | |
5598 | is used when @var{name} is shared. If not defined, @code{ASM_OUTPUT_LOCAL} | |
5599 | will be used. | |
5600 | @end table | |
5601 | ||
5602 | @node Label Output | |
5603 | @subsection Output and Generation of Labels | |
5604 | ||
5605 | @c prevent bad page break with this line | |
5606 | This is about outputting labels. | |
5607 | ||
5608 | @table @code | |
5609 | @findex ASM_OUTPUT_LABEL | |
5610 | @findex assemble_name | |
5611 | @item ASM_OUTPUT_LABEL (@var{stream}, @var{name}) | |
5612 | A C statement (sans semicolon) to output to the stdio stream | |
5613 | @var{stream} the assembler definition of a label named @var{name}. | |
5614 | Use the expression @code{assemble_name (@var{stream}, @var{name})} to | |
5615 | output the name itself; before and after that, output the additional | |
5616 | assembler syntax for defining the name, and a newline. | |
5617 | ||
5618 | @findex ASM_DECLARE_FUNCTION_NAME | |
5619 | @item ASM_DECLARE_FUNCTION_NAME (@var{stream}, @var{name}, @var{decl}) | |
5620 | A C statement (sans semicolon) to output to the stdio stream | |
5621 | @var{stream} any text necessary for declaring the name @var{name} of a | |
5622 | function which is being defined. This macro is responsible for | |
5623 | outputting the label definition (perhaps using | |
5624 | @code{ASM_OUTPUT_LABEL}). The argument @var{decl} is the | |
5625 | @code{FUNCTION_DECL} tree node representing the function. | |
5626 | ||
5627 | If this macro is not defined, then the function name is defined in the | |
5628 | usual manner as a label (by means of @code{ASM_OUTPUT_LABEL}). | |
5629 | ||
5630 | @findex ASM_DECLARE_FUNCTION_SIZE | |
5631 | @item ASM_DECLARE_FUNCTION_SIZE (@var{stream}, @var{name}, @var{decl}) | |
5632 | A C statement (sans semicolon) to output to the stdio stream | |
5633 | @var{stream} any text necessary for declaring the size of a function | |
5634 | which is being defined. The argument @var{name} is the name of the | |
5635 | function. The argument @var{decl} is the @code{FUNCTION_DECL} tree node | |
5636 | representing the function. | |
5637 | ||
5638 | If this macro is not defined, then the function size is not defined. | |
5639 | ||
5640 | @findex ASM_DECLARE_OBJECT_NAME | |
5641 | @item ASM_DECLARE_OBJECT_NAME (@var{stream}, @var{name}, @var{decl}) | |
5642 | A C statement (sans semicolon) to output to the stdio stream | |
5643 | @var{stream} any text necessary for declaring the name @var{name} of an | |
5644 | initialized variable which is being defined. This macro must output the | |
5645 | label definition (perhaps using @code{ASM_OUTPUT_LABEL}). The argument | |
5646 | @var{decl} is the @code{VAR_DECL} tree node representing the variable. | |
5647 | ||
5648 | If this macro is not defined, then the variable name is defined in the | |
5649 | usual manner as a label (by means of @code{ASM_OUTPUT_LABEL}). | |
5650 | ||
1cb36a98 RH |
5651 | @findex ASM_DECLARE_REGISTER_GLOBAL |
5652 | @item ASM_DECLARE_REGISTER_GLOBAL (@var{stream}, @var{decl}, @var{regno}, @var{name}) | |
5653 | A C statement (sans semicolon) to output to the stdio stream | |
5654 | @var{stream} any text necessary for claiming a register @var{regno} | |
5655 | for a global variable @var{decl} with name @var{name}. | |
5656 | ||
5657 | If you don't define this macro, that is equivalent to defining it to do | |
5658 | nothing. | |
5659 | ||
feca2ed3 JW |
5660 | @findex ASM_FINISH_DECLARE_OBJECT |
5661 | @item ASM_FINISH_DECLARE_OBJECT (@var{stream}, @var{decl}, @var{toplevel}, @var{atend}) | |
5662 | A C statement (sans semicolon) to finish up declaring a variable name | |
5663 | once the compiler has processed its initializer fully and thus has had a | |
5664 | chance to determine the size of an array when controlled by an | |
5665 | initializer. This is used on systems where it's necessary to declare | |
5666 | something about the size of the object. | |
5667 | ||
5668 | If you don't define this macro, that is equivalent to defining it to do | |
5669 | nothing. | |
5670 | ||
5671 | @findex ASM_GLOBALIZE_LABEL | |
5672 | @item ASM_GLOBALIZE_LABEL (@var{stream}, @var{name}) | |
5673 | A C statement (sans semicolon) to output to the stdio stream | |
5674 | @var{stream} some commands that will make the label @var{name} global; | |
5675 | that is, available for reference from other files. Use the expression | |
5676 | @code{assemble_name (@var{stream}, @var{name})} to output the name | |
5677 | itself; before and after that, output the additional assembler syntax | |
5678 | for making that name global, and a newline. | |
5679 | ||
5680 | @findex ASM_WEAKEN_LABEL | |
5681 | @item ASM_WEAKEN_LABEL | |
5682 | A C statement (sans semicolon) to output to the stdio stream | |
5683 | @var{stream} some commands that will make the label @var{name} weak; | |
5684 | that is, available for reference from other files but only used if | |
5685 | no other definition is available. Use the expression | |
5686 | @code{assemble_name (@var{stream}, @var{name})} to output the name | |
5687 | itself; before and after that, output the additional assembler syntax | |
5688 | for making that name weak, and a newline. | |
5689 | ||
a3a15b4d | 5690 | If you don't define this macro, GCC will not support weak |
feca2ed3 JW |
5691 | symbols and you should not define the @code{SUPPORTS_WEAK} macro. |
5692 | ||
5693 | @findex SUPPORTS_WEAK | |
5694 | @item SUPPORTS_WEAK | |
5695 | A C expression which evaluates to true if the target supports weak symbols. | |
5696 | ||
5697 | If you don't define this macro, @file{defaults.h} provides a default | |
5698 | definition. If @code{ASM_WEAKEN_LABEL} is defined, the default | |
5699 | definition is @samp{1}; otherwise, it is @samp{0}. Define this macro if | |
5700 | you want to control weak symbol support with a compiler flag such as | |
5701 | @samp{-melf}. | |
5702 | ||
5703 | @findex MAKE_DECL_ONE_ONLY (@var{decl}) | |
5704 | @item MAKE_DECL_ONE_ONLY | |
5705 | A C statement (sans semicolon) to mark @var{decl} to be emitted as a | |
5706 | public symbol such that extra copies in multiple translation units will | |
5707 | be discarded by the linker. Define this macro if your object file | |
5708 | format provides support for this concept, such as the @samp{COMDAT} | |
5709 | section flags in the Microsoft Windows PE/COFF format, and this support | |
5710 | requires changes to @var{decl}, such as putting it in a separate section. | |
5711 | ||
e9a25f70 JL |
5712 | @findex SUPPORTS_ONE_ONLY |
5713 | @item SUPPORTS_ONE_ONLY | |
feca2ed3 JW |
5714 | A C expression which evaluates to true if the target supports one-only |
5715 | semantics. | |
5716 | ||
5717 | If you don't define this macro, @file{varasm.c} provides a default | |
5718 | definition. If @code{MAKE_DECL_ONE_ONLY} is defined, the default | |
5719 | definition is @samp{1}; otherwise, it is @samp{0}. Define this macro if | |
e9a25f70 | 5720 | you want to control one-only symbol support with a compiler flag, or if |
feca2ed3 JW |
5721 | setting the @code{DECL_ONE_ONLY} flag is enough to mark a declaration to |
5722 | be emitted as one-only. | |
5723 | ||
5724 | @findex ASM_OUTPUT_EXTERNAL | |
5725 | @item ASM_OUTPUT_EXTERNAL (@var{stream}, @var{decl}, @var{name}) | |
5726 | A C statement (sans semicolon) to output to the stdio stream | |
5727 | @var{stream} any text necessary for declaring the name of an external | |
5728 | symbol named @var{name} which is referenced in this compilation but | |
5729 | not defined. The value of @var{decl} is the tree node for the | |
5730 | declaration. | |
5731 | ||
5732 | This macro need not be defined if it does not need to output anything. | |
5733 | The GNU assembler and most Unix assemblers don't require anything. | |
5734 | ||
5735 | @findex ASM_OUTPUT_EXTERNAL_LIBCALL | |
5736 | @item ASM_OUTPUT_EXTERNAL_LIBCALL (@var{stream}, @var{symref}) | |
5737 | A C statement (sans semicolon) to output on @var{stream} an assembler | |
5738 | pseudo-op to declare a library function name external. The name of the | |
5739 | library function is given by @var{symref}, which has type @code{rtx} and | |
5740 | is a @code{symbol_ref}. | |
5741 | ||
5742 | This macro need not be defined if it does not need to output anything. | |
5743 | The GNU assembler and most Unix assemblers don't require anything. | |
5744 | ||
5745 | @findex ASM_OUTPUT_LABELREF | |
5746 | @item ASM_OUTPUT_LABELREF (@var{stream}, @var{name}) | |
5747 | A C statement (sans semicolon) to output to the stdio stream | |
5748 | @var{stream} a reference in assembler syntax to a label named | |
5749 | @var{name}. This should add @samp{_} to the front of the name, if that | |
5750 | is customary on your operating system, as it is in most Berkeley Unix | |
5751 | systems. This macro is used in @code{assemble_name}. | |
5752 | ||
5753 | @ignore @c Seems not to exist anymore. | |
5754 | @findex ASM_OUTPUT_LABELREF_AS_INT | |
5755 | @item ASM_OUTPUT_LABELREF_AS_INT (@var{file}, @var{label}) | |
5756 | Define this macro for systems that use the program @code{collect2}. | |
5757 | The definition should be a C statement to output a word containing | |
5758 | a reference to the label @var{label}. | |
5759 | @end ignore | |
5760 | ||
5761 | @findex ASM_OUTPUT_INTERNAL_LABEL | |
5762 | @item ASM_OUTPUT_INTERNAL_LABEL (@var{stream}, @var{prefix}, @var{num}) | |
5763 | A C statement to output to the stdio stream @var{stream} a label whose | |
5764 | name is made from the string @var{prefix} and the number @var{num}. | |
5765 | ||
5766 | It is absolutely essential that these labels be distinct from the labels | |
5767 | used for user-level functions and variables. Otherwise, certain programs | |
5768 | will have name conflicts with internal labels. | |
5769 | ||
5770 | It is desirable to exclude internal labels from the symbol table of the | |
5771 | object file. Most assemblers have a naming convention for labels that | |
5772 | should be excluded; on many systems, the letter @samp{L} at the | |
5773 | beginning of a label has this effect. You should find out what | |
5774 | convention your system uses, and follow it. | |
5775 | ||
5776 | The usual definition of this macro is as follows: | |
5777 | ||
5778 | @example | |
5779 | fprintf (@var{stream}, "L%s%d:\n", @var{prefix}, @var{num}) | |
5780 | @end example | |
5781 | ||
8cd0faaf CM |
5782 | @findex ASM_OUTPUT_ALTERNATE_LABEL_NAME |
5783 | @item ASM_OUTPUT_ALTERNATE_LABEL_NAME (@var{stream}, @var{string}) | |
5784 | A C statement to output to the stdio stream @var{stream} the string | |
5785 | @var{string}. | |
5786 | ||
5787 | The default definition of this macro is as follows: | |
5788 | ||
5789 | @example | |
5790 | fprintf (@var{stream}, "%s:\n", LABEL_ALTERNATE_NAME (INSN)) | |
5791 | @end example | |
5792 | ||
feca2ed3 JW |
5793 | @findex ASM_GENERATE_INTERNAL_LABEL |
5794 | @item ASM_GENERATE_INTERNAL_LABEL (@var{string}, @var{prefix}, @var{num}) | |
5795 | A C statement to store into the string @var{string} a label whose name | |
5796 | is made from the string @var{prefix} and the number @var{num}. | |
5797 | ||
5798 | This string, when output subsequently by @code{assemble_name}, should | |
5799 | produce the output that @code{ASM_OUTPUT_INTERNAL_LABEL} would produce | |
5800 | with the same @var{prefix} and @var{num}. | |
5801 | ||
5802 | If the string begins with @samp{*}, then @code{assemble_name} will | |
5803 | output the rest of the string unchanged. It is often convenient for | |
5804 | @code{ASM_GENERATE_INTERNAL_LABEL} to use @samp{*} in this way. If the | |
5805 | string doesn't start with @samp{*}, then @code{ASM_OUTPUT_LABELREF} gets | |
5806 | to output the string, and may change it. (Of course, | |
5807 | @code{ASM_OUTPUT_LABELREF} is also part of your machine description, so | |
5808 | you should know what it does on your machine.) | |
5809 | ||
5810 | @findex ASM_FORMAT_PRIVATE_NAME | |
5811 | @item ASM_FORMAT_PRIVATE_NAME (@var{outvar}, @var{name}, @var{number}) | |
5812 | A C expression to assign to @var{outvar} (which is a variable of type | |
5813 | @code{char *}) a newly allocated string made from the string | |
5814 | @var{name} and the number @var{number}, with some suitable punctuation | |
5815 | added. Use @code{alloca} to get space for the string. | |
5816 | ||
5817 | The string will be used as an argument to @code{ASM_OUTPUT_LABELREF} to | |
5818 | produce an assembler label for an internal static variable whose name is | |
5819 | @var{name}. Therefore, the string must be such as to result in valid | |
5820 | assembler code. The argument @var{number} is different each time this | |
5821 | macro is executed; it prevents conflicts between similarly-named | |
5822 | internal static variables in different scopes. | |
5823 | ||
5824 | Ideally this string should not be a valid C identifier, to prevent any | |
5825 | conflict with the user's own symbols. Most assemblers allow periods | |
5826 | or percent signs in assembler symbols; putting at least one of these | |
5827 | between the name and the number will suffice. | |
5828 | ||
5829 | @findex ASM_OUTPUT_DEF | |
5830 | @item ASM_OUTPUT_DEF (@var{stream}, @var{name}, @var{value}) | |
5831 | A C statement to output to the stdio stream @var{stream} assembler code | |
5832 | which defines (equates) the symbol @var{name} to have the value @var{value}. | |
5833 | ||
203cb4ef | 5834 | @findex SET_ASM_OP |
feca2ed3 JW |
5835 | If SET_ASM_OP is defined, a default definition is provided which is |
5836 | correct for most systems. | |
810e3c45 | 5837 | |
e4faf1eb | 5838 | @findex ASM_OUTPUT_DEF_FROM_DECLS |
8760eaae | 5839 | @item ASM_OUTPUT_DEF_FROM_DECLS (@var{stream}, @var{decl_of_name}, @var{decl_of_value}) |
e4faf1eb NC |
5840 | A C statement to output to the stdio stream @var{stream} assembler code |
5841 | which defines (equates) the symbol whoes tree node is @var{decl_of_name} | |
5842 | to have the value of the tree node @var{decl_of_value}. This macro will | |
5843 | be used in preference to @samp{ASM_OUTPUT_DEF} if it is defined and if | |
5844 | the tree nodes are available. | |
5845 | ||
956d6950 JL |
5846 | @findex ASM_OUTPUT_DEFINE_LABEL_DIFFERENCE_SYMBOL |
5847 | @item ASM_OUTPUT_DEFINE_LABEL_DIFFERENCE_SYMBOL (@var{stream}, @var{symbol}, @var{high}, @var{low}) | |
5848 | A C statement to output to the stdio stream @var{stream} assembler code | |
5849 | which defines (equates) the symbol @var{symbol} to have a value equal to | |
5850 | the difference of the two symbols @var{high} and @var{low}, i.e. | |
a3a15b4d | 5851 | @var{high} minus @var{low}. GCC guarantees that the symbols @var{high} |
956d6950 JL |
5852 | and @var{low} are already known by the assembler so that the difference |
5853 | resolves into a constant. | |
5854 | ||
203cb4ef | 5855 | @findex SET_ASM_OP |
956d6950 JL |
5856 | If SET_ASM_OP is defined, a default definition is provided which is |
5857 | correct for most systems. | |
5858 | ||
810e3c45 JM |
5859 | @findex ASM_OUTPUT_WEAK_ALIAS |
5860 | @item ASM_OUTPUT_WEAK_ALIAS (@var{stream}, @var{name}, @var{value}) | |
5861 | A C statement to output to the stdio stream @var{stream} assembler code | |
5862 | which defines (equates) the weak symbol @var{name} to have the value | |
5863 | @var{value}. | |
5864 | ||
5865 | Define this macro if the target only supports weak aliases; define | |
5866 | ASM_OUTPUT_DEF instead if possible. | |
5867 | ||
feca2ed3 JW |
5868 | @findex OBJC_GEN_METHOD_LABEL |
5869 | @item OBJC_GEN_METHOD_LABEL (@var{buf}, @var{is_inst}, @var{class_name}, @var{cat_name}, @var{sel_name}) | |
5870 | Define this macro to override the default assembler names used for | |
5871 | Objective C methods. | |
5872 | ||
5873 | The default name is a unique method number followed by the name of the | |
5874 | class (e.g.@: @samp{_1_Foo}). For methods in categories, the name of | |
5875 | the category is also included in the assembler name (e.g.@: | |
5876 | @samp{_1_Foo_Bar}). | |
5877 | ||
5878 | These names are safe on most systems, but make debugging difficult since | |
5879 | the method's selector is not present in the name. Therefore, particular | |
5880 | systems define other ways of computing names. | |
5881 | ||
5882 | @var{buf} is an expression of type @code{char *} which gives you a | |
5883 | buffer in which to store the name; its length is as long as | |
5884 | @var{class_name}, @var{cat_name} and @var{sel_name} put together, plus | |
5885 | 50 characters extra. | |
5886 | ||
5887 | The argument @var{is_inst} specifies whether the method is an instance | |
5888 | method or a class method; @var{class_name} is the name of the class; | |
5889 | @var{cat_name} is the name of the category (or NULL if the method is not | |
5890 | in a category); and @var{sel_name} is the name of the selector. | |
5891 | ||
5892 | On systems where the assembler can handle quoted names, you can use this | |
5893 | macro to provide more human-readable names. | |
5894 | @end table | |
5895 | ||
5896 | @node Initialization | |
5897 | @subsection How Initialization Functions Are Handled | |
5898 | @cindex initialization routines | |
5899 | @cindex termination routines | |
5900 | @cindex constructors, output of | |
5901 | @cindex destructors, output of | |
5902 | ||
5903 | The compiled code for certain languages includes @dfn{constructors} | |
5904 | (also called @dfn{initialization routines})---functions to initialize | |
5905 | data in the program when the program is started. These functions need | |
5906 | to be called before the program is ``started''---that is to say, before | |
5907 | @code{main} is called. | |
5908 | ||
5909 | Compiling some languages generates @dfn{destructors} (also called | |
5910 | @dfn{termination routines}) that should be called when the program | |
5911 | terminates. | |
5912 | ||
5913 | To make the initialization and termination functions work, the compiler | |
5914 | must output something in the assembler code to cause those functions to | |
5915 | be called at the appropriate time. When you port the compiler to a new | |
5916 | system, you need to specify how to do this. | |
5917 | ||
5918 | There are two major ways that GCC currently supports the execution of | |
5919 | initialization and termination functions. Each way has two variants. | |
5920 | Much of the structure is common to all four variations. | |
5921 | ||
5922 | @findex __CTOR_LIST__ | |
5923 | @findex __DTOR_LIST__ | |
5924 | The linker must build two lists of these functions---a list of | |
5925 | initialization functions, called @code{__CTOR_LIST__}, and a list of | |
5926 | termination functions, called @code{__DTOR_LIST__}. | |
5927 | ||
5928 | Each list always begins with an ignored function pointer (which may hold | |
5929 | 0, @minus{}1, or a count of the function pointers after it, depending on | |
5930 | the environment). This is followed by a series of zero or more function | |
5931 | pointers to constructors (or destructors), followed by a function | |
5932 | pointer containing zero. | |
5933 | ||
5934 | Depending on the operating system and its executable file format, either | |
5935 | @file{crtstuff.c} or @file{libgcc2.c} traverses these lists at startup | |
5936 | time and exit time. Constructors are called in reverse order of the | |
5937 | list; destructors in forward order. | |
5938 | ||
5939 | The best way to handle static constructors works only for object file | |
5940 | formats which provide arbitrarily-named sections. A section is set | |
5941 | aside for a list of constructors, and another for a list of destructors. | |
5942 | Traditionally these are called @samp{.ctors} and @samp{.dtors}. Each | |
5943 | object file that defines an initialization function also puts a word in | |
5944 | the constructor section to point to that function. The linker | |
5945 | accumulates all these words into one contiguous @samp{.ctors} section. | |
5946 | Termination functions are handled similarly. | |
5947 | ||
5948 | To use this method, you need appropriate definitions of the macros | |
5949 | @code{ASM_OUTPUT_CONSTRUCTOR} and @code{ASM_OUTPUT_DESTRUCTOR}. Usually | |
5950 | you can get them by including @file{svr4.h}. | |
5951 | ||
5952 | When arbitrary sections are available, there are two variants, depending | |
5953 | upon how the code in @file{crtstuff.c} is called. On systems that | |
5954 | support an @dfn{init} section which is executed at program startup, | |
5955 | parts of @file{crtstuff.c} are compiled into that section. The | |
5956 | program is linked by the @code{gcc} driver like this: | |
5957 | ||
5958 | @example | |
5959 | ld -o @var{output_file} crtbegin.o @dots{} crtend.o -lgcc | |
5960 | @end example | |
5961 | ||
5962 | The head of a function (@code{__do_global_ctors}) appears in the init | |
5963 | section of @file{crtbegin.o}; the remainder of the function appears in | |
5964 | the init section of @file{crtend.o}. The linker will pull these two | |
5965 | parts of the section together, making a whole function. If any of the | |
5966 | user's object files linked into the middle of it contribute code, then that | |
5967 | code will be executed as part of the body of @code{__do_global_ctors}. | |
5968 | ||
5969 | To use this variant, you must define the @code{INIT_SECTION_ASM_OP} | |
5970 | macro properly. | |
5971 | ||
5972 | If no init section is available, do not define | |
5973 | @code{INIT_SECTION_ASM_OP}. Then @code{__do_global_ctors} is built into | |
5974 | the text section like all other functions, and resides in | |
5975 | @file{libgcc.a}. When GCC compiles any function called @code{main}, it | |
5976 | inserts a procedure call to @code{__main} as the first executable code | |
5977 | after the function prologue. The @code{__main} function, also defined | |
5978 | in @file{libgcc2.c}, simply calls @file{__do_global_ctors}. | |
5979 | ||
5980 | In file formats that don't support arbitrary sections, there are again | |
5981 | two variants. In the simplest variant, the GNU linker (GNU @code{ld}) | |
5982 | and an `a.out' format must be used. In this case, | |
5983 | @code{ASM_OUTPUT_CONSTRUCTOR} is defined to produce a @code{.stabs} | |
5984 | entry of type @samp{N_SETT}, referencing the name @code{__CTOR_LIST__}, | |
5985 | and with the address of the void function containing the initialization | |
5986 | code as its value. The GNU linker recognizes this as a request to add | |
5987 | the value to a ``set''; the values are accumulated, and are eventually | |
5988 | placed in the executable as a vector in the format described above, with | |
5989 | a leading (ignored) count and a trailing zero element. | |
5990 | @code{ASM_OUTPUT_DESTRUCTOR} is handled similarly. Since no init | |
5991 | section is available, the absence of @code{INIT_SECTION_ASM_OP} causes | |
5992 | the compilation of @code{main} to call @code{__main} as above, starting | |
5993 | the initialization process. | |
5994 | ||
5995 | The last variant uses neither arbitrary sections nor the GNU linker. | |
5996 | This is preferable when you want to do dynamic linking and when using | |
5997 | file formats which the GNU linker does not support, such as `ECOFF'. In | |
5998 | this case, @code{ASM_OUTPUT_CONSTRUCTOR} does not produce an | |
5999 | @code{N_SETT} symbol; initialization and termination functions are | |
6000 | recognized simply by their names. This requires an extra program in the | |
6001 | linkage step, called @code{collect2}. This program pretends to be the | |
a3a15b4d | 6002 | linker, for use with GCC; it does its job by running the ordinary |
feca2ed3 JW |
6003 | linker, but also arranges to include the vectors of initialization and |
6004 | termination functions. These functions are called via @code{__main} as | |
6005 | described above. | |
6006 | ||
6007 | Choosing among these configuration options has been simplified by a set | |
6008 | of operating-system-dependent files in the @file{config} subdirectory. | |
6009 | These files define all of the relevant parameters. Usually it is | |
6010 | sufficient to include one into your specific machine-dependent | |
6011 | configuration file. These files are: | |
6012 | ||
6013 | @table @file | |
6014 | @item aoutos.h | |
6015 | For operating systems using the `a.out' format. | |
6016 | ||
6017 | @item next.h | |
6018 | For operating systems using the `MachO' format. | |
6019 | ||
6020 | @item svr3.h | |
6021 | For System V Release 3 and similar systems using `COFF' format. | |
6022 | ||
6023 | @item svr4.h | |
6024 | For System V Release 4 and similar systems using `ELF' format. | |
6025 | ||
6026 | @item vms.h | |
6027 | For the VMS operating system. | |
6028 | @end table | |
6029 | ||
6030 | @ifinfo | |
6031 | The following section describes the specific macros that control and | |
6032 | customize the handling of initialization and termination functions. | |
6033 | @end ifinfo | |
6034 | ||
6035 | @node Macros for Initialization | |
6036 | @subsection Macros Controlling Initialization Routines | |
6037 | ||
6038 | Here are the macros that control how the compiler handles initialization | |
6039 | and termination functions: | |
6040 | ||
6041 | @table @code | |
6042 | @findex INIT_SECTION_ASM_OP | |
6043 | @item INIT_SECTION_ASM_OP | |
6044 | If defined, a C string constant for the assembler operation to identify | |
a3a15b4d | 6045 | the following data as initialization code. If not defined, GCC will |
feca2ed3 JW |
6046 | assume such a section does not exist. When you are using special |
6047 | sections for initialization and termination functions, this macro also | |
6048 | controls how @file{crtstuff.c} and @file{libgcc2.c} arrange to run the | |
6049 | initialization functions. | |
6050 | ||
6051 | @item HAS_INIT_SECTION | |
6052 | @findex HAS_INIT_SECTION | |
6053 | If defined, @code{main} will not call @code{__main} as described above. | |
6054 | This macro should be defined for systems that control the contents of the | |
6055 | init section on a symbol-by-symbol basis, such as OSF/1, and should not | |
6056 | be defined explicitly for systems that support | |
6057 | @code{INIT_SECTION_ASM_OP}. | |
6058 | ||
6059 | @item LD_INIT_SWITCH | |
6060 | @findex LD_INIT_SWITCH | |
6061 | If defined, a C string constant for a switch that tells the linker that | |
6062 | the following symbol is an initialization routine. | |
6063 | ||
6064 | @item LD_FINI_SWITCH | |
6065 | @findex LD_FINI_SWITCH | |
6066 | If defined, a C string constant for a switch that tells the linker that | |
6067 | the following symbol is a finalization routine. | |
6068 | ||
6069 | @item INVOKE__main | |
6070 | @findex INVOKE__main | |
6071 | If defined, @code{main} will call @code{__main} despite the presence of | |
6072 | @code{INIT_SECTION_ASM_OP}. This macro should be defined for systems | |
6073 | where the init section is not actually run automatically, but is still | |
6074 | useful for collecting the lists of constructors and destructors. | |
6075 | ||
6076 | @item ASM_OUTPUT_CONSTRUCTOR (@var{stream}, @var{name}) | |
6077 | @findex ASM_OUTPUT_CONSTRUCTOR | |
6078 | Define this macro as a C statement to output on the stream @var{stream} | |
6079 | the assembler code to arrange to call the function named @var{name} at | |
6080 | initialization time. | |
6081 | ||
6082 | Assume that @var{name} is the name of a C function generated | |
6083 | automatically by the compiler. This function takes no arguments. Use | |
6084 | the function @code{assemble_name} to output the name @var{name}; this | |
6085 | performs any system-specific syntactic transformations such as adding an | |
6086 | underscore. | |
6087 | ||
6088 | If you don't define this macro, nothing special is output to arrange to | |
6089 | call the function. This is correct when the function will be called in | |
6090 | some other manner---for example, by means of the @code{collect2} program, | |
6091 | which looks through the symbol table to find these functions by their | |
6092 | names. | |
6093 | ||
6094 | @item ASM_OUTPUT_DESTRUCTOR (@var{stream}, @var{name}) | |
6095 | @findex ASM_OUTPUT_DESTRUCTOR | |
6096 | This is like @code{ASM_OUTPUT_CONSTRUCTOR} but used for termination | |
6097 | functions rather than initialization functions. | |
14686fcd JL |
6098 | |
6099 | When @code{ASM_OUTPUT_CONSTRUCTOR} and @code{ASM_OUTPUT_DESTRUCTOR} are | |
6100 | defined, the initializaiton routine generated for the generated object | |
6101 | file will have static linkage. | |
feca2ed3 JW |
6102 | @end table |
6103 | ||
6104 | If your system uses @code{collect2} as the means of processing | |
6105 | constructors, then that program normally uses @code{nm} to scan an | |
14686fcd JL |
6106 | object file for constructor functions to be called. On such systems you |
6107 | must not define @code{ASM_OUTPUT_CONSTRUCTOR} and @code{ASM_OUTPUT_DESTRUCTOR} | |
6108 | as the object file's initialization routine must have global scope. | |
6109 | ||
6110 | On certain kinds of systems, you can define these macros to make | |
6111 | @code{collect2} work faster (and, in some cases, make it work at all): | |
feca2ed3 JW |
6112 | |
6113 | @table @code | |
6114 | @findex OBJECT_FORMAT_COFF | |
6115 | @item OBJECT_FORMAT_COFF | |
6116 | Define this macro if the system uses COFF (Common Object File Format) | |
6117 | object files, so that @code{collect2} can assume this format and scan | |
6118 | object files directly for dynamic constructor/destructor functions. | |
6119 | ||
6120 | @findex OBJECT_FORMAT_ROSE | |
6121 | @item OBJECT_FORMAT_ROSE | |
6122 | Define this macro if the system uses ROSE format object files, so that | |
6123 | @code{collect2} can assume this format and scan object files directly | |
6124 | for dynamic constructor/destructor functions. | |
6125 | ||
6126 | These macros are effective only in a native compiler; @code{collect2} as | |
6127 | part of a cross compiler always uses @code{nm} for the target machine. | |
6128 | ||
6129 | @findex REAL_NM_FILE_NAME | |
6130 | @item REAL_NM_FILE_NAME | |
6131 | Define this macro as a C string constant containing the file name to use | |
6132 | to execute @code{nm}. The default is to search the path normally for | |
6133 | @code{nm}. | |
6134 | ||
6135 | If your system supports shared libraries and has a program to list the | |
6136 | dynamic dependencies of a given library or executable, you can define | |
6137 | these macros to enable support for running initialization and | |
6138 | termination functions in shared libraries: | |
6139 | ||
6140 | @findex LDD_SUFFIX | |
6141 | @item LDD_SUFFIX | |
6142 | Define this macro to a C string constant containing the name of the | |
6143 | program which lists dynamic dependencies, like @code{"ldd"} under SunOS 4. | |
6144 | ||
6145 | @findex PARSE_LDD_OUTPUT | |
6146 | @item PARSE_LDD_OUTPUT (@var{PTR}) | |
6147 | Define this macro to be C code that extracts filenames from the output | |
6148 | of the program denoted by @code{LDD_SUFFIX}. @var{PTR} is a variable | |
6149 | of type @code{char *} that points to the beginning of a line of output | |
6150 | from @code{LDD_SUFFIX}. If the line lists a dynamic dependency, the | |
6151 | code must advance @var{PTR} to the beginning of the filename on that | |
6152 | line. Otherwise, it must set @var{PTR} to @code{NULL}. | |
6153 | ||
6154 | @end table | |
6155 | ||
6156 | @node Instruction Output | |
6157 | @subsection Output of Assembler Instructions | |
6158 | ||
6159 | @c prevent bad page break with this line | |
6160 | This describes assembler instruction output. | |
6161 | ||
6162 | @table @code | |
6163 | @findex REGISTER_NAMES | |
6164 | @item REGISTER_NAMES | |
6165 | A C initializer containing the assembler's names for the machine | |
6166 | registers, each one as a C string constant. This is what translates | |
6167 | register numbers in the compiler into assembler language. | |
6168 | ||
6169 | @findex ADDITIONAL_REGISTER_NAMES | |
6170 | @item ADDITIONAL_REGISTER_NAMES | |
6171 | If defined, a C initializer for an array of structures containing a name | |
6172 | and a register number. This macro defines additional names for hard | |
6173 | registers, thus allowing the @code{asm} option in declarations to refer | |
6174 | to registers using alternate names. | |
6175 | ||
6176 | @findex ASM_OUTPUT_OPCODE | |
6177 | @item ASM_OUTPUT_OPCODE (@var{stream}, @var{ptr}) | |
6178 | Define this macro if you are using an unusual assembler that | |
6179 | requires different names for the machine instructions. | |
6180 | ||
6181 | The definition is a C statement or statements which output an | |
6182 | assembler instruction opcode to the stdio stream @var{stream}. The | |
6183 | macro-operand @var{ptr} is a variable of type @code{char *} which | |
6184 | points to the opcode name in its ``internal'' form---the form that is | |
6185 | written in the machine description. The definition should output the | |
6186 | opcode name to @var{stream}, performing any translation you desire, and | |
6187 | increment the variable @var{ptr} to point at the end of the opcode | |
6188 | so that it will not be output twice. | |
6189 | ||
6190 | In fact, your macro definition may process less than the entire opcode | |
6191 | name, or more than the opcode name; but if you want to process text | |
6192 | that includes @samp{%}-sequences to substitute operands, you must take | |
6193 | care of the substitution yourself. Just be sure to increment | |
6194 | @var{ptr} over whatever text should not be output normally. | |
6195 | ||
6196 | @findex recog_operand | |
6197 | If you need to look at the operand values, they can be found as the | |
6198 | elements of @code{recog_operand}. | |
6199 | ||
6200 | If the macro definition does nothing, the instruction is output | |
6201 | in the usual way. | |
6202 | ||
6203 | @findex FINAL_PRESCAN_INSN | |
6204 | @item FINAL_PRESCAN_INSN (@var{insn}, @var{opvec}, @var{noperands}) | |
6205 | If defined, a C statement to be executed just prior to the output of | |
6206 | assembler code for @var{insn}, to modify the extracted operands so | |
6207 | they will be output differently. | |
6208 | ||
6209 | Here the argument @var{opvec} is the vector containing the operands | |
6210 | extracted from @var{insn}, and @var{noperands} is the number of | |
6211 | elements of the vector which contain meaningful data for this insn. | |
6212 | The contents of this vector are what will be used to convert the insn | |
6213 | template into assembler code, so you can change the assembler output | |
6214 | by changing the contents of the vector. | |
6215 | ||
6216 | This macro is useful when various assembler syntaxes share a single | |
6217 | file of instruction patterns; by defining this macro differently, you | |
6218 | can cause a large class of instructions to be output differently (such | |
6219 | as with rearranged operands). Naturally, variations in assembler | |
6220 | syntax affecting individual insn patterns ought to be handled by | |
6221 | writing conditional output routines in those patterns. | |
6222 | ||
6223 | If this macro is not defined, it is equivalent to a null statement. | |
6224 | ||
6225 | @findex FINAL_PRESCAN_LABEL | |
6226 | @item FINAL_PRESCAN_LABEL | |
6227 | If defined, @code{FINAL_PRESCAN_INSN} will be called on each | |
6228 | @code{CODE_LABEL}. In that case, @var{opvec} will be a null pointer and | |
6229 | @var{noperands} will be zero. | |
6230 | ||
6231 | @findex PRINT_OPERAND | |
6232 | @item PRINT_OPERAND (@var{stream}, @var{x}, @var{code}) | |
6233 | A C compound statement to output to stdio stream @var{stream} the | |
6234 | assembler syntax for an instruction operand @var{x}. @var{x} is an | |
6235 | RTL expression. | |
6236 | ||
6237 | @var{code} is a value that can be used to specify one of several ways | |
6238 | of printing the operand. It is used when identical operands must be | |
6239 | printed differently depending on the context. @var{code} comes from | |
6240 | the @samp{%} specification that was used to request printing of the | |
6241 | operand. If the specification was just @samp{%@var{digit}} then | |
6242 | @var{code} is 0; if the specification was @samp{%@var{ltr} | |
6243 | @var{digit}} then @var{code} is the ASCII code for @var{ltr}. | |
6244 | ||
6245 | @findex reg_names | |
6246 | If @var{x} is a register, this macro should print the register's name. | |
6247 | The names can be found in an array @code{reg_names} whose type is | |
6248 | @code{char *[]}. @code{reg_names} is initialized from | |
6249 | @code{REGISTER_NAMES}. | |
6250 | ||
6251 | When the machine description has a specification @samp{%@var{punct}} | |
6252 | (a @samp{%} followed by a punctuation character), this macro is called | |
6253 | with a null pointer for @var{x} and the punctuation character for | |
6254 | @var{code}. | |
6255 | ||
6256 | @findex PRINT_OPERAND_PUNCT_VALID_P | |
6257 | @item PRINT_OPERAND_PUNCT_VALID_P (@var{code}) | |
6258 | A C expression which evaluates to true if @var{code} is a valid | |
6259 | punctuation character for use in the @code{PRINT_OPERAND} macro. If | |
6260 | @code{PRINT_OPERAND_PUNCT_VALID_P} is not defined, it means that no | |
6261 | punctuation characters (except for the standard one, @samp{%}) are used | |
6262 | in this way. | |
6263 | ||
6264 | @findex PRINT_OPERAND_ADDRESS | |
6265 | @item PRINT_OPERAND_ADDRESS (@var{stream}, @var{x}) | |
6266 | A C compound statement to output to stdio stream @var{stream} the | |
6267 | assembler syntax for an instruction operand that is a memory reference | |
6268 | whose address is @var{x}. @var{x} is an RTL expression. | |
6269 | ||
6270 | @cindex @code{ENCODE_SECTION_INFO} usage | |
6271 | On some machines, the syntax for a symbolic address depends on the | |
6272 | section that the address refers to. On these machines, define the macro | |
6273 | @code{ENCODE_SECTION_INFO} to store the information into the | |
6274 | @code{symbol_ref}, and then check for it here. @xref{Assembler Format}. | |
6275 | ||
6276 | @findex DBR_OUTPUT_SEQEND | |
6277 | @findex dbr_sequence_length | |
6278 | @item DBR_OUTPUT_SEQEND(@var{file}) | |
6279 | A C statement, to be executed after all slot-filler instructions have | |
6280 | been output. If necessary, call @code{dbr_sequence_length} to | |
6281 | determine the number of slots filled in a sequence (zero if not | |
6282 | currently outputting a sequence), to decide how many no-ops to output, | |
6283 | or whatever. | |
6284 | ||
6285 | Don't define this macro if it has nothing to do, but it is helpful in | |
6286 | reading assembly output if the extent of the delay sequence is made | |
6287 | explicit (e.g. with white space). | |
6288 | ||
6289 | @findex final_sequence | |
6290 | Note that output routines for instructions with delay slots must be | |
6291 | prepared to deal with not being output as part of a sequence (i.e. | |
6292 | when the scheduling pass is not run, or when no slot fillers could be | |
6293 | found.) The variable @code{final_sequence} is null when not | |
6294 | processing a sequence, otherwise it contains the @code{sequence} rtx | |
6295 | being output. | |
6296 | ||
6297 | @findex REGISTER_PREFIX | |
6298 | @findex LOCAL_LABEL_PREFIX | |
6299 | @findex USER_LABEL_PREFIX | |
6300 | @findex IMMEDIATE_PREFIX | |
6301 | @findex asm_fprintf | |
6302 | @item REGISTER_PREFIX | |
6303 | @itemx LOCAL_LABEL_PREFIX | |
6304 | @itemx USER_LABEL_PREFIX | |
6305 | @itemx IMMEDIATE_PREFIX | |
6306 | If defined, C string expressions to be used for the @samp{%R}, @samp{%L}, | |
6307 | @samp{%U}, and @samp{%I} options of @code{asm_fprintf} (see | |
6308 | @file{final.c}). These are useful when a single @file{md} file must | |
6309 | support multiple assembler formats. In that case, the various @file{tm.h} | |
6310 | files can define these macros differently. | |
6311 | ||
fe0503ea NC |
6312 | @item ASM_FPRINTF_EXTENSIONS(@var{file}, @var{argptr}, @var{format}) |
6313 | @findex ASM_FPRINTF_EXTENSIONS | |
6314 | If defiend this macro should expand to a series of @code{case} | |
6315 | statements which will be parsed inside the @code{switch} statement of | |
6316 | the @code{asm_fprintf} function. This allows targets to define extra | |
6317 | printf formats which may useful when generating their assembler | |
6318 | statements. Noet that upper case letters are reserved for future | |
6319 | generic extensions to asm_fprintf, and so are not available to target | |
6320 | specific code. The output file is given by the parameter @var{file}. | |
6321 | The varargs input pointer is @var{argptr} and the rest of the format | |
6322 | string, starting the character after the one that is being switched | |
6323 | upon, is pointed to by @var{format}. | |
6324 | ||
feca2ed3 JW |
6325 | @findex ASSEMBLER_DIALECT |
6326 | @item ASSEMBLER_DIALECT | |
6327 | If your target supports multiple dialects of assembler language (such as | |
6328 | different opcodes), define this macro as a C expression that gives the | |
6329 | numeric index of the assembler language dialect to use, with zero as the | |
6330 | first variant. | |
6331 | ||
6332 | If this macro is defined, you may use constructs of the form | |
6333 | @samp{@{option0|option1|option2@dots{}@}} in the output | |
6334 | templates of patterns (@pxref{Output Template}) or in the first argument | |
6335 | of @code{asm_fprintf}. This construct outputs @samp{option0}, | |
6336 | @samp{option1} or @samp{option2}, etc., if the value of | |
6337 | @code{ASSEMBLER_DIALECT} is zero, one or two, etc. Any special | |
6338 | characters within these strings retain their usual meaning. | |
6339 | ||
6340 | If you do not define this macro, the characters @samp{@{}, @samp{|} and | |
6341 | @samp{@}} do not have any special meaning when used in templates or | |
6342 | operands to @code{asm_fprintf}. | |
6343 | ||
6344 | Define the macros @code{REGISTER_PREFIX}, @code{LOCAL_LABEL_PREFIX}, | |
6345 | @code{USER_LABEL_PREFIX} and @code{IMMEDIATE_PREFIX} if you can express | |
e5e809f4 | 6346 | the variations in assembler language syntax with that mechanism. Define |
feca2ed3 JW |
6347 | @code{ASSEMBLER_DIALECT} and use the @samp{@{option0|option1@}} syntax |
6348 | if the syntax variant are larger and involve such things as different | |
6349 | opcodes or operand order. | |
6350 | ||
6351 | @findex ASM_OUTPUT_REG_PUSH | |
6352 | @item ASM_OUTPUT_REG_PUSH (@var{stream}, @var{regno}) | |
6353 | A C expression to output to @var{stream} some assembler code | |
6354 | which will push hard register number @var{regno} onto the stack. | |
6355 | The code need not be optimal, since this macro is used only when | |
6356 | profiling. | |
6357 | ||
6358 | @findex ASM_OUTPUT_REG_POP | |
6359 | @item ASM_OUTPUT_REG_POP (@var{stream}, @var{regno}) | |
6360 | A C expression to output to @var{stream} some assembler code | |
6361 | which will pop hard register number @var{regno} off of the stack. | |
6362 | The code need not be optimal, since this macro is used only when | |
6363 | profiling. | |
6364 | @end table | |
6365 | ||
6366 | @node Dispatch Tables | |
6367 | @subsection Output of Dispatch Tables | |
6368 | ||
6369 | @c prevent bad page break with this line | |
6370 | This concerns dispatch tables. | |
6371 | ||
6372 | @table @code | |
6373 | @cindex dispatch table | |
6374 | @findex ASM_OUTPUT_ADDR_DIFF_ELT | |
33f7f353 | 6375 | @item ASM_OUTPUT_ADDR_DIFF_ELT (@var{stream}, @var{body}, @var{value}, @var{rel}) |
feca2ed3 JW |
6376 | A C statement to output to the stdio stream @var{stream} an assembler |
6377 | pseudo-instruction to generate a difference between two labels. | |
6378 | @var{value} and @var{rel} are the numbers of two internal labels. The | |
6379 | definitions of these labels are output using | |
6380 | @code{ASM_OUTPUT_INTERNAL_LABEL}, and they must be printed in the same | |
6381 | way here. For example, | |
6382 | ||
6383 | @example | |
6384 | fprintf (@var{stream}, "\t.word L%d-L%d\n", | |
6385 | @var{value}, @var{rel}) | |
6386 | @end example | |
6387 | ||
6388 | You must provide this macro on machines where the addresses in a | |
6389 | dispatch table are relative to the table's own address. If defined, GNU | |
6390 | CC will also use this macro on all machines when producing PIC. | |
33f7f353 JR |
6391 | @var{body} is the body of the ADDR_DIFF_VEC; it is provided so that the |
6392 | mode and flags can be read. | |
feca2ed3 JW |
6393 | |
6394 | @findex ASM_OUTPUT_ADDR_VEC_ELT | |
6395 | @item ASM_OUTPUT_ADDR_VEC_ELT (@var{stream}, @var{value}) | |
6396 | This macro should be provided on machines where the addresses | |
6397 | in a dispatch table are absolute. | |
6398 | ||
6399 | The definition should be a C statement to output to the stdio stream | |
6400 | @var{stream} an assembler pseudo-instruction to generate a reference to | |
6401 | a label. @var{value} is the number of an internal label whose | |
6402 | definition is output using @code{ASM_OUTPUT_INTERNAL_LABEL}. | |
6403 | For example, | |
6404 | ||
6405 | @example | |
6406 | fprintf (@var{stream}, "\t.word L%d\n", @var{value}) | |
6407 | @end example | |
6408 | ||
6409 | @findex ASM_OUTPUT_CASE_LABEL | |
6410 | @item ASM_OUTPUT_CASE_LABEL (@var{stream}, @var{prefix}, @var{num}, @var{table}) | |
6411 | Define this if the label before a jump-table needs to be output | |
6412 | specially. The first three arguments are the same as for | |
6413 | @code{ASM_OUTPUT_INTERNAL_LABEL}; the fourth argument is the | |
6414 | jump-table which follows (a @code{jump_insn} containing an | |
6415 | @code{addr_vec} or @code{addr_diff_vec}). | |
6416 | ||
6417 | This feature is used on system V to output a @code{swbeg} statement | |
6418 | for the table. | |
6419 | ||
6420 | If this macro is not defined, these labels are output with | |
6421 | @code{ASM_OUTPUT_INTERNAL_LABEL}. | |
6422 | ||
6423 | @findex ASM_OUTPUT_CASE_END | |
6424 | @item ASM_OUTPUT_CASE_END (@var{stream}, @var{num}, @var{table}) | |
6425 | Define this if something special must be output at the end of a | |
6426 | jump-table. The definition should be a C statement to be executed | |
6427 | after the assembler code for the table is written. It should write | |
6428 | the appropriate code to stdio stream @var{stream}. The argument | |
6429 | @var{table} is the jump-table insn, and @var{num} is the label-number | |
6430 | of the preceding label. | |
6431 | ||
6432 | If this macro is not defined, nothing special is output at the end of | |
6433 | the jump-table. | |
6434 | @end table | |
6435 | ||
6436 | @node Exception Region Output | |
6437 | @subsection Assembler Commands for Exception Regions | |
6438 | ||
6439 | @c prevent bad page break with this line | |
6440 | ||
6441 | This describes commands marking the start and the end of an exception | |
6442 | region. | |
6443 | ||
6444 | @table @code | |
6445 | @findex ASM_OUTPUT_EH_REGION_BEG | |
6446 | @item ASM_OUTPUT_EH_REGION_BEG () | |
6447 | A C expression to output text to mark the start of an exception region. | |
6448 | ||
6449 | This macro need not be defined on most platforms. | |
6450 | ||
6451 | @findex ASM_OUTPUT_EH_REGION_END | |
6452 | @item ASM_OUTPUT_EH_REGION_END () | |
6453 | A C expression to output text to mark the end of an exception region. | |
6454 | ||
6455 | This macro need not be defined on most platforms. | |
6456 | ||
0021b564 JM |
6457 | @findex EXCEPTION_SECTION |
6458 | @item EXCEPTION_SECTION () | |
6459 | A C expression to switch to the section in which the main | |
6460 | exception table is to be placed (@pxref{Sections}). The default is a | |
6461 | section named @code{.gcc_except_table} on machines that support named | |
6462 | sections via @code{ASM_OUTPUT_SECTION_NAME}, otherwise if @samp{-fpic} | |
6463 | or @samp{-fPIC} is in effect, the @code{data_section}, otherwise the | |
6464 | @code{readonly_data_section}. | |
6465 | ||
6466 | @findex EH_FRAME_SECTION_ASM_OP | |
6467 | @item EH_FRAME_SECTION_ASM_OP | |
6468 | If defined, a C string constant for the assembler operation to switch to | |
6469 | the section for exception handling frame unwind information. If not | |
a3a15b4d | 6470 | defined, GCC will provide a default definition if the target supports |
0021b564 JM |
6471 | named sections. @file{crtstuff.c} uses this macro to switch to the |
6472 | appropriate section. | |
6473 | ||
6474 | You should define this symbol if your target supports DWARF 2 frame | |
6475 | unwind information and the default definition does not work. | |
6476 | ||
feca2ed3 JW |
6477 | @findex OMIT_EH_TABLE |
6478 | @item OMIT_EH_TABLE () | |
6479 | A C expression that is nonzero if the normal exception table output | |
6480 | should be omitted. | |
6481 | ||
6482 | This macro need not be defined on most platforms. | |
6483 | ||
6484 | @findex EH_TABLE_LOOKUP | |
6485 | @item EH_TABLE_LOOKUP () | |
6486 | Alternate runtime support for looking up an exception at runtime and | |
6487 | finding the associated handler, if the default method won't work. | |
6488 | ||
6489 | This macro need not be defined on most platforms. | |
6490 | ||
6491 | @findex DOESNT_NEED_UNWINDER | |
6492 | @item DOESNT_NEED_UNWINDER | |
6493 | A C expression that decides whether or not the current function needs to | |
6494 | have a function unwinder generated for it. See the file @code{except.c} | |
6495 | for details on when to define this, and how. | |
6496 | ||
6497 | @findex MASK_RETURN_ADDR | |
6498 | @item MASK_RETURN_ADDR | |
6499 | An rtx used to mask the return address found via RETURN_ADDR_RTX, so | |
6500 | that it does not contain any extraneous set bits in it. | |
0021b564 JM |
6501 | |
6502 | @findex DWARF2_UNWIND_INFO | |
6503 | @item DWARF2_UNWIND_INFO | |
6504 | Define this macro to 0 if your target supports DWARF 2 frame unwind | |
6505 | information, but it does not yet work with exception handling. | |
6506 | Otherwise, if your target supports this information (if it defines | |
6507 | @samp{INCOMING_RETURN_ADDR_RTX} and either @samp{UNALIGNED_INT_ASM_OP} | |
6508 | or @samp{OBJECT_FORMAT_ELF}), GCC will provide a default definition of | |
6509 | 1. | |
6510 | ||
6511 | If this macro is defined to 1, the DWARF 2 unwinder will be the default | |
6512 | exception handling mechanism; otherwise, setjmp/longjmp will be used by | |
6513 | default. | |
6514 | ||
6515 | If this macro is defined to anything, the DWARF 2 unwinder will be used | |
6516 | instead of inline unwinders and __unwind_function in the non-setjmp case. | |
6517 | ||
feca2ed3 JW |
6518 | @end table |
6519 | ||
6520 | @node Alignment Output | |
6521 | @subsection Assembler Commands for Alignment | |
6522 | ||
6523 | @c prevent bad page break with this line | |
6524 | This describes commands for alignment. | |
6525 | ||
6526 | @table @code | |
fc470718 R |
6527 | @findex LABEL_ALIGN_AFTER_BARRIER |
6528 | @item LABEL_ALIGN_AFTER_BARRIER (@var{label}) | |
6529 | The alignment (log base 2) to put in front of @var{label}, which follows | |
6530 | a BARRIER. | |
feca2ed3 JW |
6531 | |
6532 | This macro need not be defined if you don't want any special alignment | |
6533 | to be done at such a time. Most machine descriptions do not currently | |
6534 | define the macro. | |
6535 | ||
efa3896a GK |
6536 | Unless it's necessary to inspect the @var{label} parameter, it is better |
6537 | to set the variable @var{align_jumps} in the target's | |
6538 | @code{OVERRIDE_OPTIONS}. Otherwise, you should try to honour the user's | |
6539 | selection in @var{align_jumps} in a @code{LABEL_ALIGN_AFTER_BARRIER} | |
6540 | implementation. | |
6541 | ||
6542 | @findex LABEL_ALIGN_AFTER_BARRIER_MAX_SKIP | |
6543 | @item LABEL_ALIGN_AFTER_BARRIER_MAX_SKIP | |
6544 | The maximum number of bytes to skip when applying | |
6545 | @code{LABEL_ALIGN_AFTER_BARRIER}. This works only if | |
6546 | @code{ASM_OUTPUT_MAX_SKIP_ALIGN} is defined. | |
6547 | ||
fc470718 R |
6548 | @findex LOOP_ALIGN |
6549 | @item LOOP_ALIGN (@var{label}) | |
6550 | The alignment (log base 2) to put in front of @var{label}, which follows | |
6551 | a NOTE_INSN_LOOP_BEG note. | |
feca2ed3 JW |
6552 | |
6553 | This macro need not be defined if you don't want any special alignment | |
6554 | to be done at such a time. Most machine descriptions do not currently | |
6555 | define the macro. | |
6556 | ||
efa3896a GK |
6557 | Unless it's necessary to inspect the @var{label} parameter, it is better |
6558 | to set the variable @var{align_loops} in the target's | |
6559 | @code{OVERRIDE_OPTIONS}. Otherwise, you should try to honour the user's | |
6560 | selection in @var{align_loops} in a @code{LOOP_ALIGN} implementation. | |
6561 | ||
6562 | @findex LOOP_ALIGN_MAX_SKIP | |
6563 | @item LOOP_ALIGN_MAX_SKIP | |
6564 | The maximum number of bytes to skip when applying @code{LOOP_ALIGN}. | |
6565 | This works only if @code{ASM_OUTPUT_MAX_SKIP_ALIGN} is defined. | |
6566 | ||
fc470718 R |
6567 | @findex LABEL_ALIGN |
6568 | @item LABEL_ALIGN (@var{label}) | |
6569 | The alignment (log base 2) to put in front of @var{label}. | |
6570 | If LABEL_ALIGN_AFTER_BARRIER / LOOP_ALIGN specify a different alignment, | |
6571 | the maximum of the specified values is used. | |
6572 | ||
efa3896a GK |
6573 | Unless it's necessary to inspect the @var{label} parameter, it is better |
6574 | to set the variable @var{align_labels} in the target's | |
6575 | @code{OVERRIDE_OPTIONS}. Otherwise, you should try to honour the user's | |
6576 | selection in @var{align_labels} in a @code{LABEL_ALIGN} implementation. | |
6577 | ||
6578 | @findex LABEL_ALIGN_MAX_SKIP | |
6579 | @item LABEL_ALIGN_MAX_SKIP | |
6580 | The maximum number of bytes to skip when applying @code{LABEL_ALIGN}. | |
6581 | This works only if @code{ASM_OUTPUT_MAX_SKIP_ALIGN} is defined. | |
6582 | ||
feca2ed3 JW |
6583 | @findex ASM_OUTPUT_SKIP |
6584 | @item ASM_OUTPUT_SKIP (@var{stream}, @var{nbytes}) | |
6585 | A C statement to output to the stdio stream @var{stream} an assembler | |
6586 | instruction to advance the location counter by @var{nbytes} bytes. | |
6587 | Those bytes should be zero when loaded. @var{nbytes} will be a C | |
6588 | expression of type @code{int}. | |
6589 | ||
6590 | @findex ASM_NO_SKIP_IN_TEXT | |
6591 | @item ASM_NO_SKIP_IN_TEXT | |
6592 | Define this macro if @code{ASM_OUTPUT_SKIP} should not be used in the | |
556e0f21 | 6593 | text section because it fails to put zeros in the bytes that are skipped. |
feca2ed3 JW |
6594 | This is true on many Unix systems, where the pseudo--op to skip bytes |
6595 | produces no-op instructions rather than zeros when used in the text | |
6596 | section. | |
6597 | ||
6598 | @findex ASM_OUTPUT_ALIGN | |
6599 | @item ASM_OUTPUT_ALIGN (@var{stream}, @var{power}) | |
6600 | A C statement to output to the stdio stream @var{stream} an assembler | |
6601 | command to advance the location counter to a multiple of 2 to the | |
6602 | @var{power} bytes. @var{power} will be a C expression of type @code{int}. | |
26f63a77 JL |
6603 | |
6604 | @findex ASM_OUTPUT_MAX_SKIP_ALIGN | |
6605 | @item ASM_OUTPUT_MAX_SKIP_ALIGN (@var{stream}, @var{power}, @var{max_skip}) | |
6606 | A C statement to output to the stdio stream @var{stream} an assembler | |
6607 | command to advance the location counter to a multiple of 2 to the | |
6608 | @var{power} bytes, but only if @var{max_skip} or fewer bytes are needed to | |
6609 | satisfy the alignment request. @var{power} and @var{max_skip} will be | |
6610 | a C expression of type @code{int}. | |
feca2ed3 JW |
6611 | @end table |
6612 | ||
6613 | @need 3000 | |
6614 | @node Debugging Info | |
6615 | @section Controlling Debugging Information Format | |
6616 | ||
6617 | @c prevent bad page break with this line | |
6618 | This describes how to specify debugging information. | |
6619 | ||
6620 | @menu | |
6621 | * All Debuggers:: Macros that affect all debugging formats uniformly. | |
6622 | * DBX Options:: Macros enabling specific options in DBX format. | |
6623 | * DBX Hooks:: Hook macros for varying DBX format. | |
6624 | * File Names and DBX:: Macros controlling output of file names in DBX format. | |
6625 | * SDB and DWARF:: Macros for SDB (COFF) and DWARF formats. | |
6626 | @end menu | |
6627 | ||
6628 | @node All Debuggers | |
6629 | @subsection Macros Affecting All Debugging Formats | |
6630 | ||
6631 | @c prevent bad page break with this line | |
6632 | These macros affect all debugging formats. | |
6633 | ||
6634 | @table @code | |
6635 | @findex DBX_REGISTER_NUMBER | |
6636 | @item DBX_REGISTER_NUMBER (@var{regno}) | |
6637 | A C expression that returns the DBX register number for the compiler | |
6638 | register number @var{regno}. In simple cases, the value of this | |
6639 | expression may be @var{regno} itself. But sometimes there are some | |
6640 | registers that the compiler knows about and DBX does not, or vice | |
6641 | versa. In such cases, some register may need to have one number in | |
6642 | the compiler and another for DBX. | |
6643 | ||
a3a15b4d | 6644 | If two registers have consecutive numbers inside GCC, and they can be |
feca2ed3 JW |
6645 | used as a pair to hold a multiword value, then they @emph{must} have |
6646 | consecutive numbers after renumbering with @code{DBX_REGISTER_NUMBER}. | |
6647 | Otherwise, debuggers will be unable to access such a pair, because they | |
6648 | expect register pairs to be consecutive in their own numbering scheme. | |
6649 | ||
6650 | If you find yourself defining @code{DBX_REGISTER_NUMBER} in way that | |
6651 | does not preserve register pairs, then what you must do instead is | |
6652 | redefine the actual register numbering scheme. | |
6653 | ||
6654 | @findex DEBUGGER_AUTO_OFFSET | |
6655 | @item DEBUGGER_AUTO_OFFSET (@var{x}) | |
6656 | A C expression that returns the integer offset value for an automatic | |
6657 | variable having address @var{x} (an RTL expression). The default | |
6658 | computation assumes that @var{x} is based on the frame-pointer and | |
6659 | gives the offset from the frame-pointer. This is required for targets | |
6660 | that produce debugging output for DBX or COFF-style debugging output | |
6661 | for SDB and allow the frame-pointer to be eliminated when the | |
6662 | @samp{-g} options is used. | |
6663 | ||
6664 | @findex DEBUGGER_ARG_OFFSET | |
6665 | @item DEBUGGER_ARG_OFFSET (@var{offset}, @var{x}) | |
6666 | A C expression that returns the integer offset value for an argument | |
6667 | having address @var{x} (an RTL expression). The nominal offset is | |
6668 | @var{offset}. | |
6669 | ||
6670 | @findex PREFERRED_DEBUGGING_TYPE | |
6671 | @item PREFERRED_DEBUGGING_TYPE | |
a3a15b4d | 6672 | A C expression that returns the type of debugging output GCC should |
e5e809f4 | 6673 | produce when the user specifies just @samp{-g}. Define |
a3a15b4d | 6674 | this if you have arranged for GCC to support more than one format of |
e5e809f4 | 6675 | debugging output. Currently, the allowable values are @code{DBX_DEBUG}, |
f3ff3f4a JM |
6676 | @code{SDB_DEBUG}, @code{DWARF_DEBUG}, @code{DWARF2_DEBUG}, and |
6677 | @code{XCOFF_DEBUG}. | |
feca2ed3 | 6678 | |
a3a15b4d | 6679 | When the user specifies @samp{-ggdb}, GCC normally also uses the |
e5e809f4 JL |
6680 | value of this macro to select the debugging output format, but with two |
6681 | exceptions. If @code{DWARF2_DEBUGGING_INFO} is defined and | |
a3a15b4d | 6682 | @code{LINKER_DOES_NOT_WORK_WITH_DWARF2} is not defined, GCC uses the |
e5e809f4 | 6683 | value @code{DWARF2_DEBUG}. Otherwise, if @code{DBX_DEBUGGING_INFO} is |
a3a15b4d | 6684 | defined, GCC uses @code{DBX_DEBUG}. |
deabc777 | 6685 | |
feca2ed3 JW |
6686 | The value of this macro only affects the default debugging output; the |
6687 | user can always get a specific type of output by using @samp{-gstabs}, | |
f3ff3f4a | 6688 | @samp{-gcoff}, @samp{-gdwarf-1}, @samp{-gdwarf-2}, or @samp{-gxcoff}. |
feca2ed3 JW |
6689 | @end table |
6690 | ||
6691 | @node DBX Options | |
6692 | @subsection Specific Options for DBX Output | |
6693 | ||
6694 | @c prevent bad page break with this line | |
6695 | These are specific options for DBX output. | |
6696 | ||
6697 | @table @code | |
6698 | @findex DBX_DEBUGGING_INFO | |
6699 | @item DBX_DEBUGGING_INFO | |
a3a15b4d | 6700 | Define this macro if GCC should produce debugging output for DBX |
feca2ed3 JW |
6701 | in response to the @samp{-g} option. |
6702 | ||
6703 | @findex XCOFF_DEBUGGING_INFO | |
6704 | @item XCOFF_DEBUGGING_INFO | |
a3a15b4d | 6705 | Define this macro if GCC should produce XCOFF format debugging output |
feca2ed3 JW |
6706 | in response to the @samp{-g} option. This is a variant of DBX format. |
6707 | ||
6708 | @findex DEFAULT_GDB_EXTENSIONS | |
6709 | @item DEFAULT_GDB_EXTENSIONS | |
a3a15b4d | 6710 | Define this macro to control whether GCC should by default generate |
feca2ed3 JW |
6711 | GDB's extended version of DBX debugging information (assuming DBX-format |
6712 | debugging information is enabled at all). If you don't define the | |
6713 | macro, the default is 1: always generate the extended information | |
6714 | if there is any occasion to. | |
6715 | ||
6716 | @findex DEBUG_SYMS_TEXT | |
6717 | @item DEBUG_SYMS_TEXT | |
6718 | Define this macro if all @code{.stabs} commands should be output while | |
6719 | in the text section. | |
6720 | ||
6721 | @findex ASM_STABS_OP | |
6722 | @item ASM_STABS_OP | |
6723 | A C string constant naming the assembler pseudo op to use instead of | |
6724 | @code{.stabs} to define an ordinary debugging symbol. If you don't | |
6725 | define this macro, @code{.stabs} is used. This macro applies only to | |
6726 | DBX debugging information format. | |
6727 | ||
6728 | @findex ASM_STABD_OP | |
6729 | @item ASM_STABD_OP | |
6730 | A C string constant naming the assembler pseudo op to use instead of | |
6731 | @code{.stabd} to define a debugging symbol whose value is the current | |
6732 | location. If you don't define this macro, @code{.stabd} is used. | |
6733 | This macro applies only to DBX debugging information format. | |
6734 | ||
6735 | @findex ASM_STABN_OP | |
6736 | @item ASM_STABN_OP | |
6737 | A C string constant naming the assembler pseudo op to use instead of | |
6738 | @code{.stabn} to define a debugging symbol with no name. If you don't | |
6739 | define this macro, @code{.stabn} is used. This macro applies only to | |
6740 | DBX debugging information format. | |
6741 | ||
6742 | @findex DBX_NO_XREFS | |
6743 | @item DBX_NO_XREFS | |
6744 | Define this macro if DBX on your system does not support the construct | |
6745 | @samp{xs@var{tagname}}. On some systems, this construct is used to | |
6746 | describe a forward reference to a structure named @var{tagname}. | |
6747 | On other systems, this construct is not supported at all. | |
6748 | ||
6749 | @findex DBX_CONTIN_LENGTH | |
6750 | @item DBX_CONTIN_LENGTH | |
6751 | A symbol name in DBX-format debugging information is normally | |
6752 | continued (split into two separate @code{.stabs} directives) when it | |
6753 | exceeds a certain length (by default, 80 characters). On some | |
6754 | operating systems, DBX requires this splitting; on others, splitting | |
6755 | must not be done. You can inhibit splitting by defining this macro | |
6756 | with the value zero. You can override the default splitting-length by | |
6757 | defining this macro as an expression for the length you desire. | |
6758 | ||
6759 | @findex DBX_CONTIN_CHAR | |
6760 | @item DBX_CONTIN_CHAR | |
6761 | Normally continuation is indicated by adding a @samp{\} character to | |
6762 | the end of a @code{.stabs} string when a continuation follows. To use | |
6763 | a different character instead, define this macro as a character | |
6764 | constant for the character you want to use. Do not define this macro | |
6765 | if backslash is correct for your system. | |
6766 | ||
6767 | @findex DBX_STATIC_STAB_DATA_SECTION | |
6768 | @item DBX_STATIC_STAB_DATA_SECTION | |
6769 | Define this macro if it is necessary to go to the data section before | |
6770 | outputting the @samp{.stabs} pseudo-op for a non-global static | |
6771 | variable. | |
6772 | ||
6773 | @findex DBX_TYPE_DECL_STABS_CODE | |
6774 | @item DBX_TYPE_DECL_STABS_CODE | |
6775 | The value to use in the ``code'' field of the @code{.stabs} directive | |
6776 | for a typedef. The default is @code{N_LSYM}. | |
6777 | ||
6778 | @findex DBX_STATIC_CONST_VAR_CODE | |
6779 | @item DBX_STATIC_CONST_VAR_CODE | |
6780 | The value to use in the ``code'' field of the @code{.stabs} directive | |
6781 | for a static variable located in the text section. DBX format does not | |
6782 | provide any ``right'' way to do this. The default is @code{N_FUN}. | |
6783 | ||
6784 | @findex DBX_REGPARM_STABS_CODE | |
6785 | @item DBX_REGPARM_STABS_CODE | |
6786 | The value to use in the ``code'' field of the @code{.stabs} directive | |
6787 | for a parameter passed in registers. DBX format does not provide any | |
6788 | ``right'' way to do this. The default is @code{N_RSYM}. | |
6789 | ||
6790 | @findex DBX_REGPARM_STABS_LETTER | |
6791 | @item DBX_REGPARM_STABS_LETTER | |
6792 | The letter to use in DBX symbol data to identify a symbol as a parameter | |
6793 | passed in registers. DBX format does not customarily provide any way to | |
6794 | do this. The default is @code{'P'}. | |
6795 | ||
6796 | @findex DBX_MEMPARM_STABS_LETTER | |
6797 | @item DBX_MEMPARM_STABS_LETTER | |
6798 | The letter to use in DBX symbol data to identify a symbol as a stack | |
6799 | parameter. The default is @code{'p'}. | |
6800 | ||
6801 | @findex DBX_FUNCTION_FIRST | |
6802 | @item DBX_FUNCTION_FIRST | |
6803 | Define this macro if the DBX information for a function and its | |
6804 | arguments should precede the assembler code for the function. Normally, | |
6805 | in DBX format, the debugging information entirely follows the assembler | |
6806 | code. | |
6807 | ||
6808 | @findex DBX_LBRAC_FIRST | |
6809 | @item DBX_LBRAC_FIRST | |
6810 | Define this macro if the @code{N_LBRAC} symbol for a block should | |
6811 | precede the debugging information for variables and functions defined in | |
6812 | that block. Normally, in DBX format, the @code{N_LBRAC} symbol comes | |
6813 | first. | |
6814 | ||
6815 | @findex DBX_BLOCKS_FUNCTION_RELATIVE | |
6816 | @item DBX_BLOCKS_FUNCTION_RELATIVE | |
6817 | Define this macro if the value of a symbol describing the scope of a | |
6818 | block (@code{N_LBRAC} or @code{N_RBRAC}) should be relative to the start | |
6819 | of the enclosing function. Normally, GNU C uses an absolute address. | |
6820 | ||
6821 | @findex DBX_USE_BINCL | |
6822 | @item DBX_USE_BINCL | |
6823 | Define this macro if GNU C should generate @code{N_BINCL} and | |
6824 | @code{N_EINCL} stabs for included header files, as on Sun systems. This | |
6825 | macro also directs GNU C to output a type number as a pair of a file | |
6826 | number and a type number within the file. Normally, GNU C does not | |
6827 | generate @code{N_BINCL} or @code{N_EINCL} stabs, and it outputs a single | |
6828 | number for a type number. | |
6829 | @end table | |
6830 | ||
6831 | @node DBX Hooks | |
6832 | @subsection Open-Ended Hooks for DBX Format | |
6833 | ||
6834 | @c prevent bad page break with this line | |
6835 | These are hooks for DBX format. | |
6836 | ||
6837 | @table @code | |
6838 | @findex DBX_OUTPUT_LBRAC | |
6839 | @item DBX_OUTPUT_LBRAC (@var{stream}, @var{name}) | |
6840 | Define this macro to say how to output to @var{stream} the debugging | |
6841 | information for the start of a scope level for variable names. The | |
6842 | argument @var{name} is the name of an assembler symbol (for use with | |
6843 | @code{assemble_name}) whose value is the address where the scope begins. | |
6844 | ||
6845 | @findex DBX_OUTPUT_RBRAC | |
6846 | @item DBX_OUTPUT_RBRAC (@var{stream}, @var{name}) | |
6847 | Like @code{DBX_OUTPUT_LBRAC}, but for the end of a scope level. | |
6848 | ||
6849 | @findex DBX_OUTPUT_ENUM | |
6850 | @item DBX_OUTPUT_ENUM (@var{stream}, @var{type}) | |
6851 | Define this macro if the target machine requires special handling to | |
6852 | output an enumeration type. The definition should be a C statement | |
6853 | (sans semicolon) to output the appropriate information to @var{stream} | |
6854 | for the type @var{type}. | |
6855 | ||
6856 | @findex DBX_OUTPUT_FUNCTION_END | |
6857 | @item DBX_OUTPUT_FUNCTION_END (@var{stream}, @var{function}) | |
6858 | Define this macro if the target machine requires special output at the | |
6859 | end of the debugging information for a function. The definition should | |
6860 | be a C statement (sans semicolon) to output the appropriate information | |
6861 | to @var{stream}. @var{function} is the @code{FUNCTION_DECL} node for | |
6862 | the function. | |
6863 | ||
6864 | @findex DBX_OUTPUT_STANDARD_TYPES | |
6865 | @item DBX_OUTPUT_STANDARD_TYPES (@var{syms}) | |
6866 | Define this macro if you need to control the order of output of the | |
6867 | standard data types at the beginning of compilation. The argument | |
6868 | @var{syms} is a @code{tree} which is a chain of all the predefined | |
6869 | global symbols, including names of data types. | |
6870 | ||
6871 | Normally, DBX output starts with definitions of the types for integers | |
6872 | and characters, followed by all the other predefined types of the | |
6873 | particular language in no particular order. | |
6874 | ||
6875 | On some machines, it is necessary to output different particular types | |
6876 | first. To do this, define @code{DBX_OUTPUT_STANDARD_TYPES} to output | |
6877 | those symbols in the necessary order. Any predefined types that you | |
6878 | don't explicitly output will be output afterward in no particular order. | |
6879 | ||
6880 | Be careful not to define this macro so that it works only for C. There | |
6881 | are no global variables to access most of the built-in types, because | |
6882 | another language may have another set of types. The way to output a | |
6883 | particular type is to look through @var{syms} to see if you can find it. | |
6884 | Here is an example: | |
6885 | ||
6886 | @smallexample | |
6887 | @{ | |
6888 | tree decl; | |
6889 | for (decl = syms; decl; decl = TREE_CHAIN (decl)) | |
6890 | if (!strcmp (IDENTIFIER_POINTER (DECL_NAME (decl)), | |
6891 | "long int")) | |
6892 | dbxout_symbol (decl); | |
6893 | @dots{} | |
6894 | @} | |
6895 | @end smallexample | |
6896 | ||
6897 | @noindent | |
6898 | This does nothing if the expected type does not exist. | |
6899 | ||
6900 | See the function @code{init_decl_processing} in @file{c-decl.c} to find | |
6901 | the names to use for all the built-in C types. | |
6902 | ||
6903 | Here is another way of finding a particular type: | |
6904 | ||
6905 | @c this is still overfull. --mew 10feb93 | |
6906 | @smallexample | |
6907 | @{ | |
6908 | tree decl; | |
6909 | for (decl = syms; decl; decl = TREE_CHAIN (decl)) | |
6910 | if (TREE_CODE (decl) == TYPE_DECL | |
6911 | && (TREE_CODE (TREE_TYPE (decl)) | |
6912 | == INTEGER_CST) | |
6913 | && TYPE_PRECISION (TREE_TYPE (decl)) == 16 | |
6914 | && TYPE_UNSIGNED (TREE_TYPE (decl))) | |
6915 | @group | |
6916 | /* @r{This must be @code{unsigned short}.} */ | |
6917 | dbxout_symbol (decl); | |
6918 | @dots{} | |
6919 | @} | |
6920 | @end group | |
6921 | @end smallexample | |
6922 | ||
6923 | @findex NO_DBX_FUNCTION_END | |
6924 | @item NO_DBX_FUNCTION_END | |
6925 | Some stabs encapsulation formats (in particular ECOFF), cannot handle the | |
6926 | @code{.stabs "",N_FUN,,0,0,Lscope-function-1} gdb dbx extention construct. | |
6927 | On those machines, define this macro to turn this feature off without | |
6928 | disturbing the rest of the gdb extensions. | |
6929 | ||
6930 | @end table | |
6931 | ||
6932 | @node File Names and DBX | |
6933 | @subsection File Names in DBX Format | |
6934 | ||
6935 | @c prevent bad page break with this line | |
6936 | This describes file names in DBX format. | |
6937 | ||
6938 | @table @code | |
6939 | @findex DBX_WORKING_DIRECTORY | |
6940 | @item DBX_WORKING_DIRECTORY | |
6941 | Define this if DBX wants to have the current directory recorded in each | |
6942 | object file. | |
6943 | ||
6944 | Note that the working directory is always recorded if GDB extensions are | |
6945 | enabled. | |
6946 | ||
6947 | @findex DBX_OUTPUT_MAIN_SOURCE_FILENAME | |
6948 | @item DBX_OUTPUT_MAIN_SOURCE_FILENAME (@var{stream}, @var{name}) | |
6949 | A C statement to output DBX debugging information to the stdio stream | |
6950 | @var{stream} which indicates that file @var{name} is the main source | |
6951 | file---the file specified as the input file for compilation. | |
6952 | This macro is called only once, at the beginning of compilation. | |
6953 | ||
6954 | This macro need not be defined if the standard form of output | |
6955 | for DBX debugging information is appropriate. | |
6956 | ||
6957 | @findex DBX_OUTPUT_MAIN_SOURCE_DIRECTORY | |
6958 | @item DBX_OUTPUT_MAIN_SOURCE_DIRECTORY (@var{stream}, @var{name}) | |
6959 | A C statement to output DBX debugging information to the stdio stream | |
6960 | @var{stream} which indicates that the current directory during | |
6961 | compilation is named @var{name}. | |
6962 | ||
6963 | This macro need not be defined if the standard form of output | |
6964 | for DBX debugging information is appropriate. | |
6965 | ||
6966 | @findex DBX_OUTPUT_MAIN_SOURCE_FILE_END | |
6967 | @item DBX_OUTPUT_MAIN_SOURCE_FILE_END (@var{stream}, @var{name}) | |
6968 | A C statement to output DBX debugging information at the end of | |
6969 | compilation of the main source file @var{name}. | |
6970 | ||
6971 | If you don't define this macro, nothing special is output at the end | |
6972 | of compilation, which is correct for most machines. | |
6973 | ||
6974 | @findex DBX_OUTPUT_SOURCE_FILENAME | |
6975 | @item DBX_OUTPUT_SOURCE_FILENAME (@var{stream}, @var{name}) | |
6976 | A C statement to output DBX debugging information to the stdio stream | |
6977 | @var{stream} which indicates that file @var{name} is the current source | |
6978 | file. This output is generated each time input shifts to a different | |
6979 | source file as a result of @samp{#include}, the end of an included file, | |
6980 | or a @samp{#line} command. | |
6981 | ||
6982 | This macro need not be defined if the standard form of output | |
6983 | for DBX debugging information is appropriate. | |
6984 | @end table | |
6985 | ||
6986 | @need 2000 | |
6987 | @node SDB and DWARF | |
6988 | @subsection Macros for SDB and DWARF Output | |
6989 | ||
6990 | @c prevent bad page break with this line | |
6991 | Here are macros for SDB and DWARF output. | |
6992 | ||
6993 | @table @code | |
6994 | @findex SDB_DEBUGGING_INFO | |
6995 | @item SDB_DEBUGGING_INFO | |
a3a15b4d | 6996 | Define this macro if GCC should produce COFF-style debugging output |
feca2ed3 JW |
6997 | for SDB in response to the @samp{-g} option. |
6998 | ||
6999 | @findex DWARF_DEBUGGING_INFO | |
7000 | @item DWARF_DEBUGGING_INFO | |
a3a15b4d | 7001 | Define this macro if GCC should produce dwarf format debugging output |
feca2ed3 JW |
7002 | in response to the @samp{-g} option. |
7003 | ||
f3ff3f4a JM |
7004 | @findex DWARF2_DEBUGGING_INFO |
7005 | @item DWARF2_DEBUGGING_INFO | |
a3a15b4d | 7006 | Define this macro if GCC should produce dwarf version 2 format |
f3ff3f4a JM |
7007 | debugging output in response to the @samp{-g} option. |
7008 | ||
861bb6c1 JL |
7009 | To support optional call frame debugging information, you must also |
7010 | define @code{INCOMING_RETURN_ADDR_RTX} and either set | |
7011 | @code{RTX_FRAME_RELATED_P} on the prologue insns if you use RTL for the | |
7012 | prologue, or call @code{dwarf2out_def_cfa} and @code{dwarf2out_reg_save} | |
7013 | as appropriate from @code{FUNCTION_PROLOGUE} if you don't. | |
7014 | ||
9ec36da5 JL |
7015 | @findex DWARF2_FRAME_INFO |
7016 | @item DWARF2_FRAME_INFO | |
a3a15b4d | 7017 | Define this macro to a nonzero value if GCC should always output |
9ec36da5 | 7018 | Dwarf 2 frame information. If @code{DWARF2_UNWIND_INFO} |
a3a15b4d | 7019 | (@pxref{Exception Region Output} is nonzero, GCC will output this |
9ec36da5 JL |
7020 | information not matter how you define @code{DWARF2_FRAME_INFO}. |
7021 | ||
deabc777 PE |
7022 | @findex LINKER_DOES_NOT_WORK_WITH_DWARF2 |
7023 | @item LINKER_DOES_NOT_WORK_WITH_DWARF2 | |
e5e809f4 | 7024 | Define this macro if the linker does not work with Dwarf version 2. |
a3a15b4d | 7025 | Normally, if the user specifies only @samp{-ggdb} GCC will use Dwarf |
e5e809f4 JL |
7026 | version 2 if available; this macro disables this. See the description |
7027 | of the @code{PREFERRED_DEBUGGING_TYPE} macro for more details. | |
deabc777 | 7028 | |
b366352b MM |
7029 | @findex DWARF2_GENERATE_TEXT_SECTION_LABEL |
7030 | @item DWARF2_GENERATE_TEXT_SECTION_LABEL | |
7031 | By default, the Dwarf 2 debugging information generator will generate a | |
7032 | label to mark the beginning of the text section. If it is better simply | |
7033 | to use the name of the text section itself, rather than an explicit label, | |
7034 | to indicate the beginning of the text section, define this macro to zero. | |
7035 | ||
b2244e22 JW |
7036 | @findex DWARF2_ASM_LINE_DEBUG_INFO |
7037 | @item DWARF2_ASM_LINE_DEBUG_INFO | |
7038 | Define this macro to be a nonzero value if the assembler can generate Dwarf 2 | |
7039 | line debug info sections. This will result in much more compact line number | |
7040 | tables, and hence is desirable if it works. | |
7041 | ||
feca2ed3 JW |
7042 | @findex PUT_SDB_@dots{} |
7043 | @item PUT_SDB_@dots{} | |
7044 | Define these macros to override the assembler syntax for the special | |
7045 | SDB assembler directives. See @file{sdbout.c} for a list of these | |
7046 | macros and their arguments. If the standard syntax is used, you need | |
7047 | not define them yourself. | |
7048 | ||
7049 | @findex SDB_DELIM | |
7050 | @item SDB_DELIM | |
7051 | Some assemblers do not support a semicolon as a delimiter, even between | |
7052 | SDB assembler directives. In that case, define this macro to be the | |
7053 | delimiter to use (usually @samp{\n}). It is not necessary to define | |
7054 | a new set of @code{PUT_SDB_@var{op}} macros if this is the only change | |
7055 | required. | |
7056 | ||
7057 | @findex SDB_GENERATE_FAKE | |
7058 | @item SDB_GENERATE_FAKE | |
7059 | Define this macro to override the usual method of constructing a dummy | |
7060 | name for anonymous structure and union types. See @file{sdbout.c} for | |
7061 | more information. | |
7062 | ||
7063 | @findex SDB_ALLOW_UNKNOWN_REFERENCES | |
7064 | @item SDB_ALLOW_UNKNOWN_REFERENCES | |
7065 | Define this macro to allow references to unknown structure, | |
7066 | union, or enumeration tags to be emitted. Standard COFF does not | |
7067 | allow handling of unknown references, MIPS ECOFF has support for | |
7068 | it. | |
7069 | ||
7070 | @findex SDB_ALLOW_FORWARD_REFERENCES | |
7071 | @item SDB_ALLOW_FORWARD_REFERENCES | |
7072 | Define this macro to allow references to structure, union, or | |
7073 | enumeration tags that have not yet been seen to be handled. Some | |
7074 | assemblers choke if forward tags are used, while some require it. | |
7075 | @end table | |
7076 | ||
7077 | @node Cross-compilation | |
7078 | @section Cross Compilation and Floating Point | |
7079 | @cindex cross compilation and floating point | |
7080 | @cindex floating point and cross compilation | |
7081 | ||
7082 | While all modern machines use 2's complement representation for integers, | |
7083 | there are a variety of representations for floating point numbers. This | |
7084 | means that in a cross-compiler the representation of floating point numbers | |
7085 | in the compiled program may be different from that used in the machine | |
7086 | doing the compilation. | |
7087 | ||
7088 | @findex atof | |
7089 | Because different representation systems may offer different amounts of | |
7090 | range and precision, the cross compiler cannot safely use the host | |
7091 | machine's floating point arithmetic. Therefore, floating point constants | |
7092 | must be represented in the target machine's format. This means that the | |
7093 | cross compiler cannot use @code{atof} to parse a floating point constant; | |
7094 | it must have its own special routine to use instead. Also, constant | |
7095 | folding must emulate the target machine's arithmetic (or must not be done | |
7096 | at all). | |
7097 | ||
7098 | The macros in the following table should be defined only if you are cross | |
7099 | compiling between different floating point formats. | |
7100 | ||
7101 | Otherwise, don't define them. Then default definitions will be set up which | |
7102 | use @code{double} as the data type, @code{==} to test for equality, etc. | |
7103 | ||
7104 | You don't need to worry about how many times you use an operand of any | |
7105 | of these macros. The compiler never uses operands which have side effects. | |
7106 | ||
7107 | @table @code | |
7108 | @findex REAL_VALUE_TYPE | |
7109 | @item REAL_VALUE_TYPE | |
7110 | A macro for the C data type to be used to hold a floating point value | |
7111 | in the target machine's format. Typically this would be a | |
7112 | @code{struct} containing an array of @code{int}. | |
7113 | ||
7114 | @findex REAL_VALUES_EQUAL | |
7115 | @item REAL_VALUES_EQUAL (@var{x}, @var{y}) | |
7116 | A macro for a C expression which compares for equality the two values, | |
7117 | @var{x} and @var{y}, both of type @code{REAL_VALUE_TYPE}. | |
7118 | ||
7119 | @findex REAL_VALUES_LESS | |
7120 | @item REAL_VALUES_LESS (@var{x}, @var{y}) | |
7121 | A macro for a C expression which tests whether @var{x} is less than | |
7122 | @var{y}, both values being of type @code{REAL_VALUE_TYPE} and | |
7123 | interpreted as floating point numbers in the target machine's | |
7124 | representation. | |
7125 | ||
7126 | @findex REAL_VALUE_LDEXP | |
7127 | @findex ldexp | |
7128 | @item REAL_VALUE_LDEXP (@var{x}, @var{scale}) | |
7129 | A macro for a C expression which performs the standard library | |
7130 | function @code{ldexp}, but using the target machine's floating point | |
7131 | representation. Both @var{x} and the value of the expression have | |
7132 | type @code{REAL_VALUE_TYPE}. The second argument, @var{scale}, is an | |
7133 | integer. | |
7134 | ||
7135 | @findex REAL_VALUE_FIX | |
7136 | @item REAL_VALUE_FIX (@var{x}) | |
7137 | A macro whose definition is a C expression to convert the target-machine | |
7138 | floating point value @var{x} to a signed integer. @var{x} has type | |
7139 | @code{REAL_VALUE_TYPE}. | |
7140 | ||
7141 | @findex REAL_VALUE_UNSIGNED_FIX | |
7142 | @item REAL_VALUE_UNSIGNED_FIX (@var{x}) | |
7143 | A macro whose definition is a C expression to convert the target-machine | |
7144 | floating point value @var{x} to an unsigned integer. @var{x} has type | |
7145 | @code{REAL_VALUE_TYPE}. | |
7146 | ||
7147 | @findex REAL_VALUE_RNDZINT | |
7148 | @item REAL_VALUE_RNDZINT (@var{x}) | |
7149 | A macro whose definition is a C expression to round the target-machine | |
7150 | floating point value @var{x} towards zero to an integer value (but still | |
7151 | as a floating point number). @var{x} has type @code{REAL_VALUE_TYPE}, | |
7152 | and so does the value. | |
7153 | ||
7154 | @findex REAL_VALUE_UNSIGNED_RNDZINT | |
7155 | @item REAL_VALUE_UNSIGNED_RNDZINT (@var{x}) | |
7156 | A macro whose definition is a C expression to round the target-machine | |
7157 | floating point value @var{x} towards zero to an unsigned integer value | |
7158 | (but still represented as a floating point number). @var{x} has type | |
7159 | @code{REAL_VALUE_TYPE}, and so does the value. | |
7160 | ||
7161 | @findex REAL_VALUE_ATOF | |
7162 | @item REAL_VALUE_ATOF (@var{string}, @var{mode}) | |
7163 | A macro for a C expression which converts @var{string}, an expression of | |
7164 | type @code{char *}, into a floating point number in the target machine's | |
7165 | representation for mode @var{mode}. The value has type | |
7166 | @code{REAL_VALUE_TYPE}. | |
7167 | ||
7168 | @findex REAL_INFINITY | |
7169 | @item REAL_INFINITY | |
7170 | Define this macro if infinity is a possible floating point value, and | |
7171 | therefore division by 0 is legitimate. | |
7172 | ||
7173 | @findex REAL_VALUE_ISINF | |
7174 | @findex isinf | |
7175 | @item REAL_VALUE_ISINF (@var{x}) | |
7176 | A macro for a C expression which determines whether @var{x}, a floating | |
7177 | point value, is infinity. The value has type @code{int}. | |
7178 | By default, this is defined to call @code{isinf}. | |
7179 | ||
7180 | @findex REAL_VALUE_ISNAN | |
7181 | @findex isnan | |
7182 | @item REAL_VALUE_ISNAN (@var{x}) | |
7183 | A macro for a C expression which determines whether @var{x}, a floating | |
7184 | point value, is a ``nan'' (not-a-number). The value has type | |
7185 | @code{int}. By default, this is defined to call @code{isnan}. | |
7186 | @end table | |
7187 | ||
7188 | @cindex constant folding and floating point | |
7189 | Define the following additional macros if you want to make floating | |
7190 | point constant folding work while cross compiling. If you don't | |
7191 | define them, cross compilation is still possible, but constant folding | |
7192 | will not happen for floating point values. | |
7193 | ||
7194 | @table @code | |
7195 | @findex REAL_ARITHMETIC | |
7196 | @item REAL_ARITHMETIC (@var{output}, @var{code}, @var{x}, @var{y}) | |
7197 | A macro for a C statement which calculates an arithmetic operation of | |
7198 | the two floating point values @var{x} and @var{y}, both of type | |
7199 | @code{REAL_VALUE_TYPE} in the target machine's representation, to | |
7200 | produce a result of the same type and representation which is stored | |
7201 | in @var{output} (which will be a variable). | |
7202 | ||
7203 | The operation to be performed is specified by @var{code}, a tree code | |
7204 | which will always be one of the following: @code{PLUS_EXPR}, | |
7205 | @code{MINUS_EXPR}, @code{MULT_EXPR}, @code{RDIV_EXPR}, | |
7206 | @code{MAX_EXPR}, @code{MIN_EXPR}.@refill | |
7207 | ||
7208 | @cindex overflow while constant folding | |
7209 | The expansion of this macro is responsible for checking for overflow. | |
7210 | If overflow happens, the macro expansion should execute the statement | |
7211 | @code{return 0;}, which indicates the inability to perform the | |
7212 | arithmetic operation requested. | |
7213 | ||
7214 | @findex REAL_VALUE_NEGATE | |
7215 | @item REAL_VALUE_NEGATE (@var{x}) | |
7216 | A macro for a C expression which returns the negative of the floating | |
7217 | point value @var{x}. Both @var{x} and the value of the expression | |
7218 | have type @code{REAL_VALUE_TYPE} and are in the target machine's | |
7219 | floating point representation. | |
7220 | ||
7221 | There is no way for this macro to report overflow, since overflow | |
7222 | can't happen in the negation operation. | |
7223 | ||
7224 | @findex REAL_VALUE_TRUNCATE | |
7225 | @item REAL_VALUE_TRUNCATE (@var{mode}, @var{x}) | |
7226 | A macro for a C expression which converts the floating point value | |
7227 | @var{x} to mode @var{mode}. | |
7228 | ||
7229 | Both @var{x} and the value of the expression are in the target machine's | |
7230 | floating point representation and have type @code{REAL_VALUE_TYPE}. | |
7231 | However, the value should have an appropriate bit pattern to be output | |
7232 | properly as a floating constant whose precision accords with mode | |
7233 | @var{mode}. | |
7234 | ||
7235 | There is no way for this macro to report overflow. | |
7236 | ||
7237 | @findex REAL_VALUE_TO_INT | |
7238 | @item REAL_VALUE_TO_INT (@var{low}, @var{high}, @var{x}) | |
7239 | A macro for a C expression which converts a floating point value | |
7240 | @var{x} into a double-precision integer which is then stored into | |
7241 | @var{low} and @var{high}, two variables of type @var{int}. | |
7242 | ||
7243 | @item REAL_VALUE_FROM_INT (@var{x}, @var{low}, @var{high}, @var{mode}) | |
7244 | @findex REAL_VALUE_FROM_INT | |
7245 | A macro for a C expression which converts a double-precision integer | |
7246 | found in @var{low} and @var{high}, two variables of type @var{int}, | |
7247 | into a floating point value which is then stored into @var{x}. | |
7248 | The value is in the target machine's representation for mode @var{mode} | |
7249 | and has the type @code{REAL_VALUE_TYPE}. | |
7250 | @end table | |
7251 | ||
9f09b1f2 R |
7252 | @node Mode Switching |
7253 | @section Mode Switching Instructions | |
7254 | @cindex mode switching | |
7255 | The following macros control mode switching optimizations: | |
7256 | ||
7257 | @table @code | |
7258 | @findex OPTIMIZE_MODE_SWITCHING | |
7259 | @item OPTIMIZE_MODE_SWITCHING (@var{entity}) | |
7260 | Define this macro if the port needs extra instructions inserted for mode | |
7261 | switching in an optimizing compilation. | |
7262 | ||
7263 | For an example, the SH4 can perform both single and double precision | |
7264 | floating point operations, but to perform a single precision operation, | |
7265 | the FPSCR PR bit has to be cleared, while for a double precision | |
7266 | operation, this bit has to be set. Changing the PR bit requires a general | |
7267 | purpose register as a scratch register, hence these FPSCR sets have to | |
7268 | be inserted before reload, i.e. you can't put this into instruction emitting | |
7269 | or MACHINE_DEPENDENT_REORG. | |
7270 | ||
7271 | You can have multiple entities that are mode-switched, and select at run time | |
7272 | which entities actually need it. @code{OPTIMIZE_MODE_SWITCHING} should | |
7273 | return non-zero for any @var{entity} that that needs mode-switching. | |
7274 | If you define this macro, you also have to define | |
7275 | @code{NUM_MODES_FOR_MODE_SWITCHING}, @code{MODE_NEEDED}, | |
7276 | @code{MODE_PRIORITY_TO_MODE} and @code{EMIT_MODE_SET}. | |
7277 | @code{MODE_AT_ENTRY} and @code{MODE_USES_IN_EXIT_BLOCK} are optional. | |
7278 | ||
7279 | @findex NUM_MODES_FOR_MODE_SWITCHING | |
7280 | @item NUM_MODES_FOR_MODE_SWITCHING | |
7281 | If you define @code{OPTIMIZE_MODE_SWITCHING}, you have to define this as | |
7282 | initializer for an array of integers. Each initializer element | |
7283 | N refers to an entity that needs mode switching, and specifies the number | |
7284 | of different modes that might need to be set for this entity. | |
7285 | The position of the initializer in the initializer - starting counting at | |
7286 | zero - determines the integer that is used to refer to the mode-switched | |
7287 | entity in question. | |
7288 | In macros that take mode arguments / yield a mode result, modes are | |
7289 | represented as numbers 0 .. N - 1. N is used to specify that no mode | |
7290 | switch is needed / supplied. | |
7291 | ||
7292 | @findex MODE_USES_IN_EXIT_BLOCK | |
7293 | @item MODE_USES_IN_EXIT_BLOCK | |
7294 | If this macro is defined, it is called for each exit block when mode switching | |
7295 | optimization is performed. Its return value should be the pattern of an insn, | |
7296 | or a sequence of insns. It is emitted before the return insn / use insns at | |
7297 | the end of the exit block. | |
7298 | ||
7299 | This is done before insns are examined for their need of any mode switching. | |
7300 | ||
7301 | @findex MODE_NEEDED | |
7302 | @item MODE_NEEDED (@var{entity}, @var{insn}) | |
7303 | @var{entity} is an integer specifying a mode-switched entity. If | |
7304 | @code{OPTIMIZE_MODE_SWITCHING} is defined, you must define this macro to | |
7305 | return an integer value not larger than the corresponding element in | |
7306 | NUM_MODES_FOR_MODE_SWITCHING, to denote the mode that @var{entity} must | |
7307 | be switched into prior to the execution of INSN. | |
7308 | ||
7309 | @findex MODE_AT_ENTRY | |
7310 | @item MODE_AT_ENTRY (@var{entity}) | |
7311 | If this macro is defined, it is evaluated for every @var{entity} that needs | |
7312 | mode switching. It should evaluate to an integer, which is a mode that | |
7313 | @var{entity} is assumed to be switched to at function entry. | |
7314 | ||
7315 | @findex MODE_PRIORITY_TO_MODE | |
7316 | @item MODE_PRIORITY_TO_MODE (@var{entity}, @var{n}) | |
7317 | This macro specifies the order in which modes for ENTITY are processed. | |
7318 | 0 is the highest priority, NUM_MODES_FOR_MODE_SWITCHING[ENTITY] - 1 the | |
7319 | lowest. The value of the macro should be an integer designating a mode | |
7320 | for ENTITY. For any fixed @var{entity}, @code{mode_priority_to_mode} | |
7321 | (@var{entity}, @var{n}) shall be a bijection in 0 .. | |
7322 | @code{num_modes_for_mode_switching}[@var{entity}] - 1 . | |
7323 | ||
7324 | @findex EMIT_MODE_SET | |
7325 | @item EMIT_MODE_SET (@var{entity}, @var{mode}, @var{hard_regs_live}) | |
7326 | Generate one or more insns to set @var{entity} to @var{mode}. | |
7327 | @var{hard_reg_live} is the set of hard registers live at the point where | |
7328 | the insn(s) are to be inserted. | |
7329 | @end table | |
7330 | ||
feca2ed3 JW |
7331 | @node Misc |
7332 | @section Miscellaneous Parameters | |
7333 | @cindex parameters, miscellaneous | |
7334 | ||
7335 | @c prevent bad page break with this line | |
7336 | Here are several miscellaneous parameters. | |
7337 | ||
7338 | @table @code | |
7339 | @item PREDICATE_CODES | |
7340 | @findex PREDICATE_CODES | |
7341 | Define this if you have defined special-purpose predicates in the file | |
7342 | @file{@var{machine}.c}. This macro is called within an initializer of an | |
7343 | array of structures. The first field in the structure is the name of a | |
7344 | predicate and the second field is an array of rtl codes. For each | |
7345 | predicate, list all rtl codes that can be in expressions matched by the | |
7346 | predicate. The list should have a trailing comma. Here is an example | |
7347 | of two entries in the list for a typical RISC machine: | |
7348 | ||
7349 | @smallexample | |
7350 | #define PREDICATE_CODES \ | |
7351 | @{"gen_reg_rtx_operand", @{SUBREG, REG@}@}, \ | |
7352 | @{"reg_or_short_cint_operand", @{SUBREG, REG, CONST_INT@}@}, | |
7353 | @end smallexample | |
7354 | ||
7355 | Defining this macro does not affect the generated code (however, | |
7356 | incorrect definitions that omit an rtl code that may be matched by the | |
7357 | predicate can cause the compiler to malfunction). Instead, it allows | |
7358 | the table built by @file{genrecog} to be more compact and efficient, | |
7359 | thus speeding up the compiler. The most important predicates to include | |
556e0f21 | 7360 | in the list specified by this macro are those used in the most insn |
feca2ed3 JW |
7361 | patterns. |
7362 | ||
8fe0ca0c RH |
7363 | @item SPECIAL_MODE_PREDICATES |
7364 | @findex SPECIAL_MODE_PREDICATES | |
7365 | Define this if you have special predicates that know special things | |
7366 | about modes. Genrecog will warn about certain forms of | |
7367 | @code{match_operand} without a mode; if the operand predicate is | |
7368 | listed in @code{SPECIAL_MODE_PREDICATES}, the warning will be | |
7369 | suppressed. | |
7370 | ||
7371 | Here is an example from the IA-32 port (@code{ext_register_operand} | |
7372 | specially checks for @code{HImode} or @code{SImode} in preparation | |
7373 | for a byte extraction from @code{%ah} etc.). | |
7374 | ||
7375 | @smallexample | |
7376 | #define SPECIAL_MODE_PREDICATES \ | |
7377 | "ext_register_operand", | |
7378 | @end smallexample | |
7379 | ||
feca2ed3 JW |
7380 | @findex CASE_VECTOR_MODE |
7381 | @item CASE_VECTOR_MODE | |
7382 | An alias for a machine mode name. This is the machine mode that | |
7383 | elements of a jump-table should have. | |
7384 | ||
33f7f353 JR |
7385 | @findex CASE_VECTOR_SHORTEN_MODE |
7386 | @item CASE_VECTOR_SHORTEN_MODE (@var{min_offset}, @var{max_offset}, @var{body}) | |
7387 | Optional: return the preferred mode for an @code{addr_diff_vec} | |
7388 | when the minimum and maximum offset are known. If you define this, | |
7389 | it enables extra code in branch shortening to deal with @code{addr_diff_vec}. | |
7390 | To make this work, you also have to define INSN_ALIGN and | |
7391 | make the alignment for @code{addr_diff_vec} explicit. | |
391aaa6b | 7392 | The @var{body} argument is provided so that the offset_unsigned and scale |
33f7f353 JR |
7393 | flags can be updated. |
7394 | ||
feca2ed3 JW |
7395 | @findex CASE_VECTOR_PC_RELATIVE |
7396 | @item CASE_VECTOR_PC_RELATIVE | |
18543a22 ILT |
7397 | Define this macro to be a C expression to indicate when jump-tables |
7398 | should contain relative addresses. If jump-tables never contain | |
7399 | relative addresses, then you need not define this macro. | |
feca2ed3 JW |
7400 | |
7401 | @findex CASE_DROPS_THROUGH | |
7402 | @item CASE_DROPS_THROUGH | |
7403 | Define this if control falls through a @code{case} insn when the index | |
7404 | value is out of range. This means the specified default-label is | |
7405 | actually ignored by the @code{case} insn proper. | |
7406 | ||
7407 | @findex CASE_VALUES_THRESHOLD | |
7408 | @item CASE_VALUES_THRESHOLD | |
7409 | Define this to be the smallest number of different values for which it | |
7410 | is best to use a jump-table instead of a tree of conditional branches. | |
7411 | The default is four for machines with a @code{casesi} instruction and | |
7412 | five otherwise. This is best for most machines. | |
7413 | ||
7414 | @findex WORD_REGISTER_OPERATIONS | |
7415 | @item WORD_REGISTER_OPERATIONS | |
7416 | Define this macro if operations between registers with integral mode | |
7417 | smaller than a word are always performed on the entire register. | |
7418 | Most RISC machines have this property and most CISC machines do not. | |
7419 | ||
7420 | @findex LOAD_EXTEND_OP | |
7421 | @item LOAD_EXTEND_OP (@var{mode}) | |
7422 | Define this macro to be a C expression indicating when insns that read | |
7423 | memory in @var{mode}, an integral mode narrower than a word, set the | |
7424 | bits outside of @var{mode} to be either the sign-extension or the | |
7425 | zero-extension of the data read. Return @code{SIGN_EXTEND} for values | |
7426 | of @var{mode} for which the | |
7427 | insn sign-extends, @code{ZERO_EXTEND} for which it zero-extends, and | |
7428 | @code{NIL} for other modes. | |
7429 | ||
7430 | This macro is not called with @var{mode} non-integral or with a width | |
7431 | greater than or equal to @code{BITS_PER_WORD}, so you may return any | |
7432 | value in this case. Do not define this macro if it would always return | |
7433 | @code{NIL}. On machines where this macro is defined, you will normally | |
7434 | define it as the constant @code{SIGN_EXTEND} or @code{ZERO_EXTEND}. | |
7435 | ||
77643ab8 MM |
7436 | @findex SHORT_IMMEDIATES_SIGN_EXTEND |
7437 | @item SHORT_IMMEDIATES_SIGN_EXTEND | |
7438 | Define this macro if loading short immediate values into registers sign | |
7439 | extends. | |
7440 | ||
feca2ed3 JW |
7441 | @findex IMPLICIT_FIX_EXPR |
7442 | @item IMPLICIT_FIX_EXPR | |
7443 | An alias for a tree code that should be used by default for conversion | |
7444 | of floating point values to fixed point. Normally, | |
7445 | @code{FIX_ROUND_EXPR} is used.@refill | |
7446 | ||
7447 | @findex FIXUNS_TRUNC_LIKE_FIX_TRUNC | |
7448 | @item FIXUNS_TRUNC_LIKE_FIX_TRUNC | |
7449 | Define this macro if the same instructions that convert a floating | |
7450 | point number to a signed fixed point number also convert validly to an | |
7451 | unsigned one. | |
7452 | ||
7453 | @findex EASY_DIV_EXPR | |
7454 | @item EASY_DIV_EXPR | |
7455 | An alias for a tree code that is the easiest kind of division to | |
7456 | compile code for in the general case. It may be | |
7457 | @code{TRUNC_DIV_EXPR}, @code{FLOOR_DIV_EXPR}, @code{CEIL_DIV_EXPR} or | |
7458 | @code{ROUND_DIV_EXPR}. These four division operators differ in how | |
7459 | they round the result to an integer. @code{EASY_DIV_EXPR} is used | |
7460 | when it is permissible to use any of those kinds of division and the | |
7461 | choice should be made on the basis of efficiency.@refill | |
7462 | ||
7463 | @findex MOVE_MAX | |
7464 | @item MOVE_MAX | |
7465 | The maximum number of bytes that a single instruction can move quickly | |
7466 | between memory and registers or between two memory locations. | |
7467 | ||
7468 | @findex MAX_MOVE_MAX | |
7469 | @item MAX_MOVE_MAX | |
7470 | The maximum number of bytes that a single instruction can move quickly | |
7471 | between memory and registers or between two memory locations. If this | |
7472 | is undefined, the default is @code{MOVE_MAX}. Otherwise, it is the | |
7473 | constant value that is the largest value that @code{MOVE_MAX} can have | |
7474 | at run-time. | |
7475 | ||
7476 | @findex SHIFT_COUNT_TRUNCATED | |
7477 | @item SHIFT_COUNT_TRUNCATED | |
7478 | A C expression that is nonzero if on this machine the number of bits | |
7479 | actually used for the count of a shift operation is equal to the number | |
7480 | of bits needed to represent the size of the object being shifted. When | |
7481 | this macro is non-zero, the compiler will assume that it is safe to omit | |
7482 | a sign-extend, zero-extend, and certain bitwise `and' instructions that | |
7483 | truncates the count of a shift operation. On machines that have | |
7484 | instructions that act on bitfields at variable positions, which may | |
7485 | include `bit test' instructions, a nonzero @code{SHIFT_COUNT_TRUNCATED} | |
7486 | also enables deletion of truncations of the values that serve as | |
7487 | arguments to bitfield instructions. | |
7488 | ||
7489 | If both types of instructions truncate the count (for shifts) and | |
7490 | position (for bitfield operations), or if no variable-position bitfield | |
7491 | instructions exist, you should define this macro. | |
7492 | ||
7493 | However, on some machines, such as the 80386 and the 680x0, truncation | |
7494 | only applies to shift operations and not the (real or pretended) | |
7495 | bitfield operations. Define @code{SHIFT_COUNT_TRUNCATED} to be zero on | |
7496 | such machines. Instead, add patterns to the @file{md} file that include | |
7497 | the implied truncation of the shift instructions. | |
7498 | ||
7499 | You need not define this macro if it would always have the value of zero. | |
7500 | ||
7501 | @findex TRULY_NOOP_TRUNCATION | |
7502 | @item TRULY_NOOP_TRUNCATION (@var{outprec}, @var{inprec}) | |
7503 | A C expression which is nonzero if on this machine it is safe to | |
7504 | ``convert'' an integer of @var{inprec} bits to one of @var{outprec} | |
7505 | bits (where @var{outprec} is smaller than @var{inprec}) by merely | |
7506 | operating on it as if it had only @var{outprec} bits. | |
7507 | ||
7508 | On many machines, this expression can be 1. | |
7509 | ||
7510 | @c rearranged this, removed the phrase "it is reported that". this was | |
7511 | @c to fix an overfull hbox. --mew 10feb93 | |
7512 | When @code{TRULY_NOOP_TRUNCATION} returns 1 for a pair of sizes for | |
7513 | modes for which @code{MODES_TIEABLE_P} is 0, suboptimal code can result. | |
7514 | If this is the case, making @code{TRULY_NOOP_TRUNCATION} return 0 in | |
7515 | such cases may improve things. | |
7516 | ||
7517 | @findex STORE_FLAG_VALUE | |
7518 | @item STORE_FLAG_VALUE | |
7519 | A C expression describing the value returned by a comparison operator | |
7520 | with an integral mode and stored by a store-flag instruction | |
7521 | (@samp{s@var{cond}}) when the condition is true. This description must | |
7522 | apply to @emph{all} the @samp{s@var{cond}} patterns and all the | |
7523 | comparison operators whose results have a @code{MODE_INT} mode. | |
7524 | ||
7525 | A value of 1 or -1 means that the instruction implementing the | |
7526 | comparison operator returns exactly 1 or -1 when the comparison is true | |
7527 | and 0 when the comparison is false. Otherwise, the value indicates | |
7528 | which bits of the result are guaranteed to be 1 when the comparison is | |
7529 | true. This value is interpreted in the mode of the comparison | |
7530 | operation, which is given by the mode of the first operand in the | |
7531 | @samp{s@var{cond}} pattern. Either the low bit or the sign bit of | |
7532 | @code{STORE_FLAG_VALUE} be on. Presently, only those bits are used by | |
7533 | the compiler. | |
7534 | ||
7535 | If @code{STORE_FLAG_VALUE} is neither 1 or -1, the compiler will | |
7536 | generate code that depends only on the specified bits. It can also | |
7537 | replace comparison operators with equivalent operations if they cause | |
7538 | the required bits to be set, even if the remaining bits are undefined. | |
7539 | For example, on a machine whose comparison operators return an | |
7540 | @code{SImode} value and where @code{STORE_FLAG_VALUE} is defined as | |
7541 | @samp{0x80000000}, saying that just the sign bit is relevant, the | |
7542 | expression | |
7543 | ||
7544 | @smallexample | |
7545 | (ne:SI (and:SI @var{x} (const_int @var{power-of-2})) (const_int 0)) | |
7546 | @end smallexample | |
7547 | ||
7548 | @noindent | |
7549 | can be converted to | |
7550 | ||
7551 | @smallexample | |
7552 | (ashift:SI @var{x} (const_int @var{n})) | |
7553 | @end smallexample | |
7554 | ||
7555 | @noindent | |
7556 | where @var{n} is the appropriate shift count to move the bit being | |
7557 | tested into the sign bit. | |
7558 | ||
7559 | There is no way to describe a machine that always sets the low-order bit | |
7560 | for a true value, but does not guarantee the value of any other bits, | |
7561 | but we do not know of any machine that has such an instruction. If you | |
a3a15b4d | 7562 | are trying to port GCC to such a machine, include an instruction to |
feca2ed3 JW |
7563 | perform a logical-and of the result with 1 in the pattern for the |
7564 | comparison operators and let us know | |
7565 | @ifset USING | |
7566 | (@pxref{Bug Reporting,,How to Report Bugs}). | |
7567 | @end ifset | |
7568 | @ifclear USING | |
7569 | (@pxref{Bug Reporting,,How to Report Bugs,gcc.info,Using GCC}). | |
7570 | @end ifclear | |
7571 | ||
7572 | Often, a machine will have multiple instructions that obtain a value | |
7573 | from a comparison (or the condition codes). Here are rules to guide the | |
7574 | choice of value for @code{STORE_FLAG_VALUE}, and hence the instructions | |
7575 | to be used: | |
7576 | ||
7577 | @itemize @bullet | |
7578 | @item | |
7579 | Use the shortest sequence that yields a valid definition for | |
7580 | @code{STORE_FLAG_VALUE}. It is more efficient for the compiler to | |
7581 | ``normalize'' the value (convert it to, e.g., 1 or 0) than for the | |
7582 | comparison operators to do so because there may be opportunities to | |
7583 | combine the normalization with other operations. | |
7584 | ||
7585 | @item | |
7586 | For equal-length sequences, use a value of 1 or -1, with -1 being | |
7587 | slightly preferred on machines with expensive jumps and 1 preferred on | |
7588 | other machines. | |
7589 | ||
7590 | @item | |
7591 | As a second choice, choose a value of @samp{0x80000001} if instructions | |
7592 | exist that set both the sign and low-order bits but do not define the | |
7593 | others. | |
7594 | ||
7595 | @item | |
7596 | Otherwise, use a value of @samp{0x80000000}. | |
7597 | @end itemize | |
7598 | ||
7599 | Many machines can produce both the value chosen for | |
7600 | @code{STORE_FLAG_VALUE} and its negation in the same number of | |
7601 | instructions. On those machines, you should also define a pattern for | |
7602 | those cases, e.g., one matching | |
7603 | ||
7604 | @smallexample | |
7605 | (set @var{A} (neg:@var{m} (ne:@var{m} @var{B} @var{C}))) | |
7606 | @end smallexample | |
7607 | ||
7608 | Some machines can also perform @code{and} or @code{plus} operations on | |
7609 | condition code values with less instructions than the corresponding | |
7610 | @samp{s@var{cond}} insn followed by @code{and} or @code{plus}. On those | |
7611 | machines, define the appropriate patterns. Use the names @code{incscc} | |
7612 | and @code{decscc}, respectively, for the patterns which perform | |
7613 | @code{plus} or @code{minus} operations on condition code values. See | |
7614 | @file{rs6000.md} for some examples. The GNU Superoptizer can be used to | |
7615 | find such instruction sequences on other machines. | |
7616 | ||
7617 | You need not define @code{STORE_FLAG_VALUE} if the machine has no store-flag | |
7618 | instructions. | |
7619 | ||
7620 | @findex FLOAT_STORE_FLAG_VALUE | |
12530dbe RH |
7621 | @item FLOAT_STORE_FLAG_VALUE (@var{mode}) |
7622 | A C expression that gives a non-zero @code{REAL_VALUE_TYPE} value that is | |
feca2ed3 JW |
7623 | returned when comparison operators with floating-point results are true. |
7624 | Define this macro on machine that have comparison operations that return | |
7625 | floating-point values. If there are no such operations, do not define | |
7626 | this macro. | |
7627 | ||
7628 | @findex Pmode | |
7629 | @item Pmode | |
7630 | An alias for the machine mode for pointers. On most machines, define | |
7631 | this to be the integer mode corresponding to the width of a hardware | |
7632 | pointer; @code{SImode} on 32-bit machine or @code{DImode} on 64-bit machines. | |
7633 | On some machines you must define this to be one of the partial integer | |
7634 | modes, such as @code{PSImode}. | |
7635 | ||
7636 | The width of @code{Pmode} must be at least as large as the value of | |
7637 | @code{POINTER_SIZE}. If it is not equal, you must define the macro | |
7638 | @code{POINTERS_EXTEND_UNSIGNED} to specify how pointers are extended | |
7639 | to @code{Pmode}. | |
7640 | ||
7641 | @findex FUNCTION_MODE | |
7642 | @item FUNCTION_MODE | |
7643 | An alias for the machine mode used for memory references to functions | |
7644 | being called, in @code{call} RTL expressions. On most machines this | |
7645 | should be @code{QImode}. | |
7646 | ||
7647 | @findex INTEGRATE_THRESHOLD | |
7648 | @item INTEGRATE_THRESHOLD (@var{decl}) | |
7649 | A C expression for the maximum number of instructions above which the | |
7650 | function @var{decl} should not be inlined. @var{decl} is a | |
7651 | @code{FUNCTION_DECL} node. | |
7652 | ||
7653 | The default definition of this macro is 64 plus 8 times the number of | |
7654 | arguments that the function accepts. Some people think a larger | |
7655 | threshold should be used on RISC machines. | |
7656 | ||
7657 | @findex SCCS_DIRECTIVE | |
7658 | @item SCCS_DIRECTIVE | |
7659 | Define this if the preprocessor should ignore @code{#sccs} directives | |
7660 | and print no error message. | |
7661 | ||
7662 | @findex NO_IMPLICIT_EXTERN_C | |
7663 | @item NO_IMPLICIT_EXTERN_C | |
7664 | Define this macro if the system header files support C++ as well as C. | |
7665 | This macro inhibits the usual method of using system header files in | |
7666 | C++, which is to pretend that the file's contents are enclosed in | |
7667 | @samp{extern "C" @{@dots{}@}}. | |
7668 | ||
7669 | @findex HANDLE_PRAGMA | |
7670 | @findex #pragma | |
7671 | @findex pragma | |
e2af664c | 7672 | @item HANDLE_PRAGMA (@var{getc}, @var{ungetc}, @var{name}) |
feca2ed3 | 7673 | Define this macro if you want to implement any pragmas. If defined, it |
f09db6e0 | 7674 | is a C expression whose value is 1 if the pragma was handled by the |
e2af664c | 7675 | macro, zero otherwise. The argument @var{getc} is a function of type |
f09db6e0 NC |
7676 | @samp{int (*)(void)} which will return the next character in the input |
7677 | stream, or EOF if no characters are left. The argument @var{ungetc} is | |
7678 | a function of type @samp{void (*)(int)} which will push a character back | |
7679 | into the input stream. The argument @var{name} is the word following | |
7680 | #pragma in the input stream. The input stream pointer will be pointing | |
7681 | just beyond the end of this word. The input stream should be left | |
7682 | undistrubed if the expression returns zero, otherwise it should be | |
e2af664c NC |
7683 | pointing at the next character after the end of the pragma. Any |
7684 | characters remaining on the line will be ignored. | |
feca2ed3 JW |
7685 | |
7686 | It is generally a bad idea to implement new uses of @code{#pragma}. The | |
7687 | only reason to define this macro is for compatibility with other | |
7688 | compilers that do support @code{#pragma} for the sake of any user | |
7689 | programs which already use it. | |
7690 | ||
f09db6e0 NC |
7691 | If the pragma can be implemented by atttributes then the macro |
7692 | @samp{INSERT_ATTRIBUTES} might be a useful one to define as well. | |
7693 | ||
7694 | Note: older versions of this macro only had two arguments: @var{stream} | |
7695 | and @var{token}. The macro was changed in order to allow it to work | |
7696 | when gcc is built both with and without a cpp library. | |
7697 | ||
e2af664c NC |
7698 | @findex HANDLE_SYSV_PRAGMA |
7699 | @findex #pragma | |
7700 | @findex pragma | |
7701 | @item HANDLE_SYSV_PRAGMA | |
7702 | Define this macro (to a value of 1) if you want the System V style | |
7703 | pragmas @samp{#pragma pack(<n>)} and @samp{#pragma weak <name> | |
7704 | [=<value>]} to be supported by gcc. | |
7705 | ||
7706 | The pack pragma specifies the maximum alignment (in bytes) of fields | |
7707 | within a structure, in much the same way as the @samp{__aligned__} and | |
7708 | @samp{__packed__} @code{__attribute__}s do. A pack value of zero resets | |
7709 | the behaviour to the default. | |
7710 | ||
7711 | The weak pragma only works if @code{SUPPORTS_WEAK} and | |
7712 | @code{ASM_WEAKEN_LABEL} are defined. If enabled it allows the creation | |
7713 | of specifically named weak labels, optionally with a value. | |
7714 | ||
7715 | @findex HANDLE_PRAGMA_PACK_PUSH_POP | |
7716 | @findex #pragma | |
7717 | @findex pragma | |
7718 | @item HANDLE_PRAGMA_PACK_PUSH_POP | |
7719 | Define this macro (to a value of 1) if you want to support the Win32 | |
7720 | style pragmas @samp{#pragma pack(push,<n>)} and @samp{#pragma | |
7721 | pack(pop)}. The pack(push,<n>) pragma specifies the maximum alignment | |
7722 | (in bytes) of fields within a structure, in much the same way as the | |
7723 | @samp{__aligned__} and @samp{__packed__} @code{__attribute__}s do. A | |
7724 | pack value of zero resets the behaviour to the default. Successive | |
7725 | invocations of this pragma cause the previous values to be stacked, so | |
7726 | that invocations of @samp{#pragma pack(pop)} will return to the previous | |
7727 | value. | |
7728 | ||
feca2ed3 JW |
7729 | @findex VALID_MACHINE_DECL_ATTRIBUTE |
7730 | @item VALID_MACHINE_DECL_ATTRIBUTE (@var{decl}, @var{attributes}, @var{identifier}, @var{args}) | |
7731 | If defined, a C expression whose value is nonzero if @var{identifier} with | |
7732 | arguments @var{args} is a valid machine specific attribute for @var{decl}. | |
7733 | The attributes in @var{attributes} have previously been assigned to @var{decl}. | |
7734 | ||
7735 | @findex VALID_MACHINE_TYPE_ATTRIBUTE | |
7736 | @item VALID_MACHINE_TYPE_ATTRIBUTE (@var{type}, @var{attributes}, @var{identifier}, @var{args}) | |
7737 | If defined, a C expression whose value is nonzero if @var{identifier} with | |
7738 | arguments @var{args} is a valid machine specific attribute for @var{type}. | |
7739 | The attributes in @var{attributes} have previously been assigned to @var{type}. | |
7740 | ||
7741 | @findex COMP_TYPE_ATTRIBUTES | |
7742 | @item COMP_TYPE_ATTRIBUTES (@var{type1}, @var{type2}) | |
7743 | If defined, a C expression whose value is zero if the attributes on | |
7744 | @var{type1} and @var{type2} are incompatible, one if they are compatible, | |
7745 | and two if they are nearly compatible (which causes a warning to be | |
7746 | generated). | |
7747 | ||
7748 | @findex SET_DEFAULT_TYPE_ATTRIBUTES | |
7749 | @item SET_DEFAULT_TYPE_ATTRIBUTES (@var{type}) | |
7750 | If defined, a C statement that assigns default attributes to | |
7751 | newly defined @var{type}. | |
7752 | ||
d9525bec BK |
7753 | @findex MERGE_MACHINE_TYPE_ATTRIBUTES |
7754 | @item MERGE_MACHINE_TYPE_ATTRIBUTES (@var{type1}, @var{type2}) | |
7755 | Define this macro if the merging of type attributes needs special handling. | |
7756 | If defined, the result is a list of the combined TYPE_ATTRIBUTES of | |
7757 | @var{type1} and @var{type2}. It is assumed that comptypes has already been | |
7758 | called and returned 1. | |
7759 | ||
7760 | @findex MERGE_MACHINE_DECL_ATTRIBUTES | |
7761 | @item MERGE_MACHINE_DECL_ATTRIBUTES (@var{olddecl}, @var{newdecl}) | |
7762 | Define this macro if the merging of decl attributes needs special handling. | |
7763 | If defined, the result is a list of the combined DECL_MACHINE_ATTRIBUTES of | |
7764 | @var{olddecl} and @var{newdecl}. @var{newdecl} is a duplicate declaration | |
7765 | of @var{olddecl}. Examples of when this is needed are when one attribute | |
7766 | overrides another, or when an attribute is nullified by a subsequent | |
7767 | definition. | |
7768 | ||
f09db6e0 NC |
7769 | @findex INSERT_ATTRIBUTES |
7770 | @item INSERT_ATTRIBUTES (@var{node}, @var{attr_ptr}, @var{prefix_ptr}) | |
7771 | Define this macro if you want to be able to add attributes to a decl | |
7772 | when it is being created. This is normally useful for backends which | |
7773 | wish to implement a pragma by using the attributes which correspond to | |
7774 | the pragma's effect. The @var{node} argument is the decl which is being | |
7775 | created. The @var{attr_ptr} argument is a pointer to the attribute list | |
7776 | for this decl. The @var{prefix_ptr} is a pointer to the list of | |
7777 | attributes that have appeared after the specifiers and modifiers of the | |
7778 | declaration, but before the declaration proper. | |
7779 | ||
9ec36da5 JL |
7780 | @findex SET_DEFAULT_DECL_ATTRIBUTES |
7781 | @item SET_DEFAULT_DECL_ATTRIBUTES (@var{decl}, @var{attributes}) | |
7782 | If defined, a C statement that assigns default attributes to | |
7783 | newly defined @var{decl}. | |
7784 | ||
feca2ed3 JW |
7785 | @findex DOLLARS_IN_IDENTIFIERS |
7786 | @item DOLLARS_IN_IDENTIFIERS | |
7787 | Define this macro to control use of the character @samp{$} in identifier | |
37d13a29 | 7788 | names. 0 means @samp{$} is not allowed by default; 1 means it is allowed. |
feca2ed3 | 7789 | 1 is the default; there is no need to define this macro in that case. |
37d13a29 | 7790 | This macro controls the compiler proper; it does not affect the preprocessor. |
feca2ed3 JW |
7791 | |
7792 | @findex NO_DOLLAR_IN_LABEL | |
7793 | @item NO_DOLLAR_IN_LABEL | |
7794 | Define this macro if the assembler does not accept the character | |
7795 | @samp{$} in label names. By default constructors and destructors in | |
7796 | G++ have @samp{$} in the identifiers. If this macro is defined, | |
7797 | @samp{.} is used instead. | |
7798 | ||
7799 | @findex NO_DOT_IN_LABEL | |
7800 | @item NO_DOT_IN_LABEL | |
7801 | Define this macro if the assembler does not accept the character | |
7802 | @samp{.} in label names. By default constructors and destructors in G++ | |
7803 | have names that use @samp{.}. If this macro is defined, these names | |
7804 | are rewritten to avoid @samp{.}. | |
7805 | ||
7806 | @findex DEFAULT_MAIN_RETURN | |
7807 | @item DEFAULT_MAIN_RETURN | |
7808 | Define this macro if the target system expects every program's @code{main} | |
7809 | function to return a standard ``success'' value by default (if no other | |
7810 | value is explicitly returned). | |
7811 | ||
7812 | The definition should be a C statement (sans semicolon) to generate the | |
7813 | appropriate rtl instructions. It is used only when compiling the end of | |
7814 | @code{main}. | |
7815 | ||
c063dc98 JM |
7816 | @item NEED_ATEXIT |
7817 | @findex NEED_ATEXIT | |
7818 | Define this if the target system lacks the function @code{atexit} | |
7819 | from the ANSI C standard. If this macro is defined, a default definition | |
7820 | will be provided to support C++. If @code{ON_EXIT} is not defined, | |
7821 | a default @code{exit} function will also be provided. | |
7822 | ||
7823 | @item ON_EXIT | |
7824 | @findex ON_EXIT | |
7825 | Define this macro if the target has another way to implement atexit | |
7826 | functionality without replacing @code{exit}. For instance, SunOS 4 has | |
7827 | a similar @code{on_exit} library function. | |
7828 | ||
7829 | The definition should be a functional macro which can be used just like | |
7830 | the @code{atexit} function. | |
feca2ed3 JW |
7831 | |
7832 | @item EXIT_BODY | |
7833 | @findex EXIT_BODY | |
7834 | Define this if your @code{exit} function needs to do something | |
7835 | besides calling an external function @code{_cleanup} before | |
7836 | terminating with @code{_exit}. The @code{EXIT_BODY} macro is | |
e9a25f70 | 7837 | only needed if neither @code{HAVE_ATEXIT} nor |
feca2ed3 JW |
7838 | @code{INIT_SECTION_ASM_OP} are defined. |
7839 | ||
7840 | @findex INSN_SETS_ARE_DELAYED | |
7841 | @item INSN_SETS_ARE_DELAYED (@var{insn}) | |
7842 | Define this macro as a C expression that is nonzero if it is safe for the | |
7843 | delay slot scheduler to place instructions in the delay slot of @var{insn}, | |
7844 | even if they appear to use a resource set or clobbered in @var{insn}. | |
a3a15b4d | 7845 | @var{insn} is always a @code{jump_insn} or an @code{insn}; GCC knows that |
feca2ed3 JW |
7846 | every @code{call_insn} has this behavior. On machines where some @code{insn} |
7847 | or @code{jump_insn} is really a function call and hence has this behavior, | |
7848 | you should define this macro. | |
7849 | ||
7850 | You need not define this macro if it would always return zero. | |
7851 | ||
7852 | @findex INSN_REFERENCES_ARE_DELAYED | |
7853 | @item INSN_REFERENCES_ARE_DELAYED (@var{insn}) | |
7854 | Define this macro as a C expression that is nonzero if it is safe for the | |
7855 | delay slot scheduler to place instructions in the delay slot of @var{insn}, | |
7856 | even if they appear to set or clobber a resource referenced in @var{insn}. | |
7857 | @var{insn} is always a @code{jump_insn} or an @code{insn}. On machines where | |
7858 | some @code{insn} or @code{jump_insn} is really a function call and its operands | |
7859 | are registers whose use is actually in the subroutine it calls, you should | |
7860 | define this macro. Doing so allows the delay slot scheduler to move | |
7861 | instructions which copy arguments into the argument registers into the delay | |
7862 | slot of @var{insn}. | |
7863 | ||
7864 | You need not define this macro if it would always return zero. | |
7865 | ||
7866 | @findex MACHINE_DEPENDENT_REORG | |
7867 | @item MACHINE_DEPENDENT_REORG (@var{insn}) | |
7868 | In rare cases, correct code generation requires extra machine | |
7869 | dependent processing between the second jump optimization pass and | |
7870 | delayed branch scheduling. On those machines, define this macro as a C | |
7871 | statement to act on the code starting at @var{insn}. | |
7872 | ||
861bb6c1 JL |
7873 | @findex MULTIPLE_SYMBOL_SPACES |
7874 | @item MULTIPLE_SYMBOL_SPACES | |
7875 | Define this macro if in some cases global symbols from one translation | |
7876 | unit may not be bound to undefined symbols in another translation unit | |
7877 | without user intervention. For instance, under Microsoft Windows | |
7878 | symbols must be explicitly imported from shared libraries (DLLs). | |
7879 | ||
57bcb97a RH |
7880 | @findex MD_ASM_CLOBBERS |
7881 | @item MD_ASM_CLOBBERS | |
7882 | A C statement that adds to @var{CLOBBERS} @code{STRING_CST} trees for | |
7883 | any hard regs the port wishes to automatically clobber for all asms. | |
7884 | ||
70cfa7ad MM |
7885 | @findex ISSUE_RATE |
7886 | @item ISSUE_RATE | |
7887 | A C expression that returns how many instructions can be issued at the | |
a89608cb | 7888 | same time if the machine is a superscalar machine. |
70cfa7ad | 7889 | |
e4da5f6d | 7890 | @findex MD_SCHED_INIT |
5ea05bba | 7891 | @item MD_SCHED_INIT (@var{file}, @var{verbose}) |
a89608cb | 7892 | A C statement which is executed by the scheduler at the |
e4da5f6d MM |
7893 | beginning of each block of instructions that are to be scheduled. |
7894 | @var{file} is either a null pointer, or a stdio stream to write any | |
7895 | debug output to. @var{verbose} is the verbose level provided by | |
7896 | @samp{-fsched-verbose-}@var{n}. | |
7897 | ||
7898 | @findex MD_SCHED_REORDER | |
8760eaae | 7899 | @item MD_SCHED_REORDER (@var{file}, @var{verbose}, @var{ready}, @var{n_ready}, @var{clock}, @var{can_issue_more}) |
a89608cb | 7900 | A C statement which is executed by the scheduler after it |
e4da5f6d MM |
7901 | has scheduled the ready list to allow the machine description to reorder |
7902 | it (for example to combine two small instructions together on | |
7903 | @samp{VLIW} machines). @var{file} is either a null pointer, or a stdio | |
7904 | stream to write any debug output to. @var{verbose} is the verbose level | |
7905 | provided by @samp{-fsched-verbose-}@var{n}. @var{ready} is a pointer to | |
7906 | the ready list of instructions that are ready to be scheduled. | |
7907 | @var{n_ready} is the number of elements in the ready list. The | |
7908 | scheduler reads the ready list in reverse order, starting with | |
197043f5 RH |
7909 | @var{ready}[@var{n_ready}-1] and going to @var{ready}[0]. @var{clock} |
7910 | is the timer tick of the scheduler. @var{can_issue_more} is an output | |
7911 | parameter that is set to the number of insns that can issue this clock; | |
7912 | normally this is just @code{issue_rate}. | |
e4da5f6d MM |
7913 | |
7914 | @findex MD_SCHED_VARIABLE_ISSUE | |
7915 | @item MD_SCHED_VARIABLE_ISSUE (@var{file}, @var{verbose}, @var{insn}, @var{more}) | |
a89608cb | 7916 | A C statement which is executed by the scheduler after it |
e4da5f6d MM |
7917 | has scheduled an insn from the ready list. @var{file} is either a null |
7918 | pointer, or a stdio stream to write any debug output to. @var{verbose} | |
7919 | is the verbose level provided by @samp{-fsched-verbose-}@var{n}. | |
7920 | @var{insn} is the instruction that was scheduled. @var{more} is the | |
7921 | number of instructions that can be issued in the current cycle. The | |
7922 | @samp{MD_SCHED_VARIABLE_ISSUE} macro is responsible for updating the | |
7923 | value of @var{more} (typically by @var{more}--). | |
7924 | ||
dbecbbe4 JL |
7925 | @findex MAX_INTEGER_COMPUTATION_MODE |
7926 | @item MAX_INTEGER_COMPUTATION_MODE | |
7927 | Define this to the largest integer machine mode which can be used for | |
7928 | operations other than load, store and copy operations. | |
7929 | ||
7930 | You need only define this macro if the target holds values larger than | |
7931 | @code{word_mode} in general purpose registers. Most targets should not define | |
7932 | this macro. | |
f89223a9 | 7933 | |
71d718e0 JM |
7934 | @findex MATH_LIBRARY |
7935 | @item MATH_LIBRARY | |
7936 | Define this macro as a C string constant for the linker argument to link | |
7937 | in the system math library, or @samp{""} if the target does not have a | |
7938 | separate math library. | |
7939 | ||
7940 | You need only define this macro if the default of @samp{"-lm"} is wrong. | |
512b62fb JM |
7941 | |
7942 | @findex LIBRARY_PATH_ENV | |
7943 | @item LIBRARY_PATH_ENV | |
7944 | Define this macro as a C string constant for the environment variable that | |
7945 | specifies where the linker should look for libraries. | |
7946 | ||
7947 | You need only define this macro if the default of @samp{"LIBRARY_PATH"} | |
7948 | is wrong. | |
e09d24ff R |
7949 | |
7950 | @findex TARGET_HAS_F_SETLKW | |
7951 | @item TARGET_HAS_F_SETLKW | |
7952 | Define this macro iff the target supports file locking with fcntl / F_SETLKW. | |
7953 | Note that this functionality is part of POSIX. | |
7954 | Defining @code{TARGET_HAS_F_SETLKW} will enable the test coverage code | |
7955 | to use file locking when exiting a program, which avoids race conditions | |
7956 | if the program has forked. | |
0c99ec5c RH |
7957 | |
7958 | @findex MAX_CONDITIONAL_EXECUTE | |
7959 | @item MAX_CONDITIONAL_EXECUTE | |
7960 | ||
7961 | A C expression for the maximum number of instructions to execute via | |
7962 | conditional execution instructions instead of a branch. A value of | |
7963 | @code{BRANCH_COST}+1 is the default if the machine does not use cc0, and | |
7964 | 1 if it does use cc0. | |
feca2ed3 | 7965 | @end table |