Building an application for a non semihosting environment

The default C++ std::terminate() handler is required by the C++ Standard to call abort(). The default C library implementation of abort() uses functions that require semihosting support. Therefore, if you use exceptions in a non semihosted environment, you must provide an alternative implementation of abort().

Table 2.3 shows the functions that depend directly on semihosting.

_sys_command_string(),
_sys_close(), _sys_ensure(),
_sys_iserror(), _sys_istty(),
_sys_flen(), _sys_open(),
_sys_read(), _sys_seek(),
_sys_write(), _sys_tmpnam()

clock(),
_clock_init()remove(),
rename()system(), time()

Table 2.4 shows those functions that depend indirectly on one or more of the functions listed in Table 2.3.

__backspace(), fgetc(),
__stdin

fwrite(), fputs(), puts(),
fread(), fgets(), gets(),
ferror()

If you write an application in C, you must link it with the C library even if it makes no direct use of C library functions. The C library contains compiler helper functions and initialization code. Some C library functions use semihosting.

To avoid using semihosting, do either of the following:

To guarantee that no functions using semihosting are included in your application, use either:

If you include a semihosting‑using library function and also reference __use_no_semihosting, the library detects the conflicting symbols and the linker reports an error. To find out which objects are using semihosting, link with ‑‑verbose ‑‑list=out.txt, search the output for the symbol, and find out what object referenced it. See Controlling linker diagnostics in the Linker Guide for more information.

In addition to the semihosted functions listed in Table 2.3 and Table 2.4, Table 2.5 shows functions and files that might be useful when building for a different environment.

__main()
__rt_entry()

__rt_lib_init()
__rt_exit()
__rt_lib_shutdown()

If you are re‑implementing a function that exists in the standard ARM library, the linker uses an object or library from your project rather than the standard ARM library. Any library you add to a project does not have to follow the ARM library naming convention.