search for: sparsly

....ll files, going through jenkins output, etc. > You typically have no good way to see the environment variables in effect. > Even if you do, there are typically hundreds of them and it may be hard to > know which ones affect the compiler. > - env vars only work more reliably if they are sparsly used as soon as > they have interesting/desirable effects you will see people using them in > their makefiles as well, making the whole thing brittle again because now > you have to wonder if someone overrides, resets, manipulates the env vars > in their makefiles bringing you back to s...

Yes, but in your example getenv is called every time enableFooBar needs to be initialized. What if your code is itself wrapped inside another loop you can't see (for example, the PassManager invoking passes)? Maybe I'm being overly pedantic. We use a lot of environment variables in our compiler because it's really super annoying and takes a lot of developer time to have to update

This patch modifies the physinfo hcall to export NUMA CPU and Memory topology information. The new physinfo hcall is integrated into libxc and xend (xm info specifically). Included in this patch is a minor tweak to xm-test''s xm info testcase. The new fields in xm info are: nr_nodes : 4 mem_chunks : node0:0x0000000000000000-0x0000000190000000