| njn | daa82a5 | 2005-08-27 17:55:22 +0000 | [diff] [blame^] | 1 | ----------------------------------------------------------------------------- |
| 2 | Valgrind roadmap |
| 3 | ----------------------------------------------------------------------------- |
| 4 | |
| 5 | This file serves as a rough roadmap for Valgrind development. It shows a |
| 6 | minimal set of features we hope to implement for each version. It's in |
| 7 | reverse chronological order. |
| 8 | |
| 9 | 3.1.0 |
| 10 | ----- |
| 11 | Scheduled for around November 2005. |
| 12 | |
| 13 | * Get 32-bit and 64-bit programs working smoothly on AMD64 (Tom?). Several |
| 14 | levels of smoothness here, we should aim for at least level 3. |
| 15 | |
| 16 | 1. Be able to build a 32-bit valgrind on a 64-bit machine, so you can |
| 17 | build and install both, and manually choose between bin/valgrind and |
| 18 | bin64/valgrind. |
| 19 | 2. Build both automatically when installing. |
| 20 | 3. Choose the appropriate executable automatically at startup just from |
| 21 | "valgrind". |
| 22 | 4. With --trace-children=yes, allow 32-bit programs to exec 64-bit |
| 23 | programs and vice versa, and invoke the appropriate Valgrind |
| 24 | automatically. |
| 25 | |
| 26 | * Get PPC32 working usably with Memcheck (Julian). Has already improved a |
| 27 | lot since. Get Cachegrind working with it (Nick). |
| 28 | |
| 29 | * Rewrite address space manager; statically link the core with |
| 30 | each tool; remove all glibc dependencies (Julian). |
| 31 | |