search for: getnumstorebuff

...t; I like the idea of abstracting the hardware resource for the compiler's > needs, though I think we will in general want multiple such things. > Maybe one for load and one for store to start? For more harware-y > things like llvm-mca more detail may be desired. Your RFC already has getNumStoreBuffers, getNumLoadBuffers and getNumLoadStoreBuffers, no? As far I understand, write-combining only applies to getNumStoreBuffers(). Prefetch streams would limit getNumLoadBuffers. Michael

Am Mo., 5. Nov. 2018 um 10:26 Uhr schrieb David Greene <dag at cray.com>: > Yes, I agree the terminology is confusing. I used the term "stream" in > the sense of stream processing (https://en.wikipedia.org/wiki/Stream_processing). > The programming model is very different, of course, but the idea of a > stream of data that is acted upon and then essentially discarded

.../// > int getNumLoadBuffers() const; > > /// getMaxNumLoadBuffers - Return the maximum number of load > /// streams that may be active before shutting off streaming > /// entirely. -1 => no limit. > /// > int getMaxNumLoadBuffers(); > > /// getNumStoreBuffers - Return the effective number of store > /// buffers available. This is the number of simultaneously > /// active independent store streams the processor can handle > /// before degrading performance. > /// > int getNumStoreBuffers() const; > > /// g...