Re: More precise values in Analyzer

Joshua,

  Isn't value source can be derived from the opcode type that produced it?

  regards,
  Eugene


On Thu, Jul 15, 2010 at 3:56 PM,  <[email protected]> wrote:
>
> Hi,
>
> Im trying to use ASM in a Java-to-LLVM translator project.  In short, I'm using
> the Analyzer and a custom version of Value to (attempt to) extract a SSA form
> of the Java bytecode.
>
> The problem I am having is that some of the origins of the values are not
> precise enough.  For instance, at present, it seems impossible to track where
> some of the values originally came from - Analyzer.analyze just calls
> Interpreter.newValue(...) for uninitialized values, parameters, the this
> reference, etc.
>
> What do you recommend?
>
> Would I be able to get a patch through that gives the Interpreter room to
> distinguish between these?  I propose adding Interpreter.newParameter(int
> index, Type type), Interpreter.newReturnValue(Type type),
> Interpreter.newThisReference(Type type), and Interpreter.newUninitialized().
>
> FYI, I am using the stable 3.3 version - but the nightly SVN seems to have the
> same problem.
>
> Sincerely,
>
> Joshua Warner
>
>
> --
> 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