<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;"><font size="2"><span style="font-size: 10pt;">Rafael,<br>
<br>
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.<br>
<br>
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.<br>
<br>
Jack<br>
<br>
**********************************************<br>
<br>
-; CHECK: ('r_type', 0x2b)<br>
-; CHECK: ('r_type', 0x2c)<br>
-; CHECK: ('r_type', 0x2d)<br>
+; CHECK: ('r_type', 0x{{[0]*}}2b)<br>
+; CHECK: ('r_type', 0x{{[0]*}}2c)<br>
+; CHECK: ('r_type', 0x{{[0]*}}2d)<br>
<br>
Why is this needed? The elf-dump script should be printing the value<br>
with the correct number of bits (8 on 32 ELF and 32 on 64 bit ELF). Is<br>
the script not doing the right thing for big endian ELF files?<br>
<br>
Cheers,<br>
Rafael<br>
</span></font></div>
</body>
</html>