Jim LaGrone <jlagr...@cs.uh.edu> wrote on 11/13/2009 06:10:30 PM:
> When compiling an app I received the following output. Versions are at
> the bottom. I didn't get this when using the option -commandlineonly.
> Any ideas about what the problem might be?
>
> $ x10c -d ../bin *.x10
> Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
> at x10.constraint.XPromise_c.intern(XPromise_c.java:260)
> at x10.constraint.XPromise_c.intern(XPromise_c.java:264)
> at x10.constraint.XPromise_c.intern(XPromise_c.java:264)
> at x10.constraint.XVar_c.internIntoConstraint(XVar_c.java:23)
> at x10.constraint.XConstraint_c.intern(XConstraint_c.java:225)
> at x10.constraint.XConstraint_c.intern(XConstraint_c.java:193)
> at x10.constraint.XConstraint_c.addBinding(XConstraint_c.java:315)
> at x10.constraint.XConstraint_c.addTerm(XConstraint_c.java:973)
> at x10.constraint.XConstraint_c.substitute(XConstraint_c.java:741)
> at polyglot.ext.x10.types.Subst.subst(Subst.java:49)
> at polyglot.ext.x10.types.Subst.subst(Subst.java:63)
> at polyglot.ext.x10.types.Subst.subst(Subst.java:130)
> at
polyglot.ext.x10.types.X10ParsedClassType_c.interfaces(X10ParsedClassType_c.java:164)
> at polyglot.types.TypeSystem_c.hasMethodNamed(TypeSystem_c.java:775)
> at
polyglot.ext.x10.types.X10TypeSystem_c.hasMethodNamed(X10TypeSystem_c.java:2419)
> at
polyglot.ext.x10.types.X10TypeSystem_c.hasMethodNamed(X10TypeSystem_c.java:2410)
> at
polyglot.ext.x10.types.X10TypeSystem_c.hasMethodNamed(X10TypeSystem_c.java:2410)
> at polyglot.ext.x10.ast.X10Call_c.superFindMethod(X10Call_c.java:114)
> at polyglot.ext.x10.ast.X10Call_c.superFindMethod(X10Call_c.java:158)
> at polyglot.ext.x10.ast.X10Call_c.superFindMethod(X10Call_c.java:158)
> at polyglot.ext.x10.ast.X10Call_c.superFindMethod(X10Call_c.java:158)
> at polyglot.ext.x10.ast.X10Call_c.superFindMethod(X10Call_c.java:158)
> at polyglot.ext.x10.ast.X10Call_c.findMethod(X10Call_c.java:170)
> at
polyglot.ext.x10.ast.X10Call_c.typeCheckNullTarget(X10Call_c.java:183)
> at polyglot.ext.x10.ast.X10Call_c.typeCheck(X10Call_c.java:312)
> at polyglot.ast.JL_c.typeCheck(JL_c.java:180)
> at polyglot.visit.TypeChecker.leaveCall(TypeChecker.java:106)
> at
polyglot.visit.ErrorHandlingVisitor.leaveCall(ErrorHandlingVisitor.java:141)
> at
polyglot.visit.ErrorHandlingVisitor.leave(ErrorHandlingVisitor.java:279)
> at polyglot.visit.ContextVisitor.leave(ContextVisitor.java:140)
> at
polyglot.visit.NodeVisitor.visitEdgeNoOverride(NodeVisitor.java:258)
> at polyglot.visit.NodeVisitor.visitEdge(NodeVisitor.java:217)
> $ x10c -version
> x10c version 1.7.7
> Polyglot compiler toolkit version 3.1.1 (2009-10-22 12:00:56)
Pretty obvious: you're out of memory.
If you don't use -commandlineonly, x10c++ will attempt to compile all of
XRX, which is a hefty bit of code.
You can increase the heap size by using -J-Xmx512M.
Igor
--
Igor Peshansky (note the spelling change!)
IBM T.J. Watson Research Center
XJ: No More Pain for XML's Gain (http://www.research.ibm.com/xj/)
X10: Parallel Productivity and Performance (http://x10.sf.net/)
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
X10-users mailing list
X10-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/x10-users
