Home
last modified time | relevance | path

Searched refs:strong (Results 1 – 25 of 90) sorted by relevance

1234

/glibc-2.36/sysdeps/unix/
Dmake-syscalls.sh98 source=$strong
101 source="${strong}_${vcount}"
103 echo " echo 'strong_alias ($strong, $source)'; \\"
107 echo " echo 'weak_alias ($strong, $base)'; \\"
125 source=$strong
128 source="${strong}_${vcount}"
130 echo " echo 'strong_alias ($strong, $source)'; \\"
137 echo " echo 'strong_alias ($strong, $name)'; \\"
141 echo " echo 'weak_alias ($strong, $name)'; \\"
151 while read file srcfile caller syscall args strong weak; do
[all …]
/glibc-2.36/
Dconfigure.ac234 dnl -fstack-protector-strong.
236 AS_HELP_STRING([--enable-stack-protector=@<:@yes|no|all|strong@:>@],
237 [Use -fstack-protector[-all|-strong] to detect glibc buffer overflows]),
241 all|yes|no|strong) ;;
586 AC_CACHE_CHECK(for -fstack-protector-strong, libc_cv_ssp_strong, [dnl
587 LIBC_TRY_CC_OPTION([$CFLAGS $CPPFLAGS -Werror -fstack-protector-strong],
611 elif test "$enable_stack_protector" = strong && test "$libc_cv_ssp_strong" = yes; then
612 stack_protector="-fstack-protector-strong"
Dconfigure1432 --enable-stack-protector=[yes|no|all|strong]
1433 Use -fstack-protector[-all|-strong] to detect glibc
3492 all|yes|no|strong) ;;
4036 elif test "$enable_stack_protector" = strong && test "$libc_cv_ssp_strong" = yes; then
DINSTALL203 '--enable-stack-protector=strong'
208 '-fstack-protector-strong' or '-fstack-protector-all' options to
/glibc-2.36/manual/
Dlang.texi80 @strong{Warning:} Even the argument expression @var{expression} is not
120 @strong{Usage note:} The @code{assert} facility is designed for
154 @strong{Compatibility Note:} Many older C dialects provide a similar,
261 @strong{Portability note:} For some C compilers, the last required
327 @strong{Portability note:} With some compilers, once you pass an
582 @strong{Usage Note:} @code{size_t} is the preferred way to declare any
586 @strong{Compatibility Note:} Implementations of C before the advent of
691 @strong{Portability Note:} One cannot actually easily compute the
Dsyslog.texi102 @strong{Warning:} This terminology is not universal. Some people use
246 @strong{Portability note:} In early systems, the sense of this bit was
381 @strong{NB:} @code{syslog} recognizes one other facility code: that of
Dcrypt.texi223 generator} (CRNG), also sometimes called a @dfn{cryptographically strong
239 cryptographically strong random data should call these functions once
Dconf.texi231 @strong{Usage Note:} Don't try to test whether the system supports POSIX
249 @strong{Usage Note:} You can use this macro to tell whether a POSIX.1
1104 @strong{Portability Note:} On some systems, @theglibc{} defines
1114 @strong{Portability Note:} @Theglibc{} does not enforce this limit
1143 number. @strong{This is always the case on @gnuhurdsystems{}.}
1145 @strong{Usage Note:} Don't use @code{FILENAME_MAX} as the size of an
1406 @strong{Portability Note:} On some systems, @theglibc{} does not
Dstdio.texi1318 @strong{Warning:} If the input data has a null character, you can't tell.
1341 @strong{Warning:} If the input data has a null wide character (which are
1378 @strong{Warning:} The @code{gets} function is @strong{very dangerous}
1381 should @strong{always} use @code{fgets} or @code{getline} instead. To
2394 @strong{Warning:} The @code{sprintf} function can be @strong{dangerous}
2482 @strong{Attention:} In versions of @theglibc{} prior to 2.1 the
2579 @strong{Portability Note:} The value of the @code{va_list} pointer is
2982 @strong{Portability Note:} The ability to extend the syntax of
3033 @strong{Attention:} In @theglibc{} versions before 2.0 the
3042 @strong{Portability Note:} It is possible to redefine the standard output
[all …]
Dstring.texi1092 @strong{Note:} GNU programs should not truncate strings or wide
1679 @strong{Compatibility Note:} The string collation functions are a new
2128 @strong{Warning:} Since @code{strtok} and @code{wcstok} alter the string
2280 @strong{Portability Note:} This function may produce different results
2369 @strong{Warning:} @code{explicit_bzero} does not guarantee that
2410 @strong{Note:} The @emph{only} optimization that @code{explicit_bzero}
2417 @strong{Portability Note:} This function first appeared in OpenBSD 5.5
2454 @strong{Portability Note:} This function is unique to @theglibc{}.
2491 @strong{Portability Note:} This function is unique to @theglibc{}.
2513 @strong{Warning:} Since a static buffer is used this function should not
[all …]
Derrno.texi58 @strong{Warning:} Many library functions may set @code{errno} to some
65 @strong{Portability Note:} @w{ISO C} specifies @code{errno} as a
399 @strong{Portability Note:} In many older Unix systems, this condition
811 You did @strong{what}?
1271 @strong{Portability Note:} If you want your program to work with
Dsetjmp.texi297 @strong{Compatibility Note:} Depending on the operating system,
352 @strong{Compatibility note}: The current Unix standard is very imprecise
Dtime.texi406 @strong{Portability Note:} The @code{clock} function described in
548 @strong{Portability Note:} On some systems, including systems that use
575 @strong{Portability Note:} As of the 2008 revision of POSIX, this
631 @strong{Portability Note}: On some systems, including systems that use
841 @strong{Portability note:} Early versions of @theglibc{} did not
1250 @strong{Portability note:} @code{mktime} is essentially universally
1277 @strong{Portability note:} @code{mktime} is essentially universally
2101 @strong{NB:} The Unix specification says the upper bound on this value
2221 @strong{Portability Note:} The XPG standard advises applications to use
2946 @strong{Portability Note:} The @code{setitimer} and @code{getitimer}
Dlocale.texi442 @strong{Portability Note:} Some @w{ISO C} systems may define additional
492 @strong{Portability Note:} With the notable exception of the standard
530 @strong{Portability Note:} POSIX suggests that if a locale name starts
979 @strong{NB:} @code{ABALTMON_@dots{}} constants corresponding to the
Dctype.texi228 @strong{Compatibility Note:} In pre-@w{ISO C} dialects, instead of
452 that code like the following will @strong{not} work unconditionally for
Dmaint.texi41 This variable @strong{must} be defined.
390 system-dependent, it @strong{must not} appear in one of the main source
Dfilesys.texi485 @strong{Portability Note:} On some systems @code{readdir} may not
503 @strong{Caution:} The pointer returned by @code{readdir} points to
531 @strong{Portability Note:} @code{readdir_r} is deprecated. It is
2523 @strong{Warning:} Writing explicit numbers for file permissions is bad
3221 @strong{Note:} If @code{fallocate} is not available (because the file
3402 @strong{Warning:} Between the time the pathname is constructed and the
3419 @strong{Warning}: This function has the same security problems as
3482 @strong{Warning:} Between the time the pathname is constructed and the
3505 @strong{NB:} Because @code{mktemp} and @code{mkstemp} modify the
3523 @strong{Warning:} Between the time the pathname is constructed and the
Dstartup.texi709 runs. That protocol is not defined by any strong authority, but
882 @strong{Warning:} Don't try to use the number of errors as the exit
892 @strong{Portability note:} Some non-POSIX systems use different
Dresource.texi515 @strong{NB:} The term ``runnable'' is a synonym for ``ready to run.''
587 @strong{NB:} The absolute priority is sometimes called the ``static
673 @strong{Portability Note:} On systems that have the functions in this
692 @strong{Portability Note:} In POSIX, the @code{pid_t} arguments of the
Dterminal.texi1059 @strong{Portability note:} In @theglibc{}, the functions above
1585 @strong{Portability note:} On some systems, the MIN and TIME slots are
2200 @strong{Warning:} Using the @code{openpty} function with @var{name} not
2201 set to @code{NULL} is @strong{very dangerous} because it provides no
2234 @strong{Warning:} The @code{forkpty} function has the same problems with
Dmemory.texi672 @strong{Portability Notes:}
725 Freeing a block alters the contents of the block. @strong{Do not expect to
859 @strong{Portability Note:} This function is not part of any standard. It was
902 @strong{Portability Notes:}
1820 @strong{Note:} Failure to provide a complete set of replacement
2212 @strong{Warning:} When you do use the macros, you must observe the
2873 @strong{NB:} If you mix use of @code{alloca} and variable-sized arrays
3420 @strong{Portability Note:} POSIX.1b requires that when the @code{mlock}
Dsignal.texi1027 @strong{Compatibility Note:} A problem encountered when working with the
1088 @strong{Compatibility Note:} As said above for @code{signal}, this
1217 @strong{Portability Note:} The basic @code{signal} function is a feature
1614 @strong{Portability Note:} Always use @code{sigaction} to establish a
2218 @strong{Portability note:} @code{raise} was invented by the @w{ISO C}
2810 @strong{Portability Note:} The @code{sigpending} function is new in
3149 to implement signal delivery. The size of a signal stack @strong{must}
Dinstall.texi229 @itemx --enable-stack-protector=strong
234 @option{-fstack-protector-strong} or @option{-fstack-protector-all}
/glibc-2.36/iconvdata/testdata/
Dsuntzus274 be strong; if the bulwark is defective, the State will
416 of weak points and strong.
633 30. So in war, the way is to avoid what is strong
1120 16. When the common soldiers are too strong and
1122 When the officers are too strong and the common soldiers
1344 33. How to make the best of both strong and weak--that
/glibc-2.36/ChangeLog.old/
DChangeLog.ports-hppa359 the strong name.
1035 * sysdeps/hppa/nptl/pthread_spin_unlock.c: Remove strong alias

1234