[valgrind] [Bug 398445] uninitialized memory false reports on shared memory

2018-09-12 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=398445 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net --- Comment #6 from Ivo Raisr

[valgrind] [Bug 396290] [PATCH] Possible tool - allocfail

2018-08-22 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=396290 --- Comment #20 from Ivo Raisr --- Thank you for your work. This is going to be a useful Valgrind tool. I like the documentation for the latest patch. Reasoning explained well on examples. You could mention that the default behaviour (fail unseen

[valgrind] [Bug 396290] [PATCH] Possible tool - allocfail

2018-07-31 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=396290 --- Comment #14 from Ivo Raisr --- The current exp-allocfail crashes badly on my Ubuntu 18.04 box. When running './vg-in-place --tool=exp-allocfail /bin/date', it crashes at af_main.c:119. That's because i is equal to an equivalent of '-1' (4294967295

[valgrind] [Bug 396290] [PATCH] Possible tool - allocfail

2018-07-31 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=396290 --- Comment #13 from Ivo Raisr --- (In reply to roger.light from comment #8) > Created attachment 114229 [details] > Updated patch with fixes and text callstacks. Looks quite good. There are just few nits: - Please remove trailing whitespa

[valgrind] [Bug 396290] [PATCH] Possible tool - allocfail

2018-07-31 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=396290 --- Comment #10 from Ivo Raisr --- (In reply to Philippe Waroquiers from comment #9) > I am wondering also how much difficult it would be to somewhat more > generalise the tool. > > For example, we might want to make similar tests to c

[valgrind] [Bug 385409] s390x: z13 vector integer instructions not implemented

2018-07-31 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=385409 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net --- Comment #19 from Ivo Raisr

[valgrind] [Bug 396290] [PATCH] Possible tool - allocfail

2018-07-30 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=396290 --- Comment #7 from Ivo Raisr --- Alright, I think it would be preferable to have --num-callers used instead of --depth. Users are already familiar with --num-callers. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 384337] performance improvements to VEX register allocator v2 and v3

2018-07-30 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384337 Ivo Raisr changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution

[valgrind] [Bug 396290] [PATCH] Possible tool - allocfail

2018-07-30 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=396290 Ivo Raisr changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[valgrind] [Bug 381553] VEX register allocator v3

2018-07-24 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=381553 --- Comment #75 from Ivo Raisr --- And thank you, Julian, for your guidance. Unfortunately I won't be able to finish the VEX enhancement/rework residing in (I think) vex-jit-hacks-2 branch. Perhaps some brave soul will be able to continue... -- You

[valgrind] [Bug 395682] Reading debug info of binaries with readonly PT_LOAD segments

2018-07-15 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=395682 Ivo Raisr changed: What|Removed |Added CC||ori...@gmx.fr --- Comment #14 from Ivo Raisr

[valgrind] [Bug 384727] [PATCH]valgrind does not support debug info for read only segments (generated by LLD)

2018-07-15 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384727 Ivo Raisr changed: What|Removed |Added Resolution|--- |DUPLICATE Status|ASSIGNED

[valgrind] [Bug 384727] [PATCH]valgrind does not support debug info for read only segments (generated by LLD)

2018-07-12 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384727 Ivo Raisr changed: What|Removed |Added Ever confirmed|0 |1 Assignee|jsew...@acm.org

[valgrind] [Bug 390471] suppression by specification of source-file line number

2018-06-25 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=390471 Ivo Raisr changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[valgrind] [Bug 390471] suppression by specification of source-file line number

2018-06-25 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=390471 Ivo Raisr changed: What|Removed |Added Attachment #110691|0 |1 is obsolete

[valgrind] [Bug 390471] suppression by specification of source-file line number

2018-06-25 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=390471 Ivo Raisr changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0

[valgrind] [Bug 197915] 80-bit floats are not supported on x86 and x86-64

2018-04-01 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=197915 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added CC||iv...@ivosh.net --- Comme

