Home
last modified time | relevance | path

Searched refs:lead (Results 1 – 25 of 27) sorted by relevance

12

/glibc-2.36/timezone/
Dzdump.c1081 register int lead; in dumptime() local
1107 lead = timeptr->tm_year / DIVISOR + TM_YEAR_BASE / DIVISOR + in dumptime()
1110 if (trail < 0 && lead > 0) { in dumptime()
1112 --lead; in dumptime()
1113 } else if (lead < 0 && trail > 0) { in dumptime()
1115 ++lead; in dumptime()
1117 if (lead == 0) in dumptime()
1119 else printf("%d%d", lead, ((trail < 0) ? -trail : trail)); in dumptime()
Dsouthamerica605 # sources of time zone information lead me to believe that AL, SE, and TO were
Dasia1014 # because the public believed it would lead to longer working hours.''
/glibc-2.36/manual/
Dsetjmp.texi435 on most platforms more information which may lead to fewer surprises
486 asynchronous signal safe could lead to problems. Setting a variable in
Dcreature.texi117 (@code{lseek}) would lead to problems.
Dllio.texi509 otherwise the large offsets possible with @code{off64_t} will lead to
711 otherwise the large offsets possible with @code{off64_t} will lead to
831 otherwise the large offsets possible with @code{off64_t} will lead to
1252 otherwise the large offsets possible with @code{off64_t} will lead to
1301 otherwise the large offsets possible with @code{off64_t} will lead to
1376 otherwise the large offsets possible with @code{off64_t} will lead to
1420 otherwise the large offsets possible with @code{off64_t} will lead to
2344 like terminals where an @code{lseek} call would lead to an error.
2421 like terminals where an @code{lseek} call would lead to an error.
2959 retrieve the return value. Following calls might lead to undefined
Dtunables.texi347 Contended locks are usually slow and can lead to performance and scalability
Dcharset.texi265 Roman alphabet lead to character sets like @w{ISO 6937}. Here bytes
1058 after the newline character, which could lead to very strange results.
1997 This looks rather innocent but can lead to problems on platforms that
2014 of the @code{iconv} functions can lead to portability issues.
Dtime.texi1767 in @w{ISO C} can lead to problems in some situations. For certain
2703 lead to trouble.
Dsignal.texi1945 variable can also lead to paradoxical results, but here we only show
2446 reading or writing the data. This would lead to confusing consequences.
Dmessage.texi1132 only lead to problems.
Dstdio.texi4299 Therefore, using ftell can lead to problems if the implementation is
4825 integer, except that it might lead to doing I/O in chunks of an
Dmemory.texi1822 @theglibc{}, and other linked-in libraries) can lead to static linking
Dfilesys.texi3288 @c Although the internal xmknod takes a dev_t*, that could lead to
Dtexinfo.tex7917 % leave the code in, but it's strange for @var to lead to typewriter.
/glibc-2.36/iconvdata/testdata/
Dsuntzus123 lead to victory, and few calculations to defeat:
443 11. The direct and the indirect lead on to each other in turn.
707 13. We are not fit to lead an army on the march
1424 not fit to lead an army on the march unless we are familiar
/glibc-2.36/
DNEWS1517 4.8 can lead to application crashes for some MIPS configurations. While
1592 functions other can lead to crashes
1756 [20188] nptl: libpthread IFUNC resolver for vfork can lead to crash
1876 each syscall, but it lead to performance issues on newer kernels where the
1956 CVE-2018-19591: A file descriptor leak in if_nametoindex can lead to a
3016 [22415] stdio: setvbuf can lead to invalid free/segfault
3726 missing .cantunwind annotation. This has been observed to lead to a hang
3799 [20444] hurd: recvmsg: PF_LOCAL sockets and msg_name lead to SIGLOST
4080 [19861] nptl: libpthread IFUNC resolver for fork can lead to crash
4266 * An integer overflow in hcreate and hcreate_r could lead to an
[all …]
Dconfigure.ac1151 # since this would lead to problems installing/building glibc.
DMakerules268 # may lead to build hang on a many-core machine.
/glibc-2.36/posix/
Dtst-fnmatch.input63 # This lead to several bugs and problems with user scripts that do not
/glibc-2.36/ChangeLog.old/
DChangeLog.153993 * nscd/hstcache.c (cache_addhst): Fix two scenarios which lead to
DChangeLog.106038 the flags, kernels with different flags lead to
11329 * sysdeps/i386/strchrnul.S: Fix bugs which lead to wrong results in
DChangeLog.17217 checking lead byte of optstring for :.
1847 character lead bytes when there is a range in a COMPLEX_BRACKET.
DChangeLog.68607 This might lead to problems.
DChangeLog.78606 it would lead to warnings.

12