Lines Matching refs:lazy
378 * be loaded as dependencies (lazy-loading) are added to the handle as each new
1076 * To leverage off of lazy loading, dlsym() requests can result in two
1078 * the address space. If the symbol isn't located, and lazy
1082 * constant - this is the standard issue with lazy loading. In addition,
1084 * loading of all lazy dependencies on the given handle, which can
1085 * defeat some of the advantages of lazy loading (look out JVM).
1089 uint_t lazy = 0;
1115 * Keep track of any global pending lazy loads.
1117 lazy += LAZY(nlmp);
1122 * still has pending lazy dependencies, start loading them in an
1128 if (lazy) {
1154 uint_t lazy = 0;
1170 * Keep track of any pending lazy loads associated
1173 lazy += LAZY(nlmp);
1178 * has pending lazy dependencies, start loading the lazy
1181 if (lazy) {
1238 * any lazy dependency and establishing a direct binding if necessary.
1277 * If this handle is RTLD_NEXT determine whether a lazy load
1279 * the lazy loading initialization normally carried out by
1306 * start any possible lazy dependency loading.
1351 * not fall back to a lazy loading rescan if the symbol can't be
1352 * found within the currently loaded objects. Note, a lazy
1354 * loaded to satisfy this request, but no exhaustive lazy load
1424 * get loaded from lazy loading. These objects will have been added to
1699 * As rt_dldump() will effectively lazy load the necessary support
2236 * dlopen(), or implicitly via lazy loading. One might consider
2237 * simply banning dlopen from a callback, but lazy loading must