Searched refs:complex (Results 1 - 13 of 13) sorted by relevance

H A Dcomplex.h47 #define complex _Complex macro
52 extern float cabsf(float complex);
53 extern float cargf(float complex);
54 extern float cimagf(float complex);
55 extern float crealf(float complex);
56 extern float complex cacosf(float complex);
57 extern float complex cacoshf(float complex);
58 extern float complex casin
H A Dtgmath.h35 #include <complex.h>
38 * real-floating and complex
156 * complex only
H A Dtest-float.c16 #include <complex.h>
26 float complex d;
27 double complex e;
28 long double complex f;
H A Dtest-sou.c17 #include <complex.h>
219 complex double namine;
H A Dtst.retlist.s39 ENTRY(complex) function
47 SET_SIZE(complex)
H A Dcomplex_wrapper.h46 #include <complex.h>
49 #define dcomplex double complex
50 #define fcomplex float complex
51 #define ldcomplex long double complex
61 #include <complex.h>
H A Dzonecfg_grammar.y41 static complex_property_ptr_t complex = NULL;
114 complex = retval;
125 complex_property_ptr_t complex;
143 %type <complex> complex_piece complex_prop_val
1012 * complex data structures.
1014 * There are three kinds of properties: simple (single valued), complex
1016 * simple or complex properties).
1036 property[num_prop_vals].pv_complex = complex;
1051 * One level lower, lists are made up of simple or complex values, so
1054 * complex propertie
H A Dzonecfg.h225 extern void free_complex(complex_property_ptr_t complex);
H A Dzonecfg.c249 "complex",
739 free_complex(complex_property_ptr_t complex) argument
741 if (complex == NULL)
743 free_complex(complex->cp_next);
744 if (complex->cp_value != NULL)
745 free(complex->cp_value);
746 free(complex);
1991 * mis-parsing them as complex name=value pairs.
4387 * 2. rctl value's are complex or list (tested below)
H A Dex_re.c812 complex:
814 (unsigned char *)gettext("Re too complex") :
822 goto complex;
838 goto complex;
885 goto complex;
911 goto complex;
939 goto complex;
949 goto complex;
1050 goto complex;
H A Ddoupdate.c94 STATIC void complex(void);
221 * wise in addition to the row-wise used in complex(). It was removed
450 * Only ever used for complex().
462 * Only ever used for complex().
498 * Only ever used for complex().
804 complex() function
934 (__m_screen->_flags & S_INS_DEL_LINE) ? "complex" : "simple"
990 complex();
H A Ddoupdate.c95 static void complex(void);
610 * Only ever used for complex().
621 * Only ever used for complex().
654 * Only ever used for complex().
935 complex(void) function
1117 complex();
1124 complex();
H A Decore.tex424 \item \myindex{RT array} ��� when the ecore initializes the HW, it utilizes a common, tool-generated code known as the init-tool. Since there are quite a few values which depend upon actual setup configuration and thus must receive feedback during the initialization from the ecore, instead of adding many such hooks there���s the concept of the RunTime array ��� an array of values filled by the ecore prior to the init-tool run based on the complex ecore logic. The init-tool will then utilize the values in that array to configure the HW according to the correct order of configuration [i.e., writing the values set by ecore in the array in the correct place in the initialization flow where they���re required/the block that contains them is configured].
1708 Sr-iov is exposed to complex versioning challenges. Specifically, a given PF driver may be working with VF drivers of older and/or newer versions at the same time.

Completed in 102 milliseconds