Searched full:oblivious (Results 1 – 14 of 14) sorted by relevance
22 interrupt handlers are oblivious to this distinction and therefore it is not
32 ignore them. In the first case, handlers are oblivious to the trigger type, so
171 * intercept allocations in a module-oblivious way. This will return NULL
148 entities should remain oblivious and just pass the B<OSSL_PARAM> array
513 - Fix lg_chunk clamping for the --enable-cache-oblivious --disable-fill case.735 --enable-cache-oblivious configure option is enabled.743 allocations when --enable-cache-oblivious configure option is enabled.913 disabled via the --disable-cache-oblivious configure option, and queried via
274 entities should remain oblivious and just pass the \fB\s-1OSSL_PARAM\s0\fR array
251 * case, handlers are oblivious to the trigger type, so it is not in plic_map_intr()
233 /// omit non-trivial branch conditions as the exploration is oblivious to them.
505 // 2. ScalarEvolution is designed to be control-flow oblivious. It tends in factorArrayIndex()
1412 J. Domke, T. Hoefler and W. Nagel: Deadlock-Free Oblivious Routing
755 \fB\-\-enable\-cache\-oblivious\fR
79 // The verifier is oblivious to s1 being a valid value for wavesize registers. in isVCC()
1099 all-oblivious52128 self-oblivious
129188 oblivious