Home
last modified time | relevance | path

Searched refs:destroying (Results 1 – 25 of 74) sorted by relevance

123

/external/libwebsockets/lib/misc/threadpool/
Dthreadpool.c91 unsigned int destroying:1; member
464 while (!tp->destroying) { in lws_threadpool_worker()
474 while (!tp->task_queue_head && !tp->destroying) in lws_threadpool_worker()
477 if (tp->destroying) { in lws_threadpool_worker()
550 if (tp->destroying || !task->args.wsi) { in lws_threadpool_worker()
709 tp->destroying = 1; in lws_threadpool_finish()
758 tp->destroying = 1; in lws_threadpool_destroy()
809 if (task->outlive && !tp->destroying) { in lws_threadpool_dequeue()
911 if (tp->destroying) in lws_threadpool_enqueue()
/external/mesa3d/src/gallium/auxiliary/util/
Du_upload_mgr.c136 upload_unmap_internal(struct u_upload_mgr *upload, boolean destroying) in upload_unmap_internal() argument
153 if (destroying || !upload->map_persistent) { in upload_unmap_internal()
/external/mesa3d/docs/relnotes/
D18.0.2.rst43 - surface state leak when creating and destroying image views with
116 - mesa: free debug messages when destroying the debug state
D17.3.9.rst45 - surface state leak when creating and destroying image views with
122 - mesa: free debug messages when destroying the debug state
D20.1.4.rst109 - radv: fix destroying the syncobj when exporting a fence FD
D20.1.8.rst104 - mesa/st: release debug_output after destroying the context
D13.0.6.rst172 - anv: Properly handle destroying NULL devices and instances
205 - st/mesa: destroy pipe_context before destroying st_context (v2)
D10.5.9.rst109 - winsys/radeon: Unmap GPU VM address range when destroying BO
D9.0.1.rst97 - wayland: Destroy frame callback when destroying surface
D19.3.5.rst133 - radeonsi: don't wait for shader compilation to finish when destroying
D20.0.7.rst112 - vulkan: Allow destroying NULL debug report callbacks
D8.0.3.rst211 - darwin: Unlock our mutex before destroying it
212 - darwin: Eliminate a possible race condition while destroying a
D17.0.2.rst102 - anv: Properly handle destroying NULL devices and instances
D10.6.2.rst118 - winsys/radeon: Unmap GPU VM address range when destroying BO
/external/autotest/client/site_tests/cellular_DeferredRegistration/
Dcontrol.pseudomodem19 Tests that shill can handle temporary registration loss without destroying
/external/deqp/doc/testspecs/GLES3/
Dfunctional.buffers.txt25 + Creating and destroying buffers
Dfunctional.pbo.txt25 + Creating and destroying pixel pack and unpack buffers
/external/libwebsockets/lib/secure-streams/
Dsecure-streams-client.c397 if (h->destroying) in lws_sspc_destroy()
400 h->destroying = 1; in lws_sspc_destroy()
Dprivate-lib-secure-streams.h242 uint8_t destroying:1; member
/external/llvm-project/llvm/test/Transforms/Inline/
Dcgscc-invalidate.ll40 ; destroying dominator tree.
/external/llvm-project/lldb/test/API/api/multithreaded/
Dtest_stop-hook.cpp.template79 // We need to reset the handle before destroying the debugger
/external/grpc-grpc/src/objective-c/GRPCClient/private/
DGRPCChannel.m42 // Decrease ref count to the object when destroying
/external/python/cpython2/Doc/c-api/
Dtuple.rst145 at the end. Think of this as destroying the old tuple and creating a new one,
/external/python/cpython3/Misc/NEWS.d/
D3.9.0rc2.rst37 Fix a crash that occurred when destroying subclasses of
/external/grpc-grpc/src/core/ext/transport/chttp2/transport/
Dinternal.h299 uint8_t destroying; member

123