<div style="font-family: arial, helvetica, sans-serif; font-size: 10pt"><div dir="ltr">On Wed, Dec 12, 2012 at 12:29 PM, Bill Schmidt <span dir="ltr"><<a href="mailto:wschmidt@linux.vnet.ibm.com" target="_blank" class="cremed">wschmidt@linux.vnet.ibm.com</a>></span> wrote:<br>
<div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Author: wschmidt<br>
Date: Wed Dec 12 14:29:20 2012<br>
New Revision: 170016<br>
<br>
URL: <a href="http://llvm.org/viewvc/llvm-project?rev=170016&view=rev" target="_blank" class="cremed">http://llvm.org/viewvc/llvm-project?rev=170016&view=rev</a><br>
Log:<br>
The ordering of two relocations on the same instruction is apparently not<br>
predictable when compiled on at least one non-PowerPC host.  Source of<br>
nondeterminism not apparent.  Restrict the test to build on PowerPC hosts<br>
for now while looking into the issue further.<br></blockquote><div><br></div><div style>Ow, and thanks for finding this!!! Please let folks know if we can help track this down. Non-determinism is scary.</div><div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Modified:<br>
    llvm/trunk/test/CodeGen/PowerPC/tls-ld-obj.ll<br>
<br>
Modified: llvm/trunk/test/CodeGen/PowerPC/tls-ld-obj.ll<br>
URL: <a href="http://llvm.org/viewvc/llvm-project/llvm/trunk/test/CodeGen/PowerPC/tls-ld-obj.ll?rev=170016&r1=170015&r2=170016&view=diff" target="_blank" class="cremed">http://llvm.org/viewvc/llvm-project/llvm/trunk/test/CodeGen/PowerPC/tls-ld-obj.ll?rev=170016&r1=170015&r2=170016&view=diff</a><br>

==============================================================================<br>
--- llvm/trunk/test/CodeGen/PowerPC/tls-ld-obj.ll (original)<br>
+++ llvm/trunk/test/CodeGen/PowerPC/tls-ld-obj.ll Wed Dec 12 14:29:20 2012<br>
@@ -4,6 +4,10 @@<br>
 ; Test correct relocation generation for thread-local storage using<br>
 ; the local dynamic model.<br>
<br>
+; Relocations 2 and 3 seem to come out in unpredictable order on some<br>
+; architectures, so restrict this for now.<br>
+; REQUIRES: ppc64-registered-target<br>
+<br>
 target datalayout = "E-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-f128:128:128-v128:128:128-n32:64"<br>
 target triple = "powerpc64-unknown-linux-gnu"<br>
<br>
@@ -17,9 +21,10 @@<br>
   ret i32 %0<br>
 }<br>
<br>
-; Verify generation of R_PPC64_GOT_TLSGD16_HA, R_PPC64_GOT_TLSGD16_LO,<br>
-; and R_PPC64_TLSGD for accessing external variable a, and R_PPC64_REL24<br>
-; for the call to __tls_get_addr.<br>
+; Verify generation of R_PPC64_GOT_TLSLD16_HA, R_PPC64_GOT_TLSLD16_LO,<br>
+; R_PPC64_TLSLD, R_PPC64_DTPREL16_HA, and R_PPC64_DTPREL16_LO for<br>
+; accessing external variable a, and R_PPC64_REL24 for the call to<br>
+; __tls_get_addr.<br>
 ;<br>
 ; CHECK:       '.rela.text'<br>
 ; CHECK:       Relocation 0<br>
<br>
<br>
_______________________________________________<br>
llvm-commits mailing list<br>
<a href="mailto:llvm-commits@cs.uiuc.edu" class="cremed">llvm-commits@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits" target="_blank" class="cremed">http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits</a><br>
</blockquote></div><br></div></div></div>