[Soot-list] Re: JEDD Unsatisfied Core

[Richard Warburton]

This can probably be ignored.  I believe this was a problem with the
way that I installed JEDD/zchaff on this machine.

  Richard

On 10/24/07, Richard Warburton <richard.warburton at gmail.com> wrote:
> With the existance of an attribute n, a physical domain N1 and a
> domain Node.  I was under the impression that the following code
> should compile (it is a minimal error case of what I'm trying to
> debug).  I am highly confused as to why it doesn't.
>
> ========================================
>
> import jedd.*;
> import jedd.order.*;
> import attributes.*;
> import domains.*;
> import physical_domains.*;
> import soot.jimple.ReturnVoidStmt;
>
> public class Test {
>
>         public <n:N1> FinalNodes;
>
>         public Test() {
>                 FinalNodes = 0B;
>         }
>
>         public void addReturn(ReturnVoidStmt node) {
>                 FinalNodes |= new { node=>n };
>         }
>
> }
>
> =============================================
>
>   Richard
>
> On 10/23/07, Richard Warburton <richard.warburton at gmail.com> wrote:
> > The 2004 paper on JEDD states that I can extract information about the
> > unsatisfied core in a manner that will allow me to infer where the
> > physical domain assignment conflicts are.  Unfortunately I can't find
> > documentation that tells me how I actually do it.  I have looked in "A
> > brief user's guide to JEDD" and the paper, but I don't understand.
> > The zchaff website was also lacking in documentation on this matter.
> > It would be most helpful if someone could explain what the steps are
> > to identify this information.
> >
> >   Richard Warburton
> >
>