Specifies the name of the target Blackfin processor. Currently, cpu can be one of ‘bf512’, ‘bf514’, ‘bf516’, ‘bf518’, ‘bf522’, ‘bf523’, ‘bf524’, ‘bf525’, ‘bf526’, ‘bf527’, ‘bf531’, ‘bf532’, ‘bf533’, ‘bf534’, ‘bf536’, ‘bf537’, ‘bf538’, ‘bf539’, ‘bf542’, ‘bf544’, ‘bf547’, ‘bf548’, ‘bf549’, ‘bf542m’, ‘bf544m’, ‘bf547m’, ‘bf548m’, ‘bf549m’, ‘bf561’, ‘bf592’.
The optional sirevision specifies the silicon revision of the target Blackfin processor. Any workarounds available for the targeted silicon revision are enabled. If sirevision is ‘none’, no workarounds are enabled. If sirevision is ‘any’, all workarounds for the targeted processor are enabled. The
__SILICON_REVISION__ macro is defined to two hexadecimal digits representing the major and minor numbers in the silicon revision. If sirevision is ‘none’, the
__SILICON_REVISION__ is not defined. If sirevision is ‘any’, the
__SILICON_REVISION__ is defined to be
0xffff. If this optional sirevision is not used, GCC assumes the latest known silicon revision of the targeted Blackfin processor.
GCC defines a preprocessor macro for the specified cpu. For the ‘bfin-elf’ toolchain, this option causes the hardware BSP provided by libgloss to be linked in if -msim is not given.
Without this option, ‘bf532’ is used as the processor by default.
Note that support for ‘bf561’ is incomplete. For ‘bf561’, only the preprocessor macro is defined.
Specifies that the program will be run on the simulator. This causes the simulator BSP provided by libgloss to be linked in. This option has effect only for ‘bfin-elf’ toolchain. Certain other options, such as -mid-shared-library and -mfdpic, imply -msim.
Don’t keep the frame pointer in a register for leaf functions. This avoids the instructions to save, set up and restore frame pointers and makes an extra register available in leaf functions. The option -fomit-frame-pointer removes the frame pointer for all functions, which might make debugging harder.
When enabled, the compiler ensures that the generated code does not contain speculative loads after jump instructions. If this option is used,
__WORKAROUND_SPECULATIVE_LOADS is defined.
Don’t generate extra code to prevent speculative loads from occurring.
When enabled, the compiler ensures that the generated code does not contain CSYNC or SSYNC instructions too soon after conditional branches. If this option is used,
__WORKAROUND_SPECULATIVE_SYNCS is defined.
Don’t generate extra code to prevent CSYNC or SSYNC instructions from occurring too soon after a conditional branch.
When enabled, the compiler is free to take advantage of the knowledge that the entire program fits into the low 64k of memory.
Assume that the program is arbitrarily large. This is the default.
Do stack checking using information placed into L1 scratchpad memory by the uClinux kernel.
Generate code that allows the data segment to be located in a different area of memory from the text segment. This allows for execute in place in an environment without virtual memory management by eliminating relocations against the text section.
Generate code that assumes that the data segment follows the text segment. This is the default.
Tells the compiler to perform function calls by first loading the address of the function into a register and then performing a subroutine call on this register. This switch is needed if the target function lies outside of the 24-bit addressing range of the offset-based version of subroutine call instruction.
This feature is not enabled by default. Specifying -mno-long-calls restores the default behavior. Note these switches have no effect on how the compiler generates code to handle function calls via function pointers.
Link with the fast floating-point library. This library relaxes some of the IEEE floating-point standard’s rules for checking inputs against Not-a-Number (NAN), in the interest of performance.
Enable inlining of PLT entries in function calls to functions that are not known to bind locally. It has no effect without -mfdpic.
Build a standalone application for multicore Blackfin processors. This option causes proper start files and link scripts supporting multicore to be used, and defines the macro
__BFIN_MULTICORE. It can only be used with -mcpu=bf561[-sirevision].
This option can be used with -mcorea or -mcoreb, which selects the one-application-per-core programming model. Without -mcorea or -mcoreb, the single-application/dual-core programming model is used. In this model, the main function of Core B should be named as
If this option is not used, the single-core application programming model is used.
Build a standalone application for Core A of BF561 when using the one-application-per-core programming model. Proper start files and link scripts are used to support Core A, and the macro
__BFIN_COREA is defined. This option can only be used in conjunction with -mmulticore.
Build a standalone application for Core B of BF561 when using the one-application-per-core programming model. Proper start files and link scripts are used to support Core B, and the macro
__BFIN_COREB is defined. When this option is used,
coreb_main should be used instead of
main. This option can only be used in conjunction with -mmulticore.
Build a standalone application for SDRAM. Proper start files and link scripts are used to put the application into SDRAM, and the macro
__BFIN_SDRAM is defined. The loader should initialize SDRAM before loading the application.
Assume that ICPLBs are enabled at run time. This has an effect on certain anomaly workarounds. For Linux targets, the default is to assume ICPLBs are enabled; for standalone applications the default is off.
© Free Software Foundation
Licensed under the GNU Free Documentation License, Version 1.3.