Hello,
I am using X10 compiler svn revision r23082, which fixes the
async at and at async problems. I still cannot get the async
at(p){} code to work. It deadlocks. at(p) async{} works
fine. Also, using a val before the async at(p){} works fine (the
work around that Olivier) described before.
Another point. When I set X10_NTHREADS to 2, which is the number
of cores I got on my machine. The application somehow seems to
loose data. For example, I have a facial recognition system with
12 images. When I have X10_NTHREADS=1, then all 12 images are
recognised. But, when X10_THREADS=2, sometimes the system only
processes 4 images, discarding the other 8, sometimes it
processes only 6 images, etc.
Finally, I have only a single place Place(0). But, I purposely
set X10_NPLACES=2, just to see what happens. In this case the
program crashes without giving out any output.
I have compiled the X10 compiler without optimizations, I use
the GML (global matrix library) compiled with optimization
turned off and my own application (and streaming library that I
have built using X10) itself is compiled without optimizations
turned on.
Help is appreciated.
--
Regards,
Avinash Malik
------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Ciosco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
X10-users mailing list
X10-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/x10-users
