Searched refs:threadsafe (Results 1 – 25 of 37) sorted by relevance
12
/external/protobuf/objectivec/google/protobuf/ |
D | Wrappers.pbobjc.m | 42 // This method is threadsafe because it is initially called 85 // This method is threadsafe because it is initially called 128 // This method is threadsafe because it is initially called 171 // This method is threadsafe because it is initially called 214 // This method is threadsafe because it is initially called 257 // This method is threadsafe because it is initially called 299 // This method is threadsafe because it is initially called 342 // This method is threadsafe because it is initially called 385 // This method is threadsafe because it is initially called
|
D | Struct.pbobjc.m | 74 // This method is threadsafe because it is initially called 127 // This method is threadsafe because it is initially called 238 // This method is threadsafe because it is initially called
|
D | Type.pbobjc.m | 101 // This method is threadsafe because it is initially called 218 // This method is threadsafe because it is initially called 491 // This method is threadsafe because it is initially called 586 // This method is threadsafe because it is initially called 649 // This method is threadsafe because it is initially called
|
D | Api.pbobjc.m | 69 // This method is threadsafe because it is initially called 188 // This method is threadsafe because it is initially called 304 // This method is threadsafe because it is initially called
|
D | Empty.pbobjc.m | 40 // This method is threadsafe because it is initially called
|
D | SourceContext.pbobjc.m | 42 // This method is threadsafe because it is initially called
|
D | FieldMask.pbobjc.m | 42 // This method is threadsafe because it is initially called
|
D | Any.pbobjc.m | 44 // This method is threadsafe because it is initially called
|
D | Duration.pbobjc.m | 44 // This method is threadsafe because it is initially called
|
D | Timestamp.pbobjc.m | 44 // This method is threadsafe because it is initially called
|
/external/libchrome/base/mac/ |
D | bundle_locations.mm | 14 // NSBundle isn't threadsafe, all functions in this file must be called on the
|
/external/sfntly/ |
D | Android.bp | 121 "-fno-threadsafe-statics",
|
/external/mesa3d/src/gallium/state_trackers/d3d1x/gd3d11/ |
D | d3d11_context.h | 40 template<bool threadsafe> 41 struct GalliumD3D10Device : public GalliumD3D10ScreenImpl<threadsafe> 126 #define SYNCHRONIZED lock_t<maybe_mutex_t<threadsafe> > lock_(this->mutex) 129 …: GalliumD3D10ScreenImpl<threadsafe>(screen, pipe, owns_pipe, creation_flags, adapter), pipe(pipe)… in GalliumD3D10Device()
|
D | d3d11_screen.h | 92 template<bool threadsafe> 99 maybe_mutex_t<threadsafe> mutex; 104 #define SYNCHRONIZED lock_t<maybe_mutex_t<threadsafe> > lock_(mutex)
|
/external/libevent/ |
D | whatsnew-2.0.txt | 81 non-threadsafe code, or forced code built against one version of Libevent 95 prevent errors in your applications, and to be more threadsafe. 241 To make an evbuffer or a bufferevent object threadsafe, call its 244 The HTTP api is not currently threadsafe.
|
D | ChangeLog | 84 o core: Make event_pending() threadsafe. (be7a95c Simon Liu) 528 o Make evdns_getaddrinfo_cancel threadsafe (d51b2fc) 590 o Add a LEV_OPT_THREADSAFE option for threadsafe evconnlisteners (127d4f2) 598 O Make default signal backend fully threadsafe (95a7d41) 834 o Make evdns logging threadsafe (b1c7950) 1248 o Patch from Tani Hosokawa: make some functions in http.c threadsafe. 1262 o Make name_from_addr() threadsafe in http.c 1264 o Make all event_tagging interfaces threadsafe. 1266 …_assign, event_new, event_free) for use by apps that want to be safely threadsafe, or want to rema…
|
/external/mesa3d/src/gallium/state_trackers/d3d1x/d3d1xstutil/include/ |
D | d3d1xstutil.h | 675 template<bool threadsafe>
|
/external/clang/lib/CodeGen/ |
D | ItaniumCXXABI.cpp | 1923 bool threadsafe = getContext().getLangOpts().ThreadsafeStatics && in EmitGuardedInit() local 1929 bool useInt8GuardVariable = !threadsafe && var->hasInternalLinkage(); in EmitGuardedInit() 2020 if (threadsafe) in EmitGuardedInit() 2058 if (threadsafe) { in EmitGuardedInit() 2077 if (threadsafe) { in EmitGuardedInit()
|
/external/googletest/googletest/docs/ |
D | V1_5_AdvancedGuide.md | 609 …* If the variable's value is `"threadsafe"`, the child process re-executes the unit test binary ju… 610 …ust the single death test under consideration to be run - much like the `threadsafe` mode on POSIX. 645 The "threadsafe" death test style was introduced in order to help mitigate the 655 ::testing::FLAGS_gtest_death_test_style = "threadsafe"; 664 ::testing::FLAGS_gtest_death_test_style = "threadsafe"; 665 // This test is run in the "threadsafe" style: 703 Despite the improved thread safety afforded by the "threadsafe" style of death
|
D | AdvancedGuide.md | 685 …* If the variable's value is `"threadsafe"`, the child process re-executes the unit test binary ju… 686 …ust the single death test under consideration to be run - much like the `threadsafe` mode on POSIX. 721 The "threadsafe" death test style was introduced in order to help mitigate the 731 ::testing::FLAGS_gtest_death_test_style = "threadsafe"; 740 ::testing::FLAGS_gtest_death_test_style = "threadsafe"; 741 // This test is run in the "threadsafe" style: 778 Despite the improved thread safety afforded by the "threadsafe" style of death
|
D | V1_6_AdvancedGuide.md | 682 …* If the variable's value is `"threadsafe"`, the child process re-executes the unit test binary ju… 683 …ust the single death test under consideration to be run - much like the `threadsafe` mode on POSIX. 718 The "threadsafe" death test style was introduced in order to help mitigate the 728 ::testing::FLAGS_gtest_death_test_style = "threadsafe"; 737 ::testing::FLAGS_gtest_death_test_style = "threadsafe"; 738 // This test is run in the "threadsafe" style: 775 Despite the improved thread safety afforded by the "threadsafe" style of death
|
D | V1_7_AdvancedGuide.md | 683 …* If the variable's value is `"threadsafe"`, the child process re-executes the unit test binary ju… 684 …ust the single death test under consideration to be run - much like the `threadsafe` mode on POSIX. 719 The "threadsafe" death test style was introduced in order to help mitigate the 729 ::testing::FLAGS_gtest_death_test_style = "threadsafe"; 738 ::testing::FLAGS_gtest_death_test_style = "threadsafe"; 739 // This test is run in the "threadsafe" style: 776 Despite the improved thread safety afforded by the "threadsafe" style of death
|
/external/google-breakpad/src/build/ |
D | common.gypi | 574 '-fno-threadsafe-statics', 851 'GCC_THREADSAFE_STATICS': 'NO', # -fno-threadsafe-statics
|
/external/c-ares/ |
D | ares_config.h.in | 102 /* Define to 1 if the getaddrinfo function is threadsafe. */
|
/external/skia/gn/ |
D | BUILD.gn | 154 "-fno-threadsafe-statics",
|
12