|
From: Harold N. <ha...@al...> - 2005-11-06 12:10:58
|
> As Tom says, we've never done SSE3. I believe you. However, I was mislead by the Release notes for Valgrind 2.= 2.0, which says, "Compared to the 2.0.0. stable release, 2.2.0 has much improved signals/syscalls/threads support, works well on recent Linux distros, improves SSE2/SSE3 support, ..." > However: > It might not be too hard to fix if you can supply a reproducer for the > failure -- for example, the program, test inputs and outputs, and a > convenient way to run it. Is that possible? I'll try to cook up a quick example for you. My guess is that if you just take the assembly instructions above and assemble it, that valgrind will choke, since it doesn't handle SSE3, right? Harold |
|
From: Nicholas N. <nj...@cs...> - 2005-11-06 23:44:00
|
On Sun, 6 Nov 2005, Harold Naparst wrote: > "Compared to the 2.0.0. stable release, 2.2.0 has much improved > signals/syscalls/threads support, works well on recent Linux distros, > improves SSE2/SSE3 support, ..." That's a documentation bug. What's the etiquette about chaning incorrect old release notes? Is it the done thing? It would be good to avoid repeating this confusion... Nick |