Home
last modified time | relevance | path

Searched refs:system (Results 1 – 25 of 99) sorted by relevance

1234

/picolibc-latest/.github/
Dlinux-packages.txt33 qemu-system-x86
34 qemu-system-arm
35 qemu-system-misc
36 qemu-system-ppc64
Dzephyr-packages.txt13 qemu-system-x86
/picolibc-latest/scripts/
Drun-arc63 qemu=qemu-system-arc
67 qemu=qemu-system-arc64
70 qemu=qemu-system-arc
Dcross-xtensa-esp32-elf.txt9 system = 'unknown'
Dcross-xtensa-lx106-elf.txt9 system = 'esp8266'
Dcross-powerpc64-linux-gnu.txt9 system = 'linux'
Dcross-powerpc64le-linux-gnu.txt10 system = 'linux'
Dcross-m68k-unknown-elf.txt12 system = 'unknown'
Dcross-avr.txt14 system = 'none'
Dcross-clang-msp430.txt13 system = 'zephyr'
Dcross-xtensa-espressif_esp32_zephyr-elf.txt13 system = 'zephyr'
Dcross-xtensa-espressif_esp32s2_zephyr-elf.txt13 system = 'zephyr'
Dcross-xtensa-intel_apl_adsp_zephyr-elf.txt13 system = 'zephyr'
Dcross-xtensa-intel_s1000_zephyr-elf.txt13 system = 'zephyr'
Dcross-xtensa-nxp_imx8m_adsp_zephyr-elf.txt13 system = 'zephyr'
Dcross-xtensa-nxp_imx_adsp_zephyr-elf.txt13 system = 'zephyr'
Dcross-xtensa-sample_controller_zephyr-elf.txt13 system = 'zephyr'
Dcross-msp430.txt14 system = 'zephyr'
Dcross-m68k-linux-gnu.txt13 system = 'unknown'
/picolibc-latest/doc/
Dos.md3 Picolibc is designed to be operating-system independent, so it doesn't
4 embed any operating system support into libc. Some portions of
5 Picolibc need system support, like I/O and task termination.
9 Here's the full list of system functions used by Picolibc, split into
15 complex file operations so that a minimal system can easily support
30 __uart_putc(c); /* Defined by underlying system */
39 c = __uart_getc(); /* Defined by underlying system */
136 To get Picolibc to use a system library, that library needs to be
172 can actually build picolibc on a full POSIX system. In this
174 underlying system C library is used for the POSIX functions described
[all …]
Dusing.md4 running either no operating system or a small RTOS. It is designed to
5 be linked statically along with any operating system and application
34 file delivered with Picolibc. This will set the system header file
40 When installed directly into the system, picolibc.specs is placed in
47 When building for an embedded system, you'll probably need to use a
53 Initializing an embedded system usually requires a combination of
Dbuild.md6 build system, which is a slightly quirky build system designed to
10 system provides an older version, you can get the latest using
11 pip. For example, on a Debian or Ubuntu system, you would do:
18 system doesn't provide at least this version, head over to
26 the newlib code base and should match that configuration system. The
78 require that the underlying system offer the required functions. POSIX
101 on POSIX I/O functions from the underlying system, and perform many
129 | newlib-iconv-external-ccs | false | Use file system to store iconv tables. Requires fopen. (d…
211 | newlib-reentrant-syscalls-provided| false| Underlying system provides reentrant syscall API …
212 | newlib-missing-syscall-names| false | Underlying system provides syscall names without leading …
[all …]
/picolibc-latest/newlib/libc/
Dsys.tex7 operating system services. If you use the C library on a system that
9 these subroutines are supplied with your operating system.
11 If some of these subroutines are not provided with your system---in
13 system, without an OS---you will at least need to provide do-nothing
28 This is the complete set of system definitions (primarily subroutines)
63 Exit a program without cleaning up files. If your system doesn't
65 it (@code{exit}, @code{system}).
86 Transfer control to a new process. Minimal implementation (for a system
100 Create a new process. Minimal implementation (for a system without processes):
128 conflict with other processes. Minimal implementation, for a system
[all …]
/picolibc-latest/
Dcross.tmpl20 system = '@SYSTEM@'
/picolibc-latest/newlib/libc/stdlib/
Dsystem.c65 system (const char *s) in system() function

1234