Home
last modified time | relevance | path

Searched refs:points (Results 1 – 25 of 100) sorted by relevance

1234

/glibc-2.36/benchtests/scripts/
Dimport_bench.py113 def compress_timings(points): argument
121 do_for_all_timings(points, split_list)
/glibc-2.36/sysdeps/arm/
Ddl-trampoline.S37 @ lr points to &GOT[2]
86 @ lr points to &GOT[2]
/glibc-2.36/localedata/unicode-gen/
DPropList.txt24 # Total code points: 25
33 # Total code points: 12
39 # Total code points: 2
67 # Total code points: 30
82 # Total code points: 11
115 # Total code points: 30
227 # Total code points: 276
408 # Total code points: 1362
419 # Total code points: 44
427 # Total code points: 22
[all …]
/glibc-2.36/sysdeps/arm/armv6t2/
Dmemchr.S128 @ r0 points to the start of the double word after the one that was tested
137 @ r0 currently points to the 2nd byte of the word containing the hit
/glibc-2.36/sysdeps/unix/sysv/linux/alpha/
Dsyscalls.list23 # timeval64 entry points (see osf_*.c for GLIBC_2.0 timeval32 equivalents)
/glibc-2.36/sysdeps/s390/s390-32/
Dstrncpy-z900.S34 slr %r2,%r3 # %r3 points to src, %r2+%r3 to dst
/glibc-2.36/sysdeps/s390/s390-64/
Dstrncpy-z900.S33 slgr %r2,%r3 # %r3 points to src, %r2+%r3 to dst
/glibc-2.36/math/
DREADME.libm-test4 The libm-test math test suite tests a number of function points of
14 The tests just evaluate the functions at specified points and compare
DVersions175 # Optimized -ffinite-math-only entry points
/glibc-2.36/localedata/charmaps/
DIBM85812 % The code points from /x01 to /x1f in this file have the same mapping
19 % it ASCII-compatible we deviate fro CP00858.txt in the code points from /x01
/glibc-2.36/elf/
Drtld-debugger-interface.txt75 A pointer which, if not NULL, points to the entry in the specified
/glibc-2.36/manual/
Dsetjmp.texi48 You identify return points for non-local exits by calling the function
171 Return points are valid only during the dynamic extent of the function
489 current context it is possible to have multiple different scheduling points
Ddynlink.texi159 @code{struct dl_find_object} points to the @code{PT_GNU_EH_FRAME}
Dsearch.texi421 @c The table is released while the table pointer still points to it.
522 new element was created the pointer points to the new data (which is in
533 new element is entered (note that the @var{rootp} parameter points to a
Dcharset.texi494 sequence points. Communication protocols often require this.
1341 just part of a character, or @var{string} points to an empty string (a
1411 character, or @var{string} points to an empty string (a null character).
1619 work. Plus it suffers from the other two raised points even more due to
1798 points to the beginning of the buffer with at least
1849 After the call, @code{*@var{inbuf}} points at the first byte of the
2133 follows is a step-by-step analysis of the points raised above. The
2413 @code{__outbuf} element points to the beginning of the buffer, and
2414 @code{__outbufend} points to the byte following the last byte in the
2473 The @code{__statep} element points to an object of type @code{mbstate_t}
[all …]
Dfilesys.texi23 * Symbolic Links:: A file that ``points to'' a file name.
478 @c use, since it points to a stream's internal buffer that can be
503 @strong{Caution:} The pointer returned by @code{readdir} points to
897 first parameter points to the file name, the second parameter to an
963 The current item is a stale symbolic link. The file it points to does
1289 symbolic link points to an existing file which is later deleted, the
1297 likewise operates on the file that the symbolic link points to, instead
1367 @var{filename}. The file name that the link points to is copied into
1472 it. If @var{resolved} is not @code{NULL} it points to a buffer into
1642 directories that are mount points for filesystems, and directories
[all …]
Dargp.texi178 called for each option parsed, and at other well-defined points in the
233 The @code{options} field in a @code{struct argp} points to a vector of
364 parser to perform tasks at certain other points during parsing.
397 @var{state} points to a @code{struct argp_state}, containing useful
Dsysinfo.texi444 This name is poorly chosen. This element points to a string (possibly
591 This element points to a string describing the mount point of the
721 of these characters (e.g., mount points using spaces). Therefore
Dgetopt.texi136 key points to notice are:
Dterminal.texi299 in the structure that @var{termios-p} points to.
321 structure that @var{termios-p} points to.
349 bit in the @code{c_cflag} member of the structure @var{termios-p} points
2186 the structure that @var{termp} points to (@pxref{Terminal Modes}).
2189 @var{winp} points to.
Dtime.texi925 When @var{tzp} is not a null pointer, the data it points to @emph{may}
1151 @var{resultp} points.
1304 @var{brokentime} points to into a string in a standard format:
1317 The return value points to a statically allocated string, which might be
2236 the format string the return value points right after the last consumed
2238 points to the @code{NULL} byte at the end of the string. If an error
2863 points to.
Dpattern.texi797 * Subexpression Complications:: Find points of which parts were matched.
1610 points to. This includes various internal fields of the @code{regex_t}
1990 @code{*@var{word-vector-ptr}} points to. This does not free the
1992 data it points to.
Dthreads.texi988 critical section. This pointer and the code areas it itself points to
1014 pointer points, the value is negative.
Dsyslog.texi175 @var{ident} points to. It is also dangerous to pass a reference to an
/glibc-2.36/iconvdata/testdata/
Dsuntzus104 21. If he is secure at all points, be prepared for him.
273 if the bulwark is complete at all points; the State will
416 of weak points and strong.
520 5. Appear at points which the enemy must hasten to defend;
540 if you make for the enemy's weak points; you may retire
569 against a possible attack at several different points;
1007 knots or speaking in subdued tones points to disaffection

1234