[llvm-commits] [Mips] Direct object big endian review and submittal request (Rafael ?vila de Esp?ndola)

[Carter, Jack]

Rafael,

I slipped this in. It doesn't have anything to do with bigendian. It is an existing test case for direct object tls support that checks relocation records.

Evidently elf-dump changed to pad out with zeros causing this check to fail. The test case update uses regular expressions to zero or more padded zeros.

Jack

**********************************************

-; CHECK:     ('r_type', 0x2b)
-; CHECK:     ('r_type', 0x2c)
-; CHECK:     ('r_type', 0x2d)
+; CHECK:     ('r_type', 0x{{[0]*}}2b)
+; CHECK:     ('r_type', 0x{{[0]*}}2c)
+; CHECK:     ('r_type', 0x{{[0]*}}2d)

Why is this needed? The elf-dump script should be printing the value
with the correct number of bits (8 on 32 ELF and 32 on 64 bit ELF). Is
the script not doing the right thing for big endian ELF files?

Cheers,
Rafael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20120105/ff556862/attachment.html>