|
From: WAROQUIERS P. <phi...@eu...> - 2011-01-11 18:31:20
|
But similarly to the previous comment of Tom, your application code you would integrate and link in "valgrind tool code" will need to ensure all "writes" are properly "recorded". So, it looks the same kind of work to do it in your own code, or do it inside valgrind. So, if your often called function is relatively simple, and you know which "write" operations it is doing, you might just have a piece of code (in your application) which first tells what is being written by the function (using the client request to make a piece of memory defined), and then use the client request VALGRIND_NON_SIMD_CALLx to call the code on the native cpu. This can only (reasonably) be done if the function is quite heavy in cpu, but does not do a (lot) of writes which needs to be tracked. Philippe >-----Original Message----- >From: Oliver Schneider [mailto:ol...@f-...] >Sent: Friday 7 January 2011 16:03 >To: val...@li... >Subject: Re: [Valgrind-users] Run native code? > >Hi, > >thanks for your advice. I'll see whether I can manage to >implement that. >Nice trick :) > > >// Oliver > > ____ This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender. |