| florian | dec4a56 | 2011-11-26 04:12:01 +0000 | [diff] [blame] | 1 | |
| sewardj | b5b8740 | 2011-03-07 16:05:35 +0000 | [diff] [blame] | 2 | Requirements |
| 3 | ------------ |
| 4 | - You need GCC 3.4 or later to compile the s390 port. |
| 5 | - A working combination of autotools is required. |
| florian | 6fc11f2 | 2013-09-30 16:41:56 +0000 | [diff] [blame] | 6 | - To run valgrind a z10 machine or any later model is needed. |
| 7 | Older machine models down to and including z900 may work but have |
| 8 | not been tested extensively. |
| sewardj | b5b8740 | 2011-03-07 16:05:35 +0000 | [diff] [blame] | 9 | |
| 10 | |
| 11 | Limitations |
| 12 | ----------- |
| 13 | - 31-bit client programs are not supported. |
| 14 | - Hexadecimal floating point is not supported. |
| florian | be853a8 | 2013-10-01 07:01:08 +0000 | [diff] [blame^] | 15 | - memcheck, cachegrind, drd, helgrind, massif, lackey, and none are |
| florian | 6fc11f2 | 2013-09-30 16:41:56 +0000 | [diff] [blame] | 16 | supported. |
| 17 | - On machine models predating z10, cachegrind will assume a z10 cache |
| 18 | architecture. Otherwise, cachegrind will query the hosts cache system |
| 19 | and use those parameters. |
| florian | fb11d97 | 2012-11-02 22:00:59 +0000 | [diff] [blame] | 20 | - callgrind and all experimental tools are currently not supported. |
| sewardj | b5b8740 | 2011-03-07 16:05:35 +0000 | [diff] [blame] | 21 | - Some gcc versions use mvc to copy 4/8 byte values. This will affect some |
| 22 | debug messages. Valgrind will complain about 4 or 8 one-byte reads/writes |
| 23 | instead of just 1 read/write. |
| sewardj | b5b8740 | 2011-03-07 16:05:35 +0000 | [diff] [blame] | 24 | |
| 25 | |
| florian | 8f36de0 | 2012-08-23 00:44:22 +0000 | [diff] [blame] | 26 | Hardware facilities |
| 27 | ------------------- |
| 28 | Valgrind does not require that the host machine has the same hardware |
| 29 | facilities as the machine for which the client program was compiled. |
| 30 | This is convenient. The JIT compiler will translate the client instructions |
| 31 | according to the facilities available on the host. |
| 32 | This means, though, that probing for hardware facilities by issuing |
| 33 | instructions from that facility and observing whether SIGILL is thrown |
| 34 | may not work. As a consequence, programs that attempt to do so may |
| 35 | behave differently. It is believed that this is a rare use case. |
| 36 | |
| 37 | |
| sewardj | b5b8740 | 2011-03-07 16:05:35 +0000 | [diff] [blame] | 38 | Recommendations |
| 39 | --------------- |
| 40 | Applications should be compiled with -fno-builtin to avoid |
| 41 | false positives due to builtin string operations when running memcheck. |
| 42 | |
| 43 | |
| 44 | Reading Material |
| 45 | ---------------- |
| 46 | (1) Linux for zSeries ELF ABI Supplement |
| 47 | http://refspecs.linuxfoundation.org/ELF/zSeries/index.html |
| 48 | (2) z/Architecture Principles of Operation |
| florian | 46ac11b | 2012-09-19 16:43:30 +0000 | [diff] [blame] | 49 | http://publibfi.boulder.ibm.com/epubs/pdf/dz9zr009.pdf |
| sewardj | b5b8740 | 2011-03-07 16:05:35 +0000 | [diff] [blame] | 50 | (3) z/Architecture Reference Summary |
| florian | 46ac11b | 2012-09-19 16:43:30 +0000 | [diff] [blame] | 51 | http://publibfi.boulder.ibm.com/epubs/pdf/dz9zs007.pdf |