Lines Matching +full:runs +full:- +full:on

23 the users have everything in place. But some third-party toolchains
25 it is not possible as these headers have compiler-specific parts and
38 	$ gcc --specs=picolibc.specs -c foo.c
45 	$ gcc --specs=/usr/local/picolibc/picolibc.specs -c foo.c
48 longer name for the compiler, something like `riscv-unknown-elf-gcc`
49 or `arm-none-eabi-gcc`.
54 hardware, run-time, library and application setup. You may want to
62 default when using -specs=picolibc.specs:
64 	$ gcc -specs=picolibc.specs -o foo.elf foo.c
69  1) Architecture-specific runtime initialization. For instance, RISC-V
120 designed to be useful for fairly simple applications running on
121 embedded hardware which need read-only code and data stored in flash
122 and read-write data allocated in RAM and initialized by picolibc at
123 boot time. You can read more about this on the [linking](linking.md)
139 libc. You can do this by using the GCC --oslib=semihost
142 	$ gcc --specs=picolibc.specs --oslib=semihost -o program.elf program.o
147 	$ gcc --specs=picolibc.specs -o program.elf program.o -lc -lsemihost
156 may want to use the `crt0-hosted` variant that calls `exit` when main
159 specification). Select this using the `--crt0=hosted` flag:
161 	$ gcc --specs=picolibc.specs --crt0=hosted -o program.elf program.o
165 `crt0-minimal` variant that removes the call to
166 `__libc_init_array()`. This variant also runs an infinite loop in case
167 main returns. Select this using the `--crt0=minimal` flag:
169 	$ gcc --specs=picolibc.specs --crt0=minimal -o program.elf program.o