Home
last modified time | relevance | path

Searched refs:complex (Results 1 – 11 of 11) sorted by relevance

/frameworks/base/libs/protoutil/tests/
DProtoOutputStream_test.cpp204 ComplexProto complex; in TEST() local
205 ASSERT_TRUE(complex.ParseFromString(iterateToString(&proto))); in TEST()
206 EXPECT_EQ(complex.ints_size(), 3); in TEST()
207 EXPECT_EQ(complex.ints(0), 23); in TEST()
208 EXPECT_EQ(complex.ints(1), 101); in TEST()
209 EXPECT_EQ(complex.ints(2), -72); in TEST()
210 EXPECT_EQ(complex.logs_size(), 2); in TEST()
211 ComplexProto::Log log1 = complex.logs(0); in TEST()
215 ComplexProto::Log log2 = complex.logs(1); in TEST()
243 ComplexProto complex; in TEST() local
[all …]
/frameworks/base/core/java/android/util/
DTypedValue.java262 public static float complexToFloat(int complex) in complexToFloat() argument
264 return (complex&(TypedValue.COMPLEX_MANTISSA_MASK in complexToFloat()
266 * RADIX_MULTS[(complex>>TypedValue.COMPLEX_RADIX_SHIFT) in complexToFloat()
/frameworks/rs/script_api/include/
Drs_object_info.rsh53 * Elements can be grouped together into complex Elements, creating the equivalent of
62 * To create complex Elements, use the Element.Builder Java class.
227 * more complex numerical type (e.g. RS_TYPE_UNSIGNED_5_6_5 and RS_TYPE_MATRIX_4X4).
234 * functions to explore this complex Element.
242 * rsElementGetSubElement: Sub-element of a complex Element
262 * rsElementGetSubElementArraySize: Array size of a sub-element of a complex Element
264 * For complex Elements, sub-elements can be statically sized arrays. This function
284 * sub-elements for complex Elements.
299 * For complex Elements, this function returns the name of the sub-element at the
318 * For complex Elements, this function returns the length of the name of the sub-element
Drs_object_types.rsh138 RS_TYPE_NONE = 0, // Element is a complex type, i.e. a struct.
/frameworks/compile/slang/tests/P_warnings_rsSetElementAt/
Dsetelementat.rscript35 // No warnings for complex data types
/frameworks/base/startop/apps/test/
DREADME.md18 This activity inflates a reasonably complex layout to see the impact of layout
/frameworks/base/packages/SystemUI/docs/
Dkotlin-in-sysui.md12 - Only use extension functions for keeping complex code locality: Don't use
/frameworks/av/media/libeffects/dynamicsproc/dsp/
DRDsp.h26 using ComplexVec = std::vector<std::complex<float>>;
/frameworks/base/tools/aapt2/
Dreadme.md79 - aapt2 optimize now understands map (complex) values under the type `id`. It ignores their
146 - Added support for inline complex XML resources. See
147 https://developer.android.com/guide/topics/resources/complex-xml-resources.html
/frameworks/compile/slang/
DREADME.rst315 use more complex types. Simple structures composed of the types in
/frameworks/base/libs/androidfw/
DResourceTypes.cpp7293 static void print_complex(uint32_t complex, bool isFraction) in print_complex() argument
7302 float value = (complex&(Res_value::COMPLEX_MANTISSA_MASK in print_complex()
7304 * RADIX_MULTS[(complex>>Res_value::COMPLEX_RADIX_SHIFT) in print_complex()
7309 switch ((complex>>Res_value::COMPLEX_UNIT_SHIFT)&Res_value::COMPLEX_UNIT_MASK) { in print_complex()
7319 switch ((complex>>Res_value::COMPLEX_UNIT_SHIFT)&Res_value::COMPLEX_UNIT_MASK) { in print_complex()