You copied the Doc URL to your clipboard.

Indirect semihosting C library function dependencies

Table 3 shows functions that depend indirectly on one or more of the functions listed in Table 2. You can use Table 3 as an initial guide, but ARM recommends that you use either of the following to identify any other functions with indirect or direct dependencies on semihosting at link time:

  • asm(" .global __use_no_semihosting\n"); in C source code.

  • IMPORT __use_no_semihosting in armasm assembly language source code.

Table 3. Indirect semihosting dependencies
FunctionUsage
__raise()
Catching, handling, or diagnosing C library exceptions, without C signal support. (Tailoring error signaling, error handling, and program exit.)
__default_signal_handler()
Catching, handling, or diagnosing C library exceptions, with C signal support. (Tailoring error signaling, error handling, and program exit.)
__Heap_Initialize()
Choosing or redefining memory allocation. Avoiding the heap and heap-using C library functions supplied by ARM.
ferror(), fputc(), __stdout
Re-implementing the printf family. (Tailoring input/output functions in the C and C++ libraries.).
__backspace(), fgetc(), __stdin
Re-implementing the scanf family. (Tailoring input/output functions in the C and C++ libraries.).
fwrite(), fputs(),
puts(),fread(), fgets(),
gets(), ferror()
Re-implementing the stream output family. (Tailoring input/output functions in the C and C++ libraries.).

Was this page helpful? Yes No