|
From: Julian S. <js...@ac...> - 2011-04-20 09:25:34
|
> Since crypto cannot be modeled in an efficient way we first > thought that a dirty helper might be the right solution, but there are > some problems: > - Dirty can only have one memory area > - The length field (mSize) cannot be an IRTemp > > What might be a good approach to tackle these instruction? Can we enhance > Dirty helpers to accept multiple memory areas with dynamic length fields > (this would require changes in most tools, I guess)? This would be particularly complicated for Memcheck. See do_shadow_Dirty and do_origins_Dirty in mc_translate.c for the current handling. It's not pretty. Can you explain more about the instruction(s)? What exactly are the inputs and the outputs? I am wondering if this can be done somehow using clean helpers. J |