I seriously doubt any of this makes a difference for a huge data structure. I'll check it out though.
- Don On Fri, 2007-01-19 at 17:49 -0600, Jim O'Flaherty, Jr. wrote: > Don, > > You wrote: > > Does it matter?... > > While I am not totally up-to-date on C++ compiler optimizers, it seems > like locality of reference compiler optimizations might be influenced > if you were to specify allocation on the stack as opposed to the heap. > And aren't stack based values much more likely to end up in registers > and in CPU cache than heap based references and values? Perhaps all > of these kinds of evaluations are rendered ineffective with more > modern day CPUs and C++/C compilers. From what I have been following > in the Java JVMs, these prove to be VERY important in the way they > choose to optimize execution paths and data flows. Just figured that > it would matter in C++/C in a similar way. > > > Jim > > > Don Dailey wrote: > > On Fri, 2007-01-19 at 17:19 -0600, Jim O'Flaherty, Jr. wrote: > > > > > Don, > > > > > > So could you elaborate on where you are allocating space for big_array > > > in your code snippet below? > > > > > > > > > > > > Does it matter? I just declare it as a global but I will probably > > eventually > > just place it on the heap via malloc - with a command line argument to > > set > > the size. > > > > - Don > > > > > > _______________________________________________ > > computer-go mailing list > > [email protected] > > http://www.computer-go.org/mailman/listinfo/computer-go/ > > > > _______________________________________________ computer-go mailing list [email protected] http://www.computer-go.org/mailman/listinfo/computer-go/
