Lines Matching full:safe
1737 ABI for thread-safe initialization of local statics. You can use
1739 to be thread-safe.
2162 synchronization blocks for thread-safe execution:
2837 is perfectly safe if the values of the variables involved are such
6490 safe to edit the filename if the PCH file is available in a
8555 Like `u', but the instructions are marked to be safe for
9680 Support thread-safe exception handling on `Mingw32'. Code that
9681 relies on thread-safe exception handling must compile and link all
12031 SHmedia32/SHcompact. This is only safe if the hardware and/or OS
12036 other way to make the indexed addressing mode safe to use in the
12377 To be on the safe side, this is disabled for the C3x, since the
12646 safe density instructions to align a target, no widening will be
13419 generated. At present, it's not clear which options are safe to
13422 The following are known to be safe:
14305 This feature is especially useful in making macro definitions "safe"
14581 safe.
14721 be used to define a safe "maximum" macro that operates on any
16092 says that the hypothetical function `square' is safe to call fewer
16117 FreeBSD, are believed to be safe since the loaders there save all
19785 It is not safe to access the global register variables from signal
19790 It is not safe for one function that uses a global register variable to
20626 initializers. The earliest version where it is completely safe is
25337 It is believed to be safe to throw a C++ exception from one file through
27266 The safe way to write such code is to give the temporary a name, which
27355 One case in which you can be sure `unprotoize' is safe is when you
27520 it is safe to use certain features of ISO C, such as function
27603 It is never safe to depend on the order of evaluation of side
29145 forth). Later, more work on MT-safe string and shadow headers.
29344 * Teemu Torma for thread safe exception handling support.
