Ok, guys, this is interesting because on my machine I am seeing exactly
the same problem. First I thought it was be related to our new lab
machines but reading this, maybe it is not. The strange thing is that
just a few weeks ago everything worked fine when I started to work with
the points-to analysis. Then all the sudden (?) I got paddle crash on my
machine using the Sun JVM. After consulting Ondrej I used JRockit, which
I just gave another try today and with JRockit it also seems to take
forever just as this user reports. Personally I have no clue what could
cause this.
Ondrej would you have a bit of time to look into this? If you need any
more information, please let me know.
Eric
> -----Original Message-----
> From: Majordomo list server [mailto:majordomo@comlab.ox.ac.uk] On
> Behalf Of Eduardo S. Cordeiro
> Sent: Wednesday, August 09, 2006 3:14 PM
> To: abc-users@comlab.ox.ac.uk
> Subject: Re: [abc-users] -O3 runtime error
>
> Hello Ondrej and Eric,
>
> thanks for the replies; I noticed the problem with Paddle throwing an
> exception is solved on abc-1.2.1. I have another problem though --
with
> the -O3 flag turned on, and the -Xmx512M VM option, abc seems to run
> forever on my machine -- the most I've tried was going for over 20
> minutes when I shut it down.
>
> I don't actually need my optimization to run on -O3, however, because
> all I need is static information. The glitch seems to be that my
> optimization involves eliminating methods, and it appears that this
can
> only be done from a SceneTransformer. Adding SceneTransformers to the
> "bop" pack doesn't work though, and removing methods from a
> BodyTransformer is equally fruitless.
>
> I fear SceneTransformers can only be added to the "wjtp" pack...is
this
> true? If so, is there a way to remove methods from a BodyTransformer,
> or will -O3 be a requirement? (This might be pushing a little too
hard,
> but is it possible to run -O3 and bypass call graph creation and the
> other "wjtp" optimizations?)
>
> Thanks again for the help,
> Eduardo Cordeiro
>
> Ondrej Lhotak wrote:
> > On Thu, Aug 03, 2006 at 10:14:42AM -0400, Eric Bodden wrote:
> >
> >> You can get paddle from here:
> >> http://www.sable.mcgill.ca/~olhota/build/
> >>
> >
> > The machine that does those builds seems to not exist anymore.
> > Up-to-date builds are at:
> >
> > http://plg.uwaterloo.ca/~olhotak/build/
> >
> > I'll modify the web page to point to the up-to-date version.
> >
> > Ondrej
> >
> >
> >> Eric
> >>
> >>
> >>
> >>> -----Original Message-----
> >>> From: Majordomo list server [mailto:majordomo@comlab.ox.ac.uk] On
> >>> Behalf Of Eduardo S. Cordeiro
> >>> Sent: Wednesday, August 02, 2006 10:29 PM
> >>> To: abc-users@comlab.ox.ac.uk
> >>> Subject: Re: [abc-users] -O3 runtime error
> >>>
> >>> Eric and Ondrej,
> >>>
> >>> as a workaround, is it possible to disable at source code level
the
> >>> optimization that uses Paddle so that I can get my extension to
> run?
> >>>
> >>> Thanks and regards,
> >>> Eduardo Cordeiro
> >>>
> >>> Ondrej Lhotak wrote:
> >>>
> >>>
> >>>> This bug was reported and fixed in Paddle on April 27th (which,
> >>>> unfortunately, was after the abc 1.2.0 release). The fix should
> >>>>
> >> appear
> >>
> >>>> in the next release of abc.
> >>>>
> >>>> Ondrej
> >>>>
> >>>> On Wed, Aug 02, 2006 at 10:46:13AM -0300, Eduardo S. Cordeiro
> wrote:
> >>>>
> >>>>
> >>>>
> >>>>> Hello there,
> >>>>>
> >>>>> I've been trying to add an optimization to the wjtp pack, and so
> >>>>> abc must be executed with the -O3 option. When executed with
this
> >>>>>
> >> option,
> >>
> >>>>> abc generates the following error:
> >>>>>
> >>>>> Garbage collection #1: 1000003 nodes / 998323 free / 0.062s /
> >>>>> 0.062s total Exception in thread "main"
> >>>>>
> >> polyglot.util.InternalCompilerError:
> >>
> >>>>> unhandled exception during compilation
> >>>>> at abc.main.Main.run(Main.java:653)
> >>>>> at abc.main.Main.main(Main.java:211) Caused by:
> >>>>> java.lang.RuntimeException
> >>>>> at
> >>>>>
> >>>>
> soot.jimple.paddle.PaddleScene.makeSetFactories(PaddleScene.java:13
> >>>> 63
> >>>>
> >>> )
> >>>
> >>>>> at soot.jimple.paddle.PaddleScene.setup(PaddleScene.java:1284)
> >>>>> at
> >>>>>
> >>>
> soot.jimple.paddle.PaddleTransformer.setup(PaddleTransformer.java:84
> >>> )
> >>>
> >>>>> at
> >>>>>
> >>>>
> soot.jimple.paddle.PaddleTransformer.internalTransform(PaddleTransf
> >>>> or
> >>>>
> >>> mer.java:45)
> >>>
> >>>>> at soot.SceneTransformer.transform(SceneTransformer.java:39)
> >>>>> at
> >>>>>
> >>>
soot.jimple.paddle.PaddleHook.internalTransform(PaddleHook.java:43)
> >>>
> >>>>> at soot.SceneTransformer.transform(SceneTransformer.java:39)
> >>>>> at soot.Transform.apply(Transform.java:89)
> >>>>> at soot.RadioScenePack.internalApply(RadioScenePack.java:60)
> >>>>> at
> >>>>>
> >>>>
> soot.jimple.toolkits.callgraph.CallGraphPack.internalApply(CallGrap
> >>>> hP
> >>>>
> >>> ack.java:40)
> >>>
> >>>>> at soot.Pack.apply(Pack.java:110)
> >>>>> at
> >>>>>
> >>>
> abc.weaving.weaver.CflowAnalysisImpl.run(CflowAnalysisImpl.java:105)
> >>>
> >>>>> at abc.weaving.weaver.Weaver.runCflowAnalysis(Weaver.java:319)
> >>>>> at abc.weaving.weaver.Weaver.weave(Weaver.java:137)
> >>>>> at abc.main.Main.weave(Main.java:1064)
> >>>>> at abc.main.Main.run(Main.java:531)
> >>>>> ... 1 more
> >>>>>
> >>>>>
> >>>>> I thought this might be a problem with my extension, so I
removed
> >>>>>
> >> the
> >>
> >>>>> -ext option, but the error message still occurs. Is this an
error
> >>>>>
> >>> with
> >>>
> >>>>> my setup or maybe a known bug? I'm using abc 1.2.0 from the
> >>>>> abc-complete jar file.
> >>>>>
> >>>>> Thank you,
> >>>>> Eduardo Cordeiro
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >
> >
>
Received on Wed Aug 09 20:44:44 2006
This archive was generated by hypermail 2.1.8 : Tue Mar 06 2007 - 16:13:29 GMT