Re: Re: Re: Re: Fwd: Re: More precise values in Analyzer

Eugene,

That is all fine, but it still leaves the problem of how to detect what
local variable slot that value was created from, without modifying the
Analyzer.  Currently, the analyzer does not pass this information on to the
Interpreter when it calls newValue, and (correct me if I am wrong, but)
AbstractInstruction doesn't keep track of where loads came from (i.e. the
locals index) when copyOperation is called to perform the first load of the
parameter.

I don't mean to be stubborn, but I still think what I suggested in the
beginning (creating a few new hooks for the Interpreter) is the most direct
solution.

Sincerely,

Joshua

On Thu, Jul 15, 2010 at 8:20 PM, Eugene Kuleshov <[email protected]>wrote:

> Joshua Warner wrote:
>
>> I looked at SourceValue and SourceInterpreter, and it appears that when a
>> SourceValue comes from a parameter (or this pointer or exception variable),
>> it just reports the source as an empty set.
>>
>  So, an empty set would be an indication that value came from this or from
> method parameters and variable slot would give you parameter number Note to
> take value length into account, i.e. long will take two variables, so next
> params will be shifted to the following variables.
>
>  regards,
>  Eugene
>
>
>
>
> --
> You receive this message as a subscriber of the [email protected] mailing list.
> To unsubscribe: mailto:[email protected]
> For general help: mailto:[email protected]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>

-- 
You receive this message as a subscriber of the [email protected] mailing list.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws