search for: msg00668

...doing globadynamic in non-PIC code). GCC does the same. > > Do you know what is the rationale for that? The static linker will > optimize it anyway (but not do as good a job as the compiler could). I managed to dig out the original thread for GCC: http://gcc.gnu.org/ml/gcc-patches/2002-09/msg00668.html It doesn't give a rationale for the case we're discussing, though :/ My intuition still tells me that it would be good to separate the default and globaldynamic cases to 1) Respect the user's request: if the user went through the trouble of specifying __attribute__((tls_model(&q...

> I thought it was a good idea to make the user's choice explicit in the > IR. If we combined the default and globaldynamic modes, LLVM wouldn't > be able to tell the difference. > > It may or may not be important to be able to tell the difference, but > it would be unfortunate if we'd have to go and change the IR format > later because we limited ourselves here.

> I managed to dig out the original thread for GCC: > http://gcc.gnu.org/ml/gcc-patches/2002-09/msg00668.html > > It doesn't give a rationale for the case we're discussing, though :/ > > My intuition still tells me that it would be good to separate the > default and globaldynamic cases to > > 1) Respect the user's request: if the user went through the trouble of > s...

Hi Jan, Attached patch dumps io page fault flags. The flags show the reason of the fault and tell us if this is an unmapped interrupt fault or a DMA fault. Thanks, Wei signed-off-by: Wei Wang <wei.wang2@amd.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel