Back to bug 1296318
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2016-01-06 21:32:04 UTC | Keywords | Rebase | |
| Doc Type | Bug Fix | Rebase: Bug Fixes and Enhancements | ||
| John Skeoch | 2016-02-01 02:33:23 UTC | Blocks | 1297579 | |
| CC | mfranc | ohudlick | ||
| Martin Cermak | 2016-02-17 10:11:20 UTC | CC | mcermak | |
| Siddharth Nagar | 2016-03-01 15:30:41 UTC | Priority | unspecified | medium |
| Libor Miksik | 2016-03-01 17:43:57 UTC | Blocks | 1313485 | |
| Mark Wielaard | 2016-03-22 20:32:59 UTC | Docs Contact | rkratky | |
| Doc Text | Important: if this rebase instead contains *only bug fixes,* or *only enhancements*, select the correct option from the Doc Type drop-down list. Rebase package(s) to version: 3.11.0 from 3.10.0 in rhel-7.2 Highlights, important fixes, or notable enhancements: From the upstream NEWS file, these are the most interesting changes: * The JIT's register allocator is significantly faster, making the JIT as a whole somewhat faster, so JIT-intensive activities, for example program startup, are modestly faster, around 5%. * Intel AVX2 support is more complete (64 bit targets only). On AVX2 capable hosts, the simulated CPUID will now indicate AVX2 support. * Memcheck: - The default value for --leak-check-heuristics has been changed from "none" to "all". This helps to reduce the number of possibly lost blocks, in particular for C++ applications. - The default value for --keep-stacktraces has been changed from "malloc-then-free" to "malloc-and-free". This has a small cost in memory (one word per malloc-ed block) but allows Memcheck to show the 3 stacktraces of a dangling reference: where the block was allocated, where it was freed, and where it is acccessed after being freed. - The default value for --partial-loads-ok has been changed from "no" to "yes", so as to avoid false positive errors resulting from some kinds of vectorised loops. - A new monitor command 'xb <addr> <len>' shows the validity bits of <len> bytes at <addr>. The monitor command 'xb' is easier to use than get_vbits when you need to associate byte data value with their corresponding validity bits. - The 'block_list' monitor command has been enhanced: o it can print a range of loss records o it now accepts an optional argument 'limited <max_blocks>' to control the number of blocks printed. o if a block has been found using a heuristic, then 'block_list' now shows the heuristic after the block size. o the loss records/blocks to print can be limited to the blocks found via specified heuristics. - A new command line option, --expensive-definedness-checks=yes|no, has been added. This is useful for avoiding occasional invalid uninitialised-value errors in optimised code. Watch out for runtime degradation, as this can be up to 25%. As always, though, the slowdown is highly application specific. The default setting is "no". * The default value for the --smc-check option has been changed from "stack" to "all-non-file" on targets that provide automatic D-I cache coherence (x86, amd64 and s390x). The result is to provide, by default, transparent support for JIT generated and self-modifying code on all targets. There are many more changes/improvements, but the above are the most interesting IMHO. A full list can be found here: http://valgrind.org/docs/manual/dist.news.html |
|||
| Mark Wielaard | 2016-04-15 22:52:49 UTC | Status | NEW | ASSIGNED |
| Status | ASSIGNED | MODIFIED | ||
| Fixed In Version | valgrind-3.11.0-20.el7 | |||
| errata-xmlrpc | 2016-04-15 23:01:35 UTC | Status | MODIFIED | ON_QA |
| Miloš Prchlík | 2016-06-06 21:28:35 UTC | CC | mprchlik | |
| QA Contact | qe-baseos-tools | mprchlik | ||
| Miloš Prchlík | 2016-06-24 14:47:59 UTC | Status | ON_QA | VERIFIED |
| Lenka Špačková | 2016-08-17 13:36:55 UTC | Docs Contact | rkratky | tcapek |
| Robert Krátký | 2016-08-19 13:49:38 UTC | CC | rkratky | |
| Docs Contact | tcapek | rkratky | ||
| Doc Text | Important: if this rebase instead contains *only bug fixes,* or *only enhancements*, select the correct option from the Doc Type drop-down list. Rebase package(s) to version: 3.11.0 from 3.10.0 in rhel-7.2 Highlights, important fixes, or notable enhancements: From the upstream NEWS file, these are the most interesting changes: * The JIT's register allocator is significantly faster, making the JIT as a whole somewhat faster, so JIT-intensive activities, for example program startup, are modestly faster, around 5%. * Intel AVX2 support is more complete (64 bit targets only). On AVX2 capable hosts, the simulated CPUID will now indicate AVX2 support. * Memcheck: - The default value for --leak-check-heuristics has been changed from "none" to "all". This helps to reduce the number of possibly lost blocks, in particular for C++ applications. - The default value for --keep-stacktraces has been changed from "malloc-then-free" to "malloc-and-free". This has a small cost in memory (one word per malloc-ed block) but allows Memcheck to show the 3 stacktraces of a dangling reference: where the block was allocated, where it was freed, and where it is acccessed after being freed. - The default value for --partial-loads-ok has been changed from "no" to "yes", so as to avoid false positive errors resulting from some kinds of vectorised loops. - A new monitor command 'xb <addr> <len>' shows the validity bits of <len> bytes at <addr>. The monitor command 'xb' is easier to use than get_vbits when you need to associate byte data value with their corresponding validity bits. - The 'block_list' monitor command has been enhanced: o it can print a range of loss records o it now accepts an optional argument 'limited <max_blocks>' to control the number of blocks printed. o if a block has been found using a heuristic, then 'block_list' now shows the heuristic after the block size. o the loss records/blocks to print can be limited to the blocks found via specified heuristics. - A new command line option, --expensive-definedness-checks=yes|no, has been added. This is useful for avoiding occasional invalid uninitialised-value errors in optimised code. Watch out for runtime degradation, as this can be up to 25%. As always, though, the slowdown is highly application specific. The default setting is "no". * The default value for the --smc-check option has been changed from "stack" to "all-non-file" on targets that provide automatic D-I cache coherence (x86, amd64 and s390x). The result is to provide, by default, transparent support for JIT generated and self-modifying code on all targets. There are many more changes/improvements, but the above are the most interesting IMHO. A full list can be found here: http://valgrind.org/docs/manual/dist.news.html | Valgrind rebased to version 3.11.0 Valgrind 3.11.0 provides many improvements and bug fixes, including improved performance of the JIT register allocator, more complete support for Intel AVX2, new monitor commands, and better defaults for a number of parameters. |
||
| Tomas Capek | 2016-08-19 15:30:02 UTC | Doc Text | Valgrind rebased to version 3.11.0 Valgrind 3.11.0 provides many improvements and bug fixes, including improved performance of the JIT register allocator, more complete support for Intel AVX2, new monitor commands, and better defaults for a number of parameters. | _valgrind_ rebased to version 3.11.0 Valgrind is an instrumentation framework that is used for debugging memory, detecting memory leaks, and profiling applications. The package has been upgraded to upstream version 3.11.0. Highlighted improvements include: * The JIT's register allocator is now significantly faster, making JIT-intensive activities, for example program startup, approximately 5% faster. * Intel AVX2 support is now more complete for 64-bit targets. On AVX2-capable hosts, the simulated CPUID will now indicate AVX2 support. * The default value for the *--smc-check* option has been changed from `stack` to `all-non-file` on targets that provide automatic D-I cache coherence. The result is to provide, by default, transparent support for JIT generated and self-modifying code on all targets. Highlighted new features in the *Memcheck* utility include: * The default value for the *--leak-check-heuristics* option has been changed from `none` to `all`. This helps to reduce the number of possibly lost blocks, in particular for C++ applications. * The default value for the *--keep-stacktraces* option has been changed from `malloc-then-free` to `malloc-and-free`. This has a small cost in memory but allows *Memcheck* to show the 3 stack traces of a dangling reference: where the block was allocated, where it was freed, and where it is accessed after being freed. * The default value for the *--partial-loads-ok* option has been changed from `no` to `yes`, to avoid false-positive errors resulting from certain of vectorised loops. * A new monitor command "xb [addr] [len]" shows the validity bits of `[len]` bytes at `[addr]`. The monitor command "xb" is easier to use than *get_vbits* when you need to associate byte data value with their corresponding validity bits. * The "block_list" monitor command has been enhanced: it can print a range of loss records; it now accepts an optional argument `limited [max_blocks]` to control the number of printed blocks; if a block has been found using a heuristic, then "block_list" now shows the heuristic after the block size; the loss records/blocks to print can be limited to the blocks found via specified heuristics. * A new *--expensive-definedness-checks=yes|no* command line option has been added. This is useful for avoiding occasional invalid uninitialized-value errors in optimized code. Watch out for runtime degradation, as this can be up to 25%. The slowdown is highly application-specific though. The default value is `no`. |
| Robert Krátký | 2016-08-19 15:42:07 UTC | CC | mjw | |
| Doc Text | _valgrind_ rebased to version 3.11.0 Valgrind is an instrumentation framework that is used for debugging memory, detecting memory leaks, and profiling applications. The package has been upgraded to upstream version 3.11.0. Highlighted improvements include: * The JIT's register allocator is now significantly faster, making JIT-intensive activities, for example program startup, approximately 5% faster. * Intel AVX2 support is now more complete for 64-bit targets. On AVX2-capable hosts, the simulated CPUID will now indicate AVX2 support. * The default value for the *--smc-check* option has been changed from `stack` to `all-non-file` on targets that provide automatic D-I cache coherence. The result is to provide, by default, transparent support for JIT generated and self-modifying code on all targets. Highlighted new features in the *Memcheck* utility include: * The default value for the *--leak-check-heuristics* option has been changed from `none` to `all`. This helps to reduce the number of possibly lost blocks, in particular for C++ applications. * The default value for the *--keep-stacktraces* option has been changed from `malloc-then-free` to `malloc-and-free`. This has a small cost in memory but allows *Memcheck* to show the 3 stack traces of a dangling reference: where the block was allocated, where it was freed, and where it is accessed after being freed. * The default value for the *--partial-loads-ok* option has been changed from `no` to `yes`, to avoid false-positive errors resulting from certain of vectorised loops. * A new monitor command "xb [addr] [len]" shows the validity bits of `[len]` bytes at `[addr]`. The monitor command "xb" is easier to use than *get_vbits* when you need to associate byte data value with their corresponding validity bits. * The "block_list" monitor command has been enhanced: it can print a range of loss records; it now accepts an optional argument `limited [max_blocks]` to control the number of printed blocks; if a block has been found using a heuristic, then "block_list" now shows the heuristic after the block size; the loss records/blocks to print can be limited to the blocks found via specified heuristics. * A new *--expensive-definedness-checks=yes|no* command line option has been added. This is useful for avoiding occasional invalid uninitialized-value errors in optimized code. Watch out for runtime degradation, as this can be up to 25%. The slowdown is highly application-specific though. The default value is `no`. | _valgrind_ rebased to version 3.11.0 Valgrind is an instrumentation framework that is used for debugging memory, detecting memory leaks, and profiling applications. The package has been upgraded to upstream version 3.11.0. Highlighted improvements include: * The JIT's register allocator is now significantly faster, making JIT-intensive activities, for example program startup, approximately 5% faster. * Intel AVX2 support is now more complete for 64-bit targets. On AVX2-capable hosts, the simulated CPUID will now indicate AVX2 support. * The default value for the *--smc-check* option has been changed from `stack` to `all-non-file` on targets that provide automatic D-I cache coherence. The result is to provide, by default, transparent support for JIT generated and self-modifying code on all targets. Highlighted new features in the *Memcheck* utility include: * The default value for the *--leak-check-heuristics* option has been changed from `none` to `all`. This helps to reduce the number of possibly lost blocks, in particular for C++ applications. * The default value for the *--keep-stacktraces* option has been changed from `malloc-then-free` to `malloc-and-free`. This has a small cost in memory but allows *Memcheck* to show the 3 stack traces of a dangling reference: where the block was allocated, where it was freed, and where it is accessed after being freed. * The default value for the *--partial-loads-ok* option has been changed from `no` to `yes`, to avoid false-positive errors resulting from certain of vectorised loops. * A new monitor command "xb [addr] [len]" shows the validity bits of `[len]` bytes at `[addr]`. The monitor command "xb" is easier to use than *get_vbits* when you need to associate byte data value with their corresponding validity bits. * The "block_list" monitor command has been enhanced: it can print a range of loss records; it now accepts an optional argument, `limited [max_blocks]`, to control the number of printed blocks; if a block has been found using a heuristic, then "block_list" now shows the heuristic after the block size; the loss records/blocks to print can be limited to the blocks found via specified heuristics. * A new *--expensive-definedness-checks=yes|no* command line option has been added. This is useful for avoiding occasional invalid uninitialized-value errors in optimized code. Beware of potential runtime degradation, as this can be up to 25%. The slowdown is highly application-specific though. The default value is `no`. | ||
| Flags | needinfo?(mjw) | |||
| Mark Wielaard | 2016-08-23 11:38:40 UTC | Flags | needinfo?(mjw) | |
| Robert Krátký | 2016-08-23 13:58:22 UTC | Doc Text | _valgrind_ rebased to version 3.11.0 Valgrind is an instrumentation framework that is used for debugging memory, detecting memory leaks, and profiling applications. The package has been upgraded to upstream version 3.11.0. Highlighted improvements include: * The JIT's register allocator is now significantly faster, making JIT-intensive activities, for example program startup, approximately 5% faster. * Intel AVX2 support is now more complete for 64-bit targets. On AVX2-capable hosts, the simulated CPUID will now indicate AVX2 support. * The default value for the *--smc-check* option has been changed from `stack` to `all-non-file` on targets that provide automatic D-I cache coherence. The result is to provide, by default, transparent support for JIT generated and self-modifying code on all targets. Highlighted new features in the *Memcheck* utility include: * The default value for the *--leak-check-heuristics* option has been changed from `none` to `all`. This helps to reduce the number of possibly lost blocks, in particular for C++ applications. * The default value for the *--keep-stacktraces* option has been changed from `malloc-then-free` to `malloc-and-free`. This has a small cost in memory but allows *Memcheck* to show the 3 stack traces of a dangling reference: where the block was allocated, where it was freed, and where it is accessed after being freed. * The default value for the *--partial-loads-ok* option has been changed from `no` to `yes`, to avoid false-positive errors resulting from certain of vectorised loops. * A new monitor command "xb [addr] [len]" shows the validity bits of `[len]` bytes at `[addr]`. The monitor command "xb" is easier to use than *get_vbits* when you need to associate byte data value with their corresponding validity bits. * The "block_list" monitor command has been enhanced: it can print a range of loss records; it now accepts an optional argument, `limited [max_blocks]`, to control the number of printed blocks; if a block has been found using a heuristic, then "block_list" now shows the heuristic after the block size; the loss records/blocks to print can be limited to the blocks found via specified heuristics. * A new *--expensive-definedness-checks=yes|no* command line option has been added. This is useful for avoiding occasional invalid uninitialized-value errors in optimized code. Beware of potential runtime degradation, as this can be up to 25%. The slowdown is highly application-specific though. The default value is `no`. | _valgrind_ rebased to version 3.11.0 Valgrind is an instrumentation framework that is used for debugging memory, detecting memory leaks, and profiling applications. The package has been upgraded to upstream version 3.11.0. Highlighted improvements include: * The JIT's register allocator is now significantly faster, making JIT-intensive activities, for example program startup, approximately 5% faster. * Intel AVX2 support is now more complete for 64-bit targets. On AVX2-capable hosts, the simulated CPUID will now indicate AVX2 support. * The default value for the *--smc-check* option has been changed from `stack` to `all-non-file` on targets that provide automatic D-I cache coherence. The result is to provide, by default, transparent support for JIT generated and self-modifying code on all targets. Highlighted new features in the *Memcheck* utility include: * The default value for the *--leak-check-heuristics* option has been changed from `none` to `all`. This helps to reduce the number of possibly lost blocks, in particular for C++ applications. * The default value for the *--keep-stacktraces* option has been changed from `malloc-then-free` to `malloc-and-free`. This has a small cost in memory but allows *Memcheck* to show the 3 stack traces of a dangling reference: where the block was allocated, where it was freed, and where it is accessed after being freed. * The default value for the *--partial-loads-ok* option has been changed from `no` to `yes`, to avoid false-positive errors resulting from certain vectorised loops. * A new gdb monitor command "xb [addr] [len]" shows the validity bits of `[len]` bytes at `[addr]`. The monitor command "xb" is easier to use than *get_vbits* when you need to associate byte data value with their corresponding validity bits. * The "block_list" gdb monitor command has been enhanced: it can print a range of loss records; it now accepts an optional argument, `limited [max_blocks]`, to control the number of printed blocks; if a block has been found using a heuristic, then "block_list" now shows the heuristic after the block size; the loss records/blocks to print can be limited to the blocks found via specified heuristics. * A new *--expensive-definedness-checks=yes|no* command-line option has been added. This is useful for avoiding occasional invalid uninitialized-value errors in optimized code. Beware of potential runtime degradation, as this can be up to 25%. The slowdown is highly application-specific though. The default value is `no`. |
| errata-xmlrpc | 2016-11-02 11:28:54 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-11-04 02:55:33 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-11-03 22:55:33 UTC |
Back to bug 1296318