OpenGrok
Home
Sort by relevance
Sort by last modified time
Full Search
Definition
Symbol
File Path
History
|
|
Help
Searched
full:block_release
(Results
1 - 19
of
19
) sorted by null
/external/compiler-rt/BlocksRuntime/tests/
copynull.c
31
Block_release
(blockcopy);
dispatch_call_Block_with_release.c
20
Block_release
(b);
recursive-block.c
41
//
Block_release
(inner);
50
Block_release
(block);
globalexpression.c
27
Block_release
(gblockcopy);
rdar6414583.c
27
Block_release
(block);
blockimport.c
48
Block_release
(vvcopy);
byrefcopycopy.c
33
Block_release
(_b);
byrefcopyint.c
63
Block_release
(array[i]);
reference.C
73
Block_release
(b2);
/external/compiler-rt/BlocksRuntime/
Block.h
41
* This must be paired with
Block_release
to recover memory, even when running
56
#define
Block_release
(...) _Block_release((const void *)(__VA_ARGS__))
runtime.c
480
printf("
Block_release
called upon a stack Block: %p, ignored\n", (void *)aBlock);
534
In these cases helper functions are synthesized by the compiler for use in Block_copy and
Block_release
, called the copy and dispose helpers. The copy helper emits a call to the C++ const copy constructor for C++ stack based objects and for the rest calls into the runtime support function _Block_object_assign. The dispose helper has a call to the C++ destructor for case 1 and a call into _Block_object_dispose for the rest.
/frameworks/compile/libbcc/runtime/BlocksRuntime/
Block.h
41
* This must be paired with
Block_release
to recover memory, even when running
56
#define
Block_release
(...) _Block_release((const void *)(__VA_ARGS__))
runtime.c
481
printf("
Block_release
called upon a stack Block: %p, ignored\n", (void *)aBlock);
535
In these cases helper functions are synthesized by the compiler for use in Block_copy and
Block_release
, called the copy and dispose helpers. The copy helper emits a call to the C++ const copy constructor for C++ stack based objects and for the rest calls into the runtime support function _Block_object_assign. The dispose helper has a call to the C++ destructor for case 1 and a call into _Block_object_dispose for the rest.
/external/webkit/Source/WebKit2/UIProcess/API/C/
WKDatabaseManager.cpp
108
Block_release
(block);
127
Block_release
(block);
WKFrame.cpp
154
Block_release
(block);
178
Block_release
(block);
WKPage.cpp
410
Block_release
(block);
429
Block_release
(block);
448
Block_release
(block);
467
Block_release
(block);
/external/clang/docs/
BlockLanguageSpec.txt
108
The copy operation Block_copy() is styled as a function that takes an arbitrary Block reference and returns a Block reference of the same type. The release operation,
Block_release
(), is styled as a function that takes an arbitrary Block reference and, if dynamically matched to a Block copy operation, allows recovery of the referenced allocated memory.
115
In the case where a __block variable is a Block one must assume that the __block variable resides in allocated storage and as such is assumed to reference a Block that is also in allocated storage (that it is the result of a Block_copy operation). Despite this there is no provision to do a Block_copy or a
Block_release
if an implementation provides initial automatic storage for Blocks. This is due to the inherent race condition of potentially several threads trying to update the shared variable and the need for synchronization around disposing of older values and copying new ones. Such synchronization is beyond the scope of this language specification.
158
If a Block originates on the stack, a const copy constructor of the stack-based Block const copy is performed when a Block_copy operation is called; when the last
Block_release
(or subsequently GC) occurs, a destructor is run on the heap copy.
Block-ABI-Apple.txt
97
2) The flags field is set to zero unless there are variables imported into the block that need helper functions for program level Block_copy() and
Block_release
() operations, in which case the (1<<25) flags bit is set.
284
Variables of certain types require helper functions for when Block_copy() and
Block_release
() are performed upon a referencing Block. At the "C" level only variables that are of type Block or ones that have __attribute__((NSObject)) marked require helper functions. In Objective-C objects require helper functions and in C++ stack based objects require helper functions. Variables that require helper functions use the form:
291
// helper functions called via Block_copy() and
Block_release
()
AutomaticReferenceCounting.html
133
reference count by 1. The paired function is <tt>
Block_release
</tt>,
[
all
...]
Completed in 342 milliseconds