Searched refs:nearby (Results 1 – 25 of 44) sorted by relevance
12
24 int_mv *nearby, int_mv *best_mv, int near_mv_ref_cnts[4], in vp8_find_near_mvs() argument121 nearby->as_int = near_mvs[CNT_NEAR].as_int; in vp8_find_near_mvs()
73 int_mv *nearby, int_mv *best_mv, int near_mv_ref_cnts[4],
37 may return the name of a label or a preceeding (nearby) procedure.
25 check can be folded into a nearby memory operation that operates on
56 same machine or on a nearby machine (in terms of network distance) with the
262 reader to keep this file open nearby, so we could use it as a reference for
174 The scheduler should be able to sort nearby instructions by their address. For
85 nearby directories. If this logic fails, you'll need to manually define
123 // groups of nearby devices) before communicating.
508 # sound nearby. There is a vague pattern like this in the data, but the details
269 // Notification to let a device know it should contact a nearby device.
212 so they find it by calling talloc_parent() on a nearby IR node. The
212 // with respect to nearby accesses to the same memory.
1427 %nearby = call <2 x double> @llvm.experimental.constrained.nearbyint.v2f64(1431 ret <2 x double> %nearby1465 %nearby = call <4 x double> @llvm.experimental.constrained.nearbyint.v4f64(1470 ret <4 x double> %nearby
144 name named names narrower narrowing narrows native near nearby nearly necessarily necessary
332 dnl Assume the include files are nearby.
325 // with respect to nearby accesses to the same memory.
109 # check that nearby languages are handled
105 # check that nearby languages are handled
354 // from being reordered overly much with respect to nearby access to the same