Home
last modified time | relevance | path

Searched full:on (Results 1 – 25 of 2352) sorted by relevance

12345678910>>...95

/picolibc-latest/
DCOPYING.GPL245 software. If the software is modified by someone else and passed on, we
47 that any problems introduced by others will not reflect on the original
65 refers to any such program or work, and a "work based on the Program"
75 is covered only if its contents constitute a work based on the
77 Whether that is true depends on what the Program does.
81 conspicuously and appropriately publish on each copy an appropriate
91 of it, thus forming a work based on the Program, and copy and
111 does not normally print such an announcement, your work based on
120 on the Program, the distribution of the whole must be on the terms of
127 collective works based on the Program.
[all …]
DCMakeLists.txt30 # HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
86 option(FAST_STRCMP "Always optimize strcmp for performance" ON)
99 option(PICOLIBC_TLS "use thread local storage for static data" ON)
106 option(POSIX_IO "Provide fopen/fdopen using POSIX I/O (open, close, read, write, lseek)" ON)
114 set(default_prefer_size ON)
125 option(TINY_STDIO "Use tiny stdio from avr libc" ON)
355 option(_IO_FLOAT_EXACT "Provide exact binary/decimal conversion for printf/scanf" ON)
363 option(_ASSERT_VERBOSE "Assert provides verbose information" ON)
367 option(_PICOLIBC_ATOMIC_SIGNAL "Use atomics in signal/raise" ON)
376 option(_NANO_MALLOC "Use smaller malloc implementation" ON)
[all …]
DREADME.md174 * Set error flag when fgetc is called on an file without read
182 * Make fgets return any accumulated string on EOF instead of
187 return NULL/EOVERFLOW on overflow.
222 * Test on i386 native target.
253 * Enable MMU in picocrt on A profile ARM and AARCH64 targets when
358 multi-lib to check various FPU configurations on older and more
361 * Improve CI speed by using ccache on zephyr and mac tests,
372 * Fix a bunch of bugs on targets with 16-bit int type. Thanks to
375 * Work around a handful of platform bugs on MSP430. I think these are
379 * Run tests on MSP430 using the simulator that comes with gdb. Thanks to
[all …]
DCOPYING.NEWLIB45 PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
171 the new terms are clearly indicated on the first page of each file where
196 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
253 BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
279 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
305 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
331 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
374 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
401 OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
472 reliability, currentness, or otherwise; and you rely on the software,
[all …]
/picolibc-latest/newlib/libc/search/
Dndbm.c29 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
58 * *DBM on success
59 * NULL on failure
91 * DATUM on success
92 * NULL on failure
115 * DATUM on success
116 * NULL on failure
135 * DATUM on success
136 * NULL on failure
155 * 0 on success
[all …]
Dhash.h27 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
46 /* Define DB endianness constants based on target endianness. */
128 int cndx; /* Index of next item on cpage */
222 * PARTIAL_KEY This must be the first key/data pair on a page
224 * That is, the key is too big to fit on a single page
225 * so it starts on this page and continues on the next.
234 * FULL_KEY This must be the first key/data pair on the page. It
238 * There is a complete key on the page but no data
252 * data field, which is continued on the next page.
257 * KEY_OFF -- offset of the beginning of the data on
[all …]
/picolibc-latest/newlib/libc/stdio/
Dfopencookie.c42 <[functions.read]> should return -1 on failure, or else the number of
43 bytes read (0 on EOF). It is similar to <<read>>, except that
46 <[functions.write]> should return -1 on failure, or else the number of
50 <[functions.seek]> should return -1 on failure, and 0 on success, with
57 <[functions.close]> should return -1 on failure, or 0 on success. It
64 buffer on fully buffered or line buffered streams by calling
68 flag. They must also be prepared to have read or write calls occur on
72 The return value is an open FILE pointer on success. On error,
Dfunopen.c35 <[readfn]> should return -1 on failure, or else the number of bytes
36 read (0 on EOF). It is similar to <<read>>, except that <int> rather
41 <[writefn]> should return -1 on failure, or else the number of bytes
47 <[seekfn]> should return (fpos_t)-1 on failure, or else the current
54 <[closefn]> should return -1 on failure, or 0 on success. It is
60 buffer on fully buffered or line buffered streams by calling
64 flag. They must also be prepared to have read or write calls occur on
71 The return value is an open FILE pointer on success. On error,
Dstdio.tex24 The underlying facilities for input and output depend on the host
61 * Function fpurge:: Discard all pending I/O on a stream
62 * Function fputc:: Write a character on a stream or file
69 * Function __fsetlocking:: Set or query locking mode on FILE stream
86 * Function perror:: Print an error message on standard error
87 * Function putc:: Write a character on a stream or file (macro)
88 * Function putc_unlocked:: Write a character on a stream or file (macro)
89 * Function putchar:: Write a character on standard output (macro)
90 * Function putchar_unlocked:: Write a character on standard output (macro)
91 * Function puts:: Write a character string on standard output
Dsetvbuf.c41 Use full output buffering: output will be passed on to the host system
45 Use line buffering: pass on output to the host system at every
69 <<setvbuf>>. However, they differ on the meaning of a <<NULL>> buffer
74 Both specifications describe the result on failure only as a
103 * Verify arguments. The `int' limit on `size' is due to this in setvbuf()
174 * registered to flush buffers on exit. in setvbuf()
191 * Fix up the FILE fields, and set __cleanup for output flush on in setvbuf()
/picolibc-latest/newlib/
DREADME46 Newlib documentation is available on the net via:
52 on-line information and a printed manual. You can use one of the Info
53 formatting commands to create the on-line version of the documentation
67 use depends on your system; `lpr -d' is common; another (for PostScript
73 format. On its own, TeX cannot read, much less typeset a Texinfo file.
123 directories, you can run `make' on them in parallel (for example, if
124 they are NFS-mounted on each of the hosts); they will not interfere
135 script are based on a three-part naming scheme, but some short
149 you can use it to test your guesses on abbreviations--for example:
169 build: the platform on which gcc is built.
[all …]
/picolibc-latest/doc/
Dreleasing.md6 1. Make sure the current code builds on all supported architectures:
15 2. Test on architectures that can do so
36 4. Test c++ builds using hello-world example on ARM
73 14. Create new release on picolibc wiki pasting in relevant README.md
76 15. Create new release on github site, pasting in relevant README.md
84 Debian packaging information is contained on the 'debian' branch in
Dprintf.md3 Embedded systems are often tightly constrained on code space, which
12 link time based on knowledge of the requirements of the
20 definition must be set on the command line and not in a file.
74 -DPICOLIBC_FLOAT_PRINTF_SCANF on the command line during linking,
152 …$ qemu-system-arm -chardev stdio,id=stdio0 -semihosting-config enable=on,chardev=stdio0 -monitor n…
162 …$ qemu-system-arm -chardev stdio,id=stdio0 -semihosting-config enable=on,chardev=stdio0 -monitor n…
172 …$ qemu-system-arm -chardev stdio,id=stdio0 -semihosting-config enable=on,chardev=stdio0 -monitor n…
182 …$ qemu-system-arm -chardev stdio,id=stdio0 -semihosting-config enable=on,chardev=stdio0 -monitor n…
193 …$ qemu-system-arm -chardev stdio,id=stdio0 -semihosting-config enable=on,chardev=stdio0 -monitor n…
203 …$ qemu-system-arm -chardev stdio,id=stdio0 -semihosting-config enable=on,chardev=stdio0 -monitor n…
[all …]
/picolibc-latest/newlib/libc/machine/spu/
Dspu_timer_svcs.c25 INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
56 Returns the timer ID on success or <0 on Failure:
82 /* Initialize timer and put it on stopped list. */ in spu_timer_alloc()
98 __spu_timer_start(). Returns 0 on success and <0 on failure:
Dspu_clock_stop.c25 INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
41 Returns 0 on success and <0 on failure:
62 /* Clock is enabled on clock start - restore to original state (saved at start). */ in spu_clock_stop()
/picolibc-latest/.github/workflows/
Dlinux.yml3 on:
29 runs-on: ubuntu-latest
59 runs-on: ubuntu-latest
82 fail-on-cache-miss: true
99 # Key on job name and cache size to get separate caches for linux
114 runs-on: ubuntu-latest
142 fail-on-cache-miss: true
159 # Key on job name and cache size to get separate caches for linux
174 runs-on: ubuntu-latest
202 fail-on-cache-miss: true
[all …]
Dzephyr.yml3 on:
30 runs-on: ubuntu-latest
60 runs-on: ubuntu-latest
88 fail-on-cache-miss: true
105 # Key on job name and cache size to get separate caches for linux
120 runs-on: ubuntu-latest
148 fail-on-cache-miss: true
165 # Key on job name and cache size to get separate caches for linux
/picolibc-latest/hello-world/
DREADME.md43 default target code will run fine on a cortex-a57 processor as
94 application needs to land there. Picolibc on RISC-V puts _start at the
134 (`-semihosting-config enable=on`), disabling the monitor interface
140 qemu-system-arm -semihosting-config enable=on -monitor none
145 On aarch64, we use the 'virt' machine, which lets us plug in any
148 qemu-system-aarch64 -semihosting-config enable=on -monitor none
156 qemu-system-riscv32 -semihosting-config enable=on -monitor none
/picolibc-latest/newlib/libc/machine/spu/sys/
Derrno.h3 * The SPU must have these values match those on the PPU linux side, so
7 * This file is based on the CRIS file, with these modifications:
20 on which it is based, except values used or returned by syscalls must
68 #define ENOSPC 28 /* No space left on device */
109 #define ENONET 64 /* Machine is not on the network */
115 #define ECOMM 70 /* Communication error on send */
121 #define ENOTUNIQ 76 /* Name not unique on network */
133 #define ENOTSOCK 88 /* Socket operation on non-socket */
140 #define EOPNOTSUPP 95 /* Operation not supported on transport endpoint */
/picolibc-latest/scripts/
Drun-arm31 # HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
164 # Select a QEMU machine based on the CPU
233 echo "Skipping $elf: unsupported cpu on $machine"
244 chardev=stdio,mux=on,id=stdio0
276 semi=enable=on,chardev=stdio0,arg="$cmdline"
308 # when run on i686 processors
313 echo "fp imprecise for $cpu on" "$(uname -m)"
/picolibc-latest/newlib/libc/machine/powerpc/
Dsetjmp.S72 point stores are aligned on an 8 byte boundary and the Altivec
73 stores are aligned on a 16 byte boundary. */
124 /* If __SPE__, then add 84 to the offset shown from this point on until
131 # one word pad to get floating point aligned on 8 byte boundary
135 on its own would be enough for GCC 4.1 and above, but older
147 /* If __powerpc64__, then add 96 to the offset shown from this point on until
265 point loades are aligned on an 8 byte boundary and the Altivec
266 loads are aligned on a 16 byte boundary. */
315 /* If __SPE__, then add 84 to the offset shown from this point on until
324 # one word pad to get floating point aligned on 8 byte boundary
[all …]
/picolibc-latest/newlib/libc/machine/cris/sys/
Derrno.h24 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
30 on which it is based, except values used or returned by syscalls must
85 #define ENOSPC 28 /* No space left on device */
126 #define ENONET 64 /* Machine is not on the network */
132 #define ECOMM 70 /* Communication error on send */
138 #define ENOTUNIQ 76 /* Name not unique on network */
150 #define ENOTSOCK 88 /* Socket operation on non-socket */
157 #define EOPNOTSUPP 95 /* Operation not supported on transport endpoint */
/picolibc-latest/newlib/libc/string/
Dstrerror.c227 Machine is not on the network
236 No space left on device
263 Socket operation on non-socket
275 Operation not supported on socket
355 on <<_user_strerror>>), ANSI C declares that subsequent calls to
357 code cannot depend on the reentrancy of this subroutine.
361 on failure. Although POSIX allows <<strerror>> to set <<errno>>
362 to EINVAL on failure, this implementation does not do so (unless
595 error = "No space left on device"; in _strerror_r()
680 error = "Machine is not on the network"; in _strerror_r()
[all …]
/picolibc-latest/newlib/libc/machine/arm/
Dstrlen-armv7.S26 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
56 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
128 sel data1a, const_0, const_m1 /* Select based on GE<0:3>. */
137 sel data1a, const_0, const_m1 /* Select based on GE<0:3>. */
146 sel data1a, const_0, const_m1 /* Select based on GE<0:3>. */
156 sel data1a, const_0, const_m1 /* Select based on GE<0:3>. */
/picolibc-latest/newlib/libc/stdio64/
Dfdopen64.c69 /* POSIX recommends setting the O_APPEND bit on fd to match append in fdopen64()
70 streams. Someone may later clear O_APPEND on fileno(fp), but the in fdopen64()
71 stream must still remain in append mode. Rely on __sflags in fdopen64()
92 /* Explicit given mode results in explicit setting mode on fd */ in fdopen64()

12345678910>>...95