Lines Matching full:safe
2022 ABI for thread-safe initialization of local statics. You can use
2024 to be thread-safe.
2487 synchronization blocks for thread-safe execution:
3297 is perfectly safe if the values of the variables involved are such
7707 safe to edit the filename if the PCH file is available in a
9992 Like `u', but the instructions are marked to be safe for
11261 Support thread-safe exception handling on `Mingw32'. Code that
11262 relies on thread-safe exception handling must compile and link all
12723 accesses to these regions are indeed safe.
14168 SHmedia32/SHcompact. This is only safe if the hardware and/or OS
14173 other way to make the indexed addressing mode safe to use in the
14832 safe density instructions to align a target, no widening will be
15657 generated. At present, it's not clear which options are safe to
15660 The following are known to be safe:
16546 This feature is especially useful in making macro definitions "safe"
16828 safe.
17023 be used to define a safe "maximum" macro that operates on any
18740 says that the hypothetical function `square' is safe to call fewer
18796 FreeBSD, are believed to be safe since the loaders there save EAX,
22887 It is not safe to access the global register variables from signal
22892 It is not safe for one function that uses a global register variable to
23743 initializers. The earliest version where it is completely safe is
35404 It is believed to be safe to throw a C++ exception from one file through
37330 The safe way to write such code is to give the temporary a name, which
37419 One case in which you can be sure `unprotoize' is safe is when you
37584 it is safe to use certain features of ISO C, such as function
37667 It is never safe to depend on the order of evaluation of side
39579 forth). Later, more work on MT-safe string and shadow headers.
39780 * Teemu Torma for thread safe exception handling support.
