Searched refs:resolvable (Results 1 – 13 of 13) sorted by relevance
2 ; resolvable by cfl-aa (derived from BasicAA/2003-11-04-SimpleCases.ll).
2 ; resolvable by cfl-aa, but require analysis of getelementptr constant exprs.
2 ; resolvable by basicaa.
2 ; resolvable by basicaa, but require analysis of getelementptr constant exprs.
1604 private static void addFutureResolution(Resolvable resolvable, String variable, in addFutureResolution() argument1606 resolvable.addResolution(new Resolution(variable, value, builder)); in addFutureResolution()1608 Caches.addResolvableToCache(resolvable); in addFutureResolution()2013 public static void addResolvableToCache(Resolvable resolvable) { in addResolvableToCache() argument2014 mInfosToResolve.add(resolvable); in addResolvableToCache()
29 obtained host name is resolvable to an IP address appropriate
98 This is resolvable in WSGI -- a WSGI application can provide its own
1108 resolvable, and applications making use of long subtype names may
1202 resolvable, and applications making use of long subtype names
META-INF/MANIFEST.MF META-INF/ECLIPSEF.SF META-INF/ECLIPSEF ...
2486 a test, it doesn't make sense to run an IPv6 test when a host is resolvable10238 builds of libcurl would often fail to resolve perfectly resolvable host
META-INF/ META-INF/MANIFEST.MF com/ com/google/ com/ ...