On 06/09/14 13:16, Olivier Goffart wrote: > On Monday 09 June 2014 09:53:37 Bart Van Assche wrote: >> If g++ would be modified such that the "if (!guard.first_byte)" test can >> be skipped at run-time then it would become possible for Helgrind and >> DRD to recognize static initialization by intercepting the >> __cxa_guard_*() functions. However, I'm not sure which mechanism the gcc >> maintainers will prefer for disabling that if-test at run-time. > > Just an idea: Is it not possible to record guard's address on > __cxa_guard_release, and then consider that an access to guard as an happens > after? > I don't know the internals of helgrind, so I can't say if it is possible, or > if it would be too slow. > Or is __cxa_guard_* used for more than the static initialization?
This is certainly possible but I don't see how to implement this without slowing down Helgrind and DRD significantly. Bart. ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://www.hpccsystems.com _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
