David E Hudak <dhu...@osc.edu> wrote on 11/25/2010 08:19:33 AM:

> FT is hitting a syntax error, but the code in question looks right. 
> 
> dhu...@opt-login01 1017%> make FT
> make -C FT fft-opt
> make[1]: Entering directory 
> `/nfs/07/dhudak/devel/x10/20101124r1/benchmarks/hpcc/FT'
> mkdir -p opt-gen/FT
> x10c++ -O -NO_CHECKS -d opt-gen -report postcompile=5 -x10rt mpi fft.x10 
Random.x10 -post '#  -O3 # # ' -o fft-opt
> /nfs/07/dhudak/devel/x10/20101124r1/benchmarks/hpcc/FT/fft.x10:3: 
> Syntax error: Token "*" expected instead of this input
> /nfs/07/dhudak/devel/x10/20101124r1/benchmarks/hpcc/FT/fft.x10:3-15: 
> Syntax error: Misplaced constructs(s): "ERROR_TOKEN"
> /nfs/07/dhudak/devel/x10/20101124r1/benchmarks/hpcc/FT/fft.x10:23: 
> Syntax error: Token(s) inserted to complete scope: "= 
VariableInitializer"
> /nfs/07/dhudak/devel/x10/20101124r1/benchmarks/hpcc/FT/fft.x10:23: 
> Syntax error: Token(s) inserted to complete scope: ";"
> /nfs/07/dhudak/devel/x10/20101124r1/benchmarks/hpcc/FT/fft.x10:123: 
> Syntax error: Token "=>" expected instead of this input
> 5 errors.
> make[1]: *** [fft-opt] Error 1
> make[1]: Leaving directory 
> `/nfs/07/dhudak/devel/x10/20101124r1/benchmarks/hpcc/FT'
> make: *** [FT-opt] Error 2

Dave,

Looks like FT has not been updated to the 2.1 syntax and APIs.

Some of the syntax has changed between 2.0 and 2.1.  These particular
syntax errors seem to be caused by the use of "const", which is no
longer a keyword in 2.1, in line 23, and the change in point
decomposition syntax in line 123 (the errors in line 3 are spurious,
and are caused by the parser getting confused).

After fixing those, there were more non-syntax errors caused by the
parser incorrectly parsing some of the constructs (the point
decomposition in lines 64, 160, 162, 163, 168, 172, and 200), the
change in Place API in line 121, and the change in API from (Val)Rail
to Array in line 192.  Also, the uses of Rail had to be replaced by
uses of Array(1).

I've fixed most of the obvious fft.x10 errors in SVN r18525, but cannot
change from the old Rail.copyTo API to the new Array.copy, as the
algorithm actually needs to be rewritten to use that API.  Hopefully
someone more familiar with the new API and the structure of the FT
code will take over and fix that one remaining issue.
        Igor
-- 
Igor Peshansky  (note the spelling change!)
IBM T.J. Watson Research Center
X10: Parallel Productivity and Performance (http://x10-lang.org/)
XJ: No More Pain for XML's Gain (http://www.research.ibm.com/xj/)
"I hear and I forget.  I see and I remember.  I do and I understand" -- 
Xun Zi


------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
X10-users mailing list
X10-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/x10-users

Reply via email to