Searched refs:leads (Results 1 – 8 of 8) sorted by relevance
816 const char *leads[MAX_LEADS + 1]; member851 const char **leads; in equiv_name() local863 leads = user_rel[i].leads; /* array of leading names to try */ in equiv_name()865 leading_name = fn_string_from_str((unsigned char *)*leads); in equiv_name()874 } while (equiv == NULL && *++leads != NULL); in equiv_name()
24 approach just leads to insanity. However, at the same time clearly
166 the labels "x" and "x ". This is not useful, and leads to subtle
486 This leads to an important simplification: it's no longer necessary506 This leads to another simplification. The I/O logic in the existing1172 Thus, although it leads to some complexity in reworking the data
270 This leads us into the `ipc_action' object. An `ipc_action'
1657 4996 rtld _init race leads to incorrect symbol values
5925 error and leads to termination of the connection.
1087 purpose. Some toolchains may define _FORTIFY_SOURCE which leads redefined 1516 zeros especially), and leads to inconsistent output from ACPICA across