blob: 003d5c819a363762464c237c2dd84c5faf336019 [file] [log] [blame]
Elliott Hughesa0664b92017-04-18 17:46:52 -07001<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>8. README.S390</title>
5<link rel="stylesheet" type="text/css" href="vg_basic.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
7<link rel="home" href="index.html" title="Valgrind Documentation">
8<link rel="up" href="dist.html" title="Valgrind Distribution Documents">
9<link rel="prev" href="dist.readme-packagers.html" title="7. README_PACKAGERS">
10<link rel="next" href="dist.readme-android.html" title="9. README.android">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
13<div><table class="nav" width="100%" cellspacing="3" cellpadding="3" border="0" summary="Navigation header"><tr>
14<td width="22px" align="center" valign="middle"><a accesskey="p" href="dist.readme-packagers.html"><img src="images/prev.png" width="18" height="21" border="0" alt="Prev"></a></td>
15<td width="25px" align="center" valign="middle"><a accesskey="u" href="dist.html"><img src="images/up.png" width="21" height="18" border="0" alt="Up"></a></td>
16<td width="31px" align="center" valign="middle"><a accesskey="h" href="index.html"><img src="images/home.png" width="27" height="20" border="0" alt="Up"></a></td>
17<th align="center" valign="middle">Valgrind Distribution Documents</th>
18<td width="22px" align="center" valign="middle"><a accesskey="n" href="dist.readme-android.html"><img src="images/next.png" width="18" height="21" border="0" alt="Next"></a></td>
19</tr></table></div>
20<div class="chapter">
21<div class="titlepage"><div><div><h1 class="title">
22<a name="dist.readme-s390"></a>8. README.S390</h1></div></div></div>
23<div class="literallayout"><p><br>
24      <br>
25Requirements<br>
26------------<br>
27- You need GCC 3.4 or later to compile the s390 port.<br>
28- To run valgrind a z10 machine or any later model is recommended.<br>
29  Older machine models down to and including z990 may work but have<br>
30  not been tested extensively.<br>
31<br>
32<br>
33Limitations<br>
34-----------<br>
35- 31-bit client programs are not supported.<br>
36- Hexadecimal floating point is not supported.<br>
37- Transactional memory is not supported.<br>
38- Instructions operating on vector registers are not supported.<br>
39- memcheck, cachegrind, drd, helgrind, massif, lackey, and none are<br>
40  supported. <br>
41- On machine models predating z10, cachegrind will assume a z10 cache<br>
42  architecture. Otherwise, cachegrind will query the hosts cache system<br>
43  and use those parameters.<br>
44- callgrind and all experimental tools are currently not supported.<br>
45- Some gcc versions use mvc to copy 4/8 byte values. This will affect<br>
46  certain debug messages. For example, memcheck will complain about<br>
47  4 one-byte reads/writes instead of just a single read/write.<br>
48- The transactional-execution facility is not supported; it is masked<br>
49  off from HWCAP.<br>
50- The vector facility is not supported; it is masked off from HWCAP.<br>
51<br>
52<br>
53Hardware facilities<br>
54-------------------<br>
55Valgrind does not require that the host machine has the same hardware<br>
56facilities as the machine for which the client program was compiled.<br>
57This is convenient. If possible, the JIT compiler will translate the<br>
58client instructions according to the facilities available on the host.<br>
59This means, though, that probing for hardware facilities by issuing<br>
60instructions from that facility and observing whether SIGILL is thrown<br>
61may not work. As a consequence, programs that attempt to do so may<br>
62behave differently. It is believed that this is a rare use case.<br>
63<br>
64<br>
65Recommendations<br>
66---------------<br>
67Applications should be compiled with -fno-builtin to avoid<br>
68false positives due to builtin string operations when running memcheck.<br>
69<br>
70<br>
71Reading Material<br>
72----------------<br>
73(1) Linux for zSeries ELF ABI Supplement<br>
74    http://refspecs.linuxfoundation.org/ELF/zSeries/index.html<br>
75(2) z/Architecture Principles of Operation<br>
76    http://publibfi.boulder.ibm.com/epubs/pdf/dz9zr010.pdf<br>
77(3) z/Architecture Reference Summary<br>
78    http://publibfi.boulder.ibm.com/epubs/pdf/dz9zs008.pdf<br>
79<br>
80    </p></div>
81</div>
82<div>
83<br><table class="nav" width="100%" cellspacing="3" cellpadding="2" border="0" summary="Navigation footer">
84<tr>
85<td rowspan="2" width="40%" align="left">
86<a accesskey="p" href="dist.readme-packagers.html">&lt;&lt; 7. README_PACKAGERS</a> </td>
87<td width="20%" align="center"><a accesskey="u" href="dist.html">Up</a></td>
88<td rowspan="2" width="40%" align="right"> <a accesskey="n" href="dist.readme-android.html">9. README.android &gt;&gt;</a>
89</td>
90</tr>
91<tr><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td></tr>
92</table>
93</div>
94</body>
95</html>