|
From: Anssi H. <ans...@bi...> - 2020-08-07 12:36:49
|
Hi all, I ported the Valgrind amd64 SSE4+AES+PCLMUL code to x86. The patchset is too large to post here on the ML, so it is here: https://github.com/anssih/valgrind/commits/x86-sse4 This is useful to us as we are targeting some embedded Intel Silvermont x86 customer hardware running a 32-bit vendor OS. I've tested the patches with the ported regression tests, and our production application also works under Valgrind after the changes. I understand if this is something you don't want to apply at this time, in which case we'll continue to maintain this support out-of-tree. I expect we will continue to have a need for this for many years in the future - the hardware is not close to retirement. -- Anssi Hannula / Bitwise Oy +358 503803997 |
|
From: Philippe W. <phi...@sk...> - 2020-08-20 19:29:30
|
Might be a good idea to file a bug on bugzilla and attach the patch (not that this means it will necessarily be applied then but it has more chance to not be forgotten). Philippe On Fri, 2020-08-07 at 15:11 +0300, Anssi Hannula via Valgrind-developers wrote: > Hi all, > > I ported the Valgrind amd64 SSE4+AES+PCLMUL code to x86. > > The patchset is too large to post here on the ML, so it is here: > https://github.com/anssih/valgrind/commits/x86-sse4 > > This is useful to us as we are targeting some embedded Intel Silvermont > x86 customer hardware running a 32-bit vendor OS. > > I've tested the patches with the ported regression tests, and our > production application also works under Valgrind after the changes. > > I understand if this is something you don't want to apply at this time, > in which case we'll continue to maintain this support out-of-tree. > I expect we will continue to have a need for this for many years in the > future - the hardware is not close to retirement. > |