Adding Cache line size and PredictableSelectIsExpensive for Vulcan
CacheLineSize is only used for LoopDataPrefetch. Is there any reason that you define this vaule only?
Without defining PrefetchDistance, MinPrefetchStride, MaxPrefetchIterationsAhead, it's not worth it right now.
I agree that apart from CacheLineSize, we need the other parameters for LoopDataPrefetch to be effective.
The 2nd change i.e.PredictableSelectIsExpensive, still hold true for Vulcan. So, I am updating the diff.
Removed the CacheLineSize (set to 64) for Vulcan, as three other parameters are required for LoopDataPrefetch to be effective.
Will include CacheLineSize & 3 other parameters in another patch, after they are finalized.