Lines Matching full:safe
1957 ABI for thread-safe initialization of local statics. You can use
1959 to be thread-safe.
2412 synchronization blocks for thread-safe execution:
3214 is perfectly safe if the values of the variables involved are such
7135 safe to edit the filename if the PCH file is available in a
9356 Like `u', but the instructions are marked to be safe for
10588 Support thread-safe exception handling on `Mingw32'. Code that
10589 relies on thread-safe exception handling must compile and link all
13285 SHmedia32/SHcompact. This is only safe if the hardware and/or OS
13290 other way to make the indexed addressing mode safe to use in the
13863 safe density instructions to align a target, no widening will be
14653 generated. At present, it's not clear which options are safe to
14656 The following are known to be safe:
15542 This feature is especially useful in making macro definitions "safe"
15824 safe.
16019 be used to define a safe "maximum" macro that operates on any
17629 says that the hypothetical function `square' is safe to call fewer
17685 FreeBSD, are believed to be safe since the loaders there save all
21570 It is not safe to access the global register variables from signal
21575 It is not safe for one function that uses a global register variable to
22415 initializers. The earliest version where it is completely safe is
33597 It is believed to be safe to throw a C++ exception from one file through
35517 The safe way to write such code is to give the temporary a name, which
35606 One case in which you can be sure `unprotoize' is safe is when you
35771 it is safe to use certain features of ISO C, such as function
35854 It is never safe to depend on the order of evaluation of side
37766 forth). Later, more work on MT-safe string and shadow headers.
37967 * Teemu Torma for thread safe exception handling support.