[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails

2018-03-12 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=338252 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added CC||iv...@ivosh.net --- Comme

[valgrind] [Bug 390524] use of 0b prefix for binary constants

2018-03-06 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=390524 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[valgrind] [Bug 390524] use of 0b prefix for binary constants

2018-03-06 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=390524 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Assignee|jsew...@acm.org |iv...@ivosh.net -

[valgrind] [Bug 388862] Add replacements for wmemchr and wcsnlen on Linux

2018-03-02 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=388862 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Status|ASSIGNED|RESOLVED Reso

[valgrind] [Bug 388862] Add replacements for wmemchr and wcsnlen on Linux

2018-03-02 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=388862 --- Comment #10 from Ivo Raisr <iv...@ivosh.net> --- :-) There was also a problem with the actual replacement definition. For example wcsnlen had the following: #if defined(VGO_linux) STRNLEN(VG_Z_LIBC_SONAME, wcsnlen) STRNLEN(VG_Z_LIBC_

[valgrind] [Bug 388862] Add replacements for wmemchr and wcsnlen on Linux

2018-03-02 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=388862 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Attachment #42|0 |1 is ob

[valgrind] [Bug 388862] Add replacements for wmemchr and wcsnlen on Linux

2018-03-02 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=388862 --- Comment #7 from Ivo Raisr <iv...@ivosh.net> --- Oh, alright, let's make it Int also for wcslen() so the whole file is consistent. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 388862] Add replacements for wmemchr and wcsnlen on Linux

2018-03-02 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=388862 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Attachment #111086|0 |1 is ob

[valgrind] [Bug 388862] Add replacements for wmemchr and wcsnlen on Linux

2018-03-02 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=388862 --- Comment #4 from Ivo Raisr <iv...@ivosh.net> --- Thank you for the patch. I had to make some fixes to make it actually work and do not introduce regressions. Please review the attachment. -- You are receiving this mail because: You are watchi

[valgrind] [Bug 388862] Add replacements for wmemchr and wcsnlen on Linux

2018-03-02 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=388862 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Assignee|jsew...@acm.org |iv...@ivo

[valgrind] [Bug 388862] Add replacements for wmemchr and wcsnlen on Linux

2018-03-02 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=388862 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added CC||iv...@ivo

[valgrind] [Bug 390723] make xtree dump files world wide readable, similar to log files

2018-02-20 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=390723 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Resolution|--- |FIXED Status|AS

[valgrind] [Bug 390723] make xtree dump files world wide readable, similar to log files

2018-02-19 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=390723 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCON

[valgrind] [Bug 390723] make xtree dump files world wide readable, similar to log files

2018-02-19 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=390723 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Assignee|jsew...@acm.org |iv...@ivosh.net -

[valgrind] [Bug 390723] New: make xtree dump files world wide readable, similar to log files

2018-02-19 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=390723 Bug ID: 390723 Summary: make xtree dump files world wide readable, similar to log files Product: valgrind Version: 3.14 SVN Platform: Compiled Sources OS: Linux

[valgrind] [Bug 389065] valgrind meets gcc flag -Wlogical-op

2018-01-23 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=389065 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Resolution|--- |FIXED Status|AS

[valgrind] [Bug 384633] Add a simple progress-reporting facility

2018-01-20 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384633 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Status|CONFIRMED |RESOLVED Reso

[valgrind] [Bug 384633] Add a simple progress-reporting facility

2018-01-19 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384633 --- Comment #7 from Ivo Raisr <iv...@ivosh.net> --- Hi Julian, patch with Solaris implementation is attached. The patch has been refreshed to apply cleanly to the latest git HEAD and a NEWS entry added. It is ready to be pushed - let me know if I

[valgrind] [Bug 384633] Add a simple progress-reporting facility

2018-01-19 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384633 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Attachment #109872|0 |1 is ob

[valgrind] [Bug 389065] valgrind meets gcc flag -Wlogical-op

2018-01-18 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=389065 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #4 fr

[valgrind] [Bug 389065] valgrind meets gcc flag -Wlogical-op

2018-01-18 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=389065 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Assignee|jsew...@acm.org |iv...@ivosh.net --- Comm

[valgrind] [Bug 384633] Add a simple progress-reporting facility

2018-01-17 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384633 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confi

[valgrind] [Bug 389065] valgrind meets gcc flag -Wlogical-op

2018-01-16 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=389065 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added CC||iv...@ivo

[valgrind] [Bug 388895] LibVEX_FrontEnd assertion failure: `0 == sizeof(VexGuestX86State) % LibVEX_GUEST_STATE_ALIGN'

2018-01-13 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=388895 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added CC||iv...@ivosh.net --- Comm

[valgrind] [Bug 385408] s390x: z13 vector "support" instructions not implemented

2018-01-11 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=385408 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added CC||iv...@ivo

[valgrind] [Bug 388493] exp-sgcheck fails on DW_TAG_subrange_type

2018-01-03 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=388493 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added CC||iv...@ivosh.net --- Comm

[valgrind] [Bug 381819] amd64: unhandled instruction bextr (0x8F 0xEA 0x78 0x10 0xD0 0x8 0x4) from BMI1

2017-12-28 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=381819 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added CC||x...@fictionpress.com --- C

[valgrind] [Bug 328357] TBM bextr instruction unsupported vex amd64->IR: unhandled instruction bytes: 0x8F 0xEA 0xF8 0x10 0xEF 0x3 0x5 0x0

2017-12-28 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=328357 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Resolution|--- |DUPLICATE

[valgrind] [Bug 381819] amd64: unhandled instruction bextr (0x8F 0xEA 0x78 0x10 0xD0 0x8 0x4) from BMI1

2017-12-28 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=381819 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added CC||sgtcapsl...@lavab

[valgrind] [Bug 322586] Unknown instruction (bextr) in ld-2.15.so with --march=native on AMD FX-8350

2017-12-28 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=322586 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Resolution|--- |DUPLICATE

[valgrind] [Bug 381819] amd64: unhandled instruction bextr (0x8F 0xEA 0x78 0x10 0xD0 0x8 0x4) from BMI1

2017-12-28 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=381819 --- Comment #16 from Ivo Raisr <iv...@ivosh.net> --- Created attachment 109550 --> https://bugs.kde.org/attachment.cgi?id=109550=edit support for TBM bextr Patch originally attached to bug https://bugs.kde.org/show_bug.cgi?id=322586 by &q

[valgrind] [Bug 381819] amd64: unhandled instruction bextr (0x8F 0xEA 0x78 0x10 0xD0 0x8 0x4) from BMI1

2017-12-28 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=381819 --- Comment #15 from Ivo Raisr <iv...@ivosh.net> --- (In reply to Bernd Buschinski from comment #14) > any chance we can push/fix/update this to official valgrind? I would happy > to test new patches :) As discussed previously, the pa

[valgrind] [Bug 387766] asm shifts cause false positive "Conditional jump or move depends on uninitialised value"

2017-12-10 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=387766 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added CC||iv...@ivosh.net --- Comm

[valgrind] [Bug 208052] strlcpy error when n = 0

2017-11-14 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=208052 --- Comment #9 from Ivo Raisr <iv...@ivosh.net> --- Fixed in commit a5af4146e383dd442130905901b046e2cb4b0ed4, https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=a5af4146e383dd442130905901b046e2cb4b0ed4 NEWS updated in

[valgrind] [Bug 208052] strlcpy error when n = 0

2017-11-13 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=208052 --- Comment #7 from Ivo Raisr <iv...@ivosh.net> --- Tom, would you mind integrating the fix into Valgrind source code base at this point? Alternatively, I could do it myself - just let me know. -- You are receiving this mail because: You are wa

[valgrind] [Bug 208052] strlcpy error when n = 0

2017-11-07 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=208052 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCON

[valgrind] [Bug 385939] Optionally exit on the first error

2017-11-04 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=385939 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Resolution|--- |FIXED Status|AS

[valgrind] [Bug 386318] valgrind.org/info/tools.html is missing SGCheck

2017-10-31 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=386318 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Assignee|jsew...@acm.org |iv...@ivosh.net -

[valgrind] [Bug 386318] valgrind.org/info/tools.html is missing SGCheck

2017-10-31 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=386318 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Reso

[valgrind] [Bug 376257] helgrind history full speed up using a cached stack

2017-10-30 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=376257 --- Comment #5 from Ivo Raisr <iv...@ivosh.net> --- Nice work, Philippe! I have just one question. In helgrind/hg_main.c, the last hunk, there is a message containing a weird character: "re-àsetting it to 0". Is this intended? -- Y

[valgrind] [Bug 386318] valgrind.org/info/tools.html is missing SGCheck

2017-10-30 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=386318 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added CC||iv...@ivosh.net --- Comm

[valgrind] [Bug 385939] Optionally exit on the first error

2017-10-24 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=385939 --- Comment #2 from Ivo Raisr <iv...@ivosh.net> --- Thank you for the patch and kudos for documenting the new option in the manual. >From the high level perspective, I have the following comments and questions: * It is not clear wha

[valgrind] [Bug 385939] Optionally exit on the first error

2017-10-24 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=385939 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Component|memcheck|general Summary|

[valgrind] [Bug 385939] Option to exit on first error

2017-10-24 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=385939 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added CC||iv...@ivo

[valgrind] [Bug 384676] VEX AMD64 backend should list more real registers as available for the register allocator

2017-10-19 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384676 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Resolution|--- |WONTFIX

[valgrind] [Bug 385843] [PATCH] ARM: mark caller-save VFP registes as trashed by calls

2017-10-17 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=385843 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCON

[valgrind] [Bug 385843] [PATCH] ARM: mark caller-save VFP registes as trashed by calls

2017-10-17 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=385843 --- Comment #9 from Ivo Raisr <iv...@ivosh.net> --- (In reply to Sindre Aamås from comment #6) > I have not looked at the stats, but the output is as follows. As suspected, there is a code bloat in the generated code because of the additional

[valgrind] [Bug 385843] [PATCH] ARM: mark caller-save VFP registes as trashed by calls

2017-10-16 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=385843 --- Comment #5 from Ivo Raisr <iv...@ivosh.net> --- Your fix touches register allocation. It is crucial that both ARMInstr_Call() and getRRegUniverse_ARM() are kept in sync (hinted in getRRegUniverse_ARM as well) and that register all

[valgrind] [Bug 385843] [PATCH] ARM: mark caller-save VFP registes as trashed by calls

2017-10-16 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=385843 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added CC||iv...@ivosh.net --- Comm

[valgrind] [Bug 384987] VEX register allocator: allocate caller-save registers for short lived vregs

2017-10-11 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384987 --- Comment #21 from Ivo Raisr <iv...@ivosh.net> --- Thank you all for your responses! They were really helpful. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 384987] VEX register allocator: allocate caller-save registers for short lived vregs

2017-10-11 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384987 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Status|ASSIGNED|RESOLVED Reso

[valgrind] [Bug 384987] VEX register allocator: allocate caller-save registers for short lived vregs

2017-10-11 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384987 --- Comment #19 from Ivo Raisr <iv...@ivosh.net> --- (In reply to Julian Seward from comment #17) > I expect arm(32) would also get a quite big improvement, because > it's also pretty low on registers. [This is not a request to measure, &

[valgrind] [Bug 384987] VEX register allocator: allocate caller-save registers for short lived vregs

2017-10-04 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384987 --- Comment #16 from Ivo Raisr <iv...@ivosh.net> --- I've fixed the problem with duplicate hregIsVirtual() in host_arch_defs.c files. Here are the performance numbers for amd64 and x86: Running inner Memcheck on perf/bz2 (compiled with -O

[valgrind] [Bug 384987] VEX register allocator: allocate caller-save registers for short lived vregs

2017-10-04 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384987 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Attachment #108135|0 |1 is ob

[valgrind] [Bug 384987] VEX register allocator: allocate caller-save registers for short lived vregs

2017-10-04 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384987 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Attachment #108134|0 |1 is ob

[valgrind] [Bug 384987] VEX register allocator: allocate caller-save registers for short lived vregs

2017-10-03 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384987 --- Comment #6 from Ivo Raisr <iv...@ivosh.net> --- I've tested on amd64, ppc8le and arm64 architectures. In all cases, the produced code was more compact and overall performance better, when running inner Memcheck on perf/bz2. Numbers are

[valgrind] [Bug 384987] VEX register allocator: allocate caller-save registers for short lived vregs

2017-10-03 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384987 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Attachment #107964|0 |1 is ob

[valgrind] [Bug 384987] VEX register allocator: allocate caller-save registers for short lived vregs

2017-10-03 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384987 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Attachment #107963|0 |1 is ob

[valgrind] [Bug 384987] VEX register allocator: allocate caller-save registers for short lived vregs

2017-10-03 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384987 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added See Also||https://bugs.kde.org/

[valgrind] [Bug 384337] performance improvements to VEX register allocator v2 and v3

2017-10-03 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384337 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added See Also||https://bugs.kde.org/

[valgrind] [Bug 384987] VEX register allocator: allocate caller-save registers for short lived vregs

2017-09-23 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384987 --- Comment #3 from Ivo Raisr <iv...@ivosh.net> --- The only remaining thing is to refactor isMove callbacks in the remaining architectures so that the information is available directly in HRegUsage. -- You are receiving this mail becaus

[valgrind] [Bug 384987] VEX register allocator: allocate caller-save registers for short lived vregs

2017-09-23 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384987 --- Comment #2 from Ivo Raisr <iv...@ivosh.net> --- Created attachment 107964 --> https://bugs.kde.org/attachment.cgi?id=107964=edit register allocation -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 384987] VEX register allocator: allocate caller-save registers for short lived vregs

2017-09-23 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384987 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Status|CONFIRMED |ASSIGNED -- You are rec

[valgrind] [Bug 384987] VEX register allocator: allocate caller-save registers for short lived vregs

2017-09-23 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384987 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added CC||iv...@ivosh.net --- Comm

[valgrind] [Bug 384987] New: VEX register allocator: allocate caller-save registers for short lived vregs

2017-09-23 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384987 Bug ID: 384987 Summary: VEX register allocator: allocate caller-save registers for short lived vregs Product: valgrind Version: 3.14 SVN Platform: Compiled Sources

[valgrind] [Bug 384987] VEX register allocator: allocate caller-save registers for short lived vregs

2017-09-23 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384987 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Ever confirmed|0 |1 Assigne

[valgrind] [Bug 384337] performance improvements to VEX register allocator v2 and v3

2017-09-22 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384337 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Attachment #107674|0 |1 is ob

[valgrind] [Bug 384732] posix_spawn with glibc 2.25 causes an assertion

2017-09-19 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384732 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added CC||iv...@ivosh.net --- Comm

[valgrind] [Bug 384729] __libc_freeres inhibits cross-platform valgrind

2017-09-15 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384729 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added CC||iv...@ivosh.net --- Comm

[valgrind] [Bug 384584] Callee saved registers listed first for AMD64, X86, and PPC architectures

2017-09-14 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384584 --- Comment #6 from Ivo Raisr <iv...@ivosh.net> --- At the end only %r11 was removed from the list in getRegUsage_AMD64Instr() because it's used overall as a temporary register for destination address. %rax, %rcx, %rdx could in theory b

[valgrind] [Bug 384584] Callee saved registers listed first for AMD64, X86, and PPC architectures

2017-09-14 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384584 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Resolution|--- |FIXED Status|AS

[valgrind] [Bug 384676] VEX AMD64 backend should list more real registers as available for the register allocator

2017-09-14 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384676 --- Comment #2 from Ivo Raisr <iv...@ivosh.net> --- Unfortunately performance measurements do not confirm this as a good idea. Measuring Memcheck on perf/bz2, instruction count: v3 baseline: 45,110 M total; 168 M register allocator v3 patched:

[valgrind] [Bug 384584] Callee saved registers listed first for AMD64, X86, and PPC architectures

2017-09-13 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384584 --- Comment #4 from Ivo Raisr <iv...@ivosh.net> --- The part with %rax, %rcx, %rdx, %r11 removal from getRegUsage_AMD64Instr() will be removed from the patch. The reason is explained in greater detail in: Bug 384676 - VEX AMD64 backend should lis

[valgrind] [Bug 384584] Callee saved registers listed first for AMD64, X86, and PPC architectures

2017-09-13 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384584 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added See Also||https://bugs.kde.org/

[valgrind] [Bug 384676] VEX AMD64 backend should list more real registers as available for the register allocator

2017-09-13 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384676 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added See Also||https://bugs.kde.org/

[valgrind] [Bug 384676] VEX AMD64 backend should list more real registers as available for the register allocator

2017-09-13 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384676 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added CC||iv...@ivosh.net --- Comm

[valgrind] [Bug 384676] VEX AMD64 backend should list more real registers as available for the register allocator

2017-09-13 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384676 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added Ever confirmed|0 |1 Assigne

[valgrind] [Bug 384676] New: VEX AMD64 backend should list more real registers as available for the register allocator

2017-09-13 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384676 Bug ID: 384676 Summary: VEX AMD64 backend should list more real registers as available for the register allocator Product: valgrind Version: 3.14 SVN Platform: Compiled Sources

[valgrind] [Bug 384633] Add a simple progress-reporting facility

2017-09-13 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384633 --- Comment #3 from Ivo Raisr <iv...@ivosh.net> --- And also please add the line explanation somewhere. User manual, verbose output... -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 384633] Add a simple progress-reporting facility

2017-09-13 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384633 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added CC||iv...@ivosh.net --- Comm

[valgrind] [Bug 384584] Callee saved registers listed first for AMD64, X86, and PPC architectures

2017-09-11 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384584 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added CC||iv...@ivosh.net --- Comm

[valgrind] [Bug 384584] Callee saved registers listed first for AMD64, X86, and PPC architectures

2017-09-11 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384584 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added See Also||https://bugs.kde.org/

[valgrind] [Bug 384337] performance improvements to VEX register allocator v2 and v3

2017-09-11 Thread Ivo Raisr
https://bugs.kde.org/show_bug.cgi?id=384337 Ivo Raisr <iv...@ivosh.net> changed: What|Removed |Added See Also||https://bugs.kde.org/

  1   2   3   4   5   6   >