On 03/01/13 10:17, BL wrote: > I've got a question that worries me: I tried to profile a simulation driven > by a > non linear code using valgrind --tool=callgrind. When looking at numerical > statistics I realized that my non linear code use did not have same behavior > processed in and out of callgrind (slight differences in simulation code > results > + also variations in number of iterations to get the result). > As I want to analyze bottleneck in my non linear simulation code, > I realized that I can't do analysis based on this due to these differences. > Any clues where these differences comes from and how I can avoid them?
Your first stop should be to read this: http://www.valgrind.org/docs/manual/manual-core.html#manual-core.limits My guess is that the section headed "Valgrind has the following limitations in its implementation of x86/AMD64 floating point relative to IEEE754" will explain the problem you are seeing. Tom -- Tom Hughes ([email protected]) http://compton.nu/ ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_122712 _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
