Re: [Valgrind-developers] Valgrind and OpenMP

[Sérgio D. J. <ser...@li...>]

Hi guys,

I'm sorry for the absence. I was a little busy working with other things
here :-).

After a few moments thinking about our (long and useful) discussion, I
have another question. It has to do with one of my proposals:

On Wed, 2008-10-15 at 11:42 -0200, Sérgio Durigan Júnior wrote:

> 2) Julian said that detecting locking primitives using only instructions
> is too complex, maybe impossible. Well, but as far as I understood, you
> are assuming a "general locking primitives detector". What if we limit
> this problem only to the locking primitives present in the libgomp?
> Would that be easier to do? (Of course it has a down side because every
> time the libgomp changed, we would have to change Valgrind too... But I
> think it's a valid question anyway)

Basically, I'd like to know: if I start to implement this idea, what are
the chances for me to have to change something in the VEX "package"?
Will I certainly have to modify VEX's source, or only Valgrind's core?

I don't know if you guys can answer this, but you certainly are more
capable than me.

Thanks in advance,

-- 
Sérgio Durigan Júnior
Linux on Power Toolchain - Software Engineer
Linux Technology Center - LTC
IBM Brazil