Menu
▾
▴
x10-users — A list for X10 users
You can subscribe to this list here.
| 2007 |
Jan
(2) |
Feb
(24) |
Mar
(7) |
Apr
(20) |
May
|
Jun
(5) |
Jul
|
Aug
(3) |
Sep
(4) |
Oct
(14) |
Nov
(6) |
Dec
(16) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(3) |
Feb
(8) |
Mar
(5) |
Apr
(17) |
May
(10) |
Jun
(5) |
Jul
(16) |
Aug
(1) |
Sep
(1) |
Oct
(8) |
Nov
|
Dec
(2) |
| 2009 |
Jan
(6) |
Feb
|
Mar
(6) |
Apr
(10) |
May
(5) |
Jun
(7) |
Jul
(20) |
Aug
(61) |
Sep
(30) |
Oct
(37) |
Nov
(48) |
Dec
(42) |
| 2010 |
Jan
(35) |
Feb
(29) |
Mar
(29) |
Apr
(36) |
May
(41) |
Jun
(70) |
Jul
(120) |
Aug
(63) |
Sep
(45) |
Oct
(33) |
Nov
(88) |
Dec
(77) |
| 2011 |
Jan
(83) |
Feb
(81) |
Mar
(13) |
Apr
(5) |
May
(13) |
Jun
(38) |
Jul
(11) |
Aug
(53) |
Sep
(18) |
Oct
(12) |
Nov
(45) |
Dec
(8) |
| 2012 |
Jan
(5) |
Feb
(28) |
Mar
(7) |
Apr
(18) |
May
(56) |
Jun
(39) |
Jul
(31) |
Aug
(6) |
Sep
(22) |
Oct
(14) |
Nov
(32) |
Dec
(9) |
| 2013 |
Jan
(12) |
Feb
(51) |
Mar
(19) |
Apr
(36) |
May
(12) |
Jun
(20) |
Jul
(20) |
Aug
(14) |
Sep
(6) |
Oct
(24) |
Nov
(27) |
Dec
(17) |
| 2014 |
Jan
(10) |
Feb
(25) |
Mar
(26) |
Apr
(22) |
May
(30) |
Jun
(15) |
Jul
(10) |
Aug
(19) |
Sep
(16) |
Oct
(44) |
Nov
(24) |
Dec
(25) |
| 2015 |
Jan
(1) |
Feb
(5) |
Mar
(21) |
Apr
(3) |
May
(8) |
Jun
(2) |
Jul
(1) |
Aug
(1) |
Sep
(12) |
Oct
(18) |
Nov
(4) |
Dec
(10) |
| 2016 |
Jan
(9) |
Feb
(9) |
Mar
(6) |
Apr
(4) |
May
(1) |
Jun
(8) |
Jul
(24) |
Aug
(1) |
Sep
(1) |
Oct
(6) |
Nov
(12) |
Dec
|
| 2017 |
Jan
|
Feb
(5) |
Mar
(4) |
Apr
(3) |
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
(2) |
Feb
|
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|
From: Igor P. <ig...@us...> - 2007-10-05 14:57:39
|
Jab,
You are welcome.
Igor
Jab Vorci <jab...@ya...> wrote on 10/05/2007 07:34:11 PM:
> Thank you very much for your answer and fast reply. Everything is
> working perfectly now!
>
> best regards.
>
> ----- Original Message ----
> From: Igor Peshansky <igorp at us.ibm.com>
> To: Jab Vorci <jabvorci at yahoo.com>
> Cc: x10-users at lists.sourceforge.net
> Sent: Friday, October 5, 2007 3:49:02 PM
> Subject: Re: [X10-users] Installation error while installing X10DT
> plugin for Eclipse 3.1.2
>
>
> Jab Vorci <jab...@ya...> wrote on 10/05/2007 06:49:24 PM:
>
> > Dear colleagues,
> >
> > I'm trying to install X10DT plug-in for eclipse 3.1.2 (on windows XP)
> > following procedure described on X10 home site:
> >
> > http://x10.sourceforge.net/x10downloads.shtml
> >
> > However I'm receiving the error message:
> >
> > "SAFARI Runtime (1.0.56) requires feature "lpg.runtime (2.0.5)", or
> > compatible."
> >
> > I'm using JDK 1.5.0 update 12.
> >
> > Any comments are welcome.
> > Thanks in advance.
>
> Jab,
>
> I think the page may be a bit outdated. You also need to install
> the LPG runtime plugin from the LPG SF update site. Add the following
> URL to your Eclipse update sites list:
>
> http://lpg.sourceforge.net/updates/
>
> (I gave it a name "LPG Release Update Site"), and installing X10DT
> should pull in lpg.runtime version 2.0.5.
> 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/)
|
|
From: Igor P. <ig...@us...> - 2007-10-05 13:49:56
|
Jab Vorci <jab...@ya...> wrote on 10/05/2007 06:49:24 PM: > Dear colleagues, > > I'm trying to install X10DT plug-in for eclipse 3.1.2 (on windows XP) > following procedure described on X10 home site: > > http://x10.sourceforge.net/x10downloads.shtml > > However I'm receiving the error message: > > "SAFARI Runtime (1.0.56) requires feature "lpg.runtime (2.0.5)", or > compatible." > > I'm using JDK 1.5.0 update 12. > > Any comments are welcome. > Thanks in advance. Jab, I think the page may be a bit outdated. You also need to install the LPG runtime plugin from the LPG SF update site. Add the following URL to your Eclipse update sites list: http://lpg.sourceforge.net/updates/ (I gave it a name "LPG Release Update Site"), and installing X10DT should pull in lpg.runtime version 2.0.5. 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/) |
|
From: Jab V. <jab...@ya...> - 2007-10-05 13:19:32
|
Dear colleagues, =0A=0AI'm trying to install X10DT plug-in for eclipse 3.1.= 2 (on windows XP) following procedure described on X10 home site: =0A=0Ahtt= p://x10.sourceforge.net/x10downloads.shtml =0A=0AHowever I'm receiving the = error message: =0A=0A"SAFARI Runtime (1.0.56) requires feature "lpg.runtime= (2.0.5)", or compatible." =0A=0AI'm using JDK 1.5.0 update 12. =0A=0AAny c= omments are welcome. =0A=0AThanks in advance.=0A=0A=0A =0A___________= _________________________________________________________________________= =0ABe a better Globetrotter. Get better travel answers from someone who kno= ws. Yahoo! Answers - Check it out.=0Ahttp://answers.yahoo.com/dir/?link=3Dl= ist&sid=3D396545469 |
|
From: Vijay S. <vi...@sa...> - 2007-09-10 12:39:53
|
Jim White wrote: >I notice the 1.5 release of X10 at sourceforge. Is there a corresponding >release of X10DT and do they both support the June 30, 2007 language >spec? > > Yes. The X10DT release is at http://eclipse-imp.sourceforge.net/updates/ Please check it out. Best, Vijay -- X10: Programming parallel machines, productively (http://x10.sf.net) |
|
From: Robert M. F. <rf...@wa...> - 2007-09-10 12:21:40
|
Byeongcheol Lee wrote: > I'm a grad student at UT Austin. I have been looking for a solution for > line number mapping in the source-to-source translation. How did you deal > with the mapping from the java byte code index to the x10 line number? > > SMAP in JSR-45 would be one possiblity, but I'm not sure if the current > JDK(6 or 7) has a good support for the JSR-45. For instance, the stack dump in > JDK(6 or 7) wouldn't be sensitive to the SMAP information. jdb would not > understand the break command like "break 10 example.x10." > > If you are not using the SMAP feature, how did you solve this line number > mapping problem. As far as I know, the JDK up to now does not support > #line directive. > Hi there, The X10DT just creates SMAP using a simple classfile post-processor that scans source files looking for "#line" directives that the x10 compiler places in the generated Java files. The upside is that the Eclipse Java debugger looks for and handles the SMAP attributes, so that breakpoints and pausing the running program can work. The downside is that, as you said, backtraces don't take the SMAP attributes into account. I haven't yet checked to see what Java 7 may do along these lines, but I'm pretty sure that Java 6 doesn't do anything sensible. I also believe that the Java 6 version of javac doesn't provide for anything like #line source directives. We'd love to see a more complete solution to this issue, but unfortunately it would presumably require some minor (though possibly backward-compatible) VM changes. -- Cheers, -- Bob =================================================== Robert M. Fuhrer, rf...@wa... Programming Technologies Department IBM T. J. Watson Research Center |
|
From: Byeongcheol L. <bc...@cs...> - 2007-09-10 06:07:55
|
Hi, I'm a grad student at UT Austin. I have been looking for a solution for line number mapping in the source-to-source translation. How did you deal with the mapping from the java byte code index to the x10 line number? SMAP in JSR-45 would be one possiblity, but I'm not sure if the current JDK(6 or 7) has a good support for the JSR-45. For instance, the stack dump in JDK(6 or 7) wouldn't be sensitive to the SMAP information. jdb would not understand the break command like "break 10 example.x10." If you are not using the SMAP feature, how did you solve this line number mapping problem. As far as I know, the JDK up to now does not support #line directive. thanks, BK |
|
From: Jim W. <Jim...@nu...> - 2007-09-06 07:18:02
|
I notice the 1.5 release of X10 at sourceforge. Is there a corresponding release of X10DT and do they both support the June 30, 2007 language spec? Thanks. /Jim White |
|
From: Vijay S. <vi...@sa...> - 2007-08-21 10:41:42
|
Indeed, very much! We do have a new spec out -- please check http://x10.cvs.sourceforge.net/x10/x10.man/v1.0/x10.pdf?view=log This includes a new section on annotations. (The link on the main documentation page will soon be updated to this link.) In addition, we have prepared a paper for submission on the constraint-based dependent type system for X10. This will also be out on the documentation page soon. Best, Vijay Jim White wrote: >It's been 8 1/2 months since the last X10 specification. Is this >project live? Thanks. /Jim White > >------------------------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. >Still grepping through log files to find problems? Stop. >Now Search log events and configuration files using AJAX and a browser. >Download your FREE copy of Splunk now >> http://get.splunk.com/ >_______________________________________________ >X10-users mailing list >X10...@li... >https://lists.sourceforge.net/lists/listinfo/x10-users > > > > -- X10: Programming parallel machines, productively (http://x10.sf.net) |
|
From: Jim W. <Jim...@nu...> - 2007-08-21 09:54:35
|
It's been 8 1/2 months since the last X10 specification. Is this project live? Thanks. /Jim White |
|
From: Jim W. <Jim...@nu...> - 2007-08-01 16:04:42
|
It's been eight months since the last X10 specification. Any idea when an updated spec. will appear? Will that spec. define generics and closures? Thanks. /Jim White |
|
From: <nat...@gm...> - 2007-06-13 20:21:25
|
Jim, The next spec will not include generics or closures. These haven't been implemented yet. They will be in a later version of the language, however. Cheers, Nate On 6/12/07, Igor Peshansky <ig...@us...> wrote: > Jim White wrote on 06/09/2007 01:47:44 PM: > > > Vijay, Will the end-of-June specification define generics and closures? > > The current spec. suggested that it would. Thanks. /Jim White > > Jim, > > The next spec should include some form of generics, as they are already > part of the X10 implementation. They will most likely be different from > Java generics. Closures are being developed, but I'm not sure if they'll > make it into that spec. > 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/) > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > X10-users mailing list > X10...@li... > https://lists.sourceforge.net/lists/listinfo/x10-users > |
|
From: Igor P. <ig...@us...> - 2007-06-12 21:20:33
|
Jim White wrote on 06/09/2007 01:47:44 PM:
> Vijay, Will the end-of-June specification define generics and closures?
> The current spec. suggested that it would. Thanks. /Jim White
Jim,
The next spec should include some form of generics, as they are already
part of the X10 implementation. They will most likely be different from
Java generics. Closures are being developed, but I'm not sure if they'll
make it into that spec.
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/)
|
|
From: Jim W. <Jim...@nu...> - 2007-06-09 17:47:50
|
Vijay, Will the end-of-June specification define generics and closures? The current spec. suggested that it would. Thanks. /Jim White |
|
From: Vijay S. <vi...@sa...> - 2007-06-09 05:40:41
|
We will revise the reference manual end of this month. Nate Nystrom has just added compiler support for user-defined annotations, so that will be documented. Various errors that we know of will be corrected. If you have any comments/feedback, please send that in. Jim White wrote: >It's been six months since the last X10 specification. Any idea when an >updated spec. might appear? /Jim White > >------------------------------------------------------------------------- >This SF.net email is sponsored by DB2 Express >Download DB2 Express C - the FREE version of DB2 express and take >control of your XML. No limits. Just data. Click to get it now. >http://sourceforge.net/powerbar/db2/ >_______________________________________________ >X10-users mailing list >X10...@li... >https://lists.sourceforge.net/lists/listinfo/x10-users > > > > -- X10: Programming parallel machines, productively (http://x10.sf.net) |
|
From: Jim W. <Jim...@nu...> - 2007-06-09 05:34:03
|
It's been six months since the last X10 specification. Any idea when an updated spec. might appear? /Jim White |
|
From: Anderson, T. A <tod...@in...> - 2007-04-11 20:34:03
|
If I have a cluster where each node has multiple cores then what is currently done? Do you have one "X10 place" per node or one "X10 place" per core? If it is the latter, do you strictly require that something allocated to one core can only run on that core or do you allow it to run on any core within the node? =20 thanks, =20 Todd |
|
From: Vijay S. <vi...@sa...> - 2007-04-11 10:06:56
|
Igor Peshansky wrote: >Aniruddha, > >Actually, this looks like a different bug. When processing local >declarations, the compiler does not check the "value"ness of the local >being declared, and so e ends up referencing the same object as f (which >is not a value array). Thanks for the report. > Igor > > Right, the compiler should flag this program as illegal (and does not do so now). The right idiom is double [.] f = new double [ [1:5, 1:5] ]; final double value [.] e = f.toValueArray(); This should work. Best, Vijay >"Shet, Aniruddha G." wrote on 04/10/2007 09:15:07 PM: > > > >>Igor, >> >>This probably is the same problem, but just to be sure... >> >>double [.] f = new double [ [1:5, 1:5] ]; >>final double value [.] e = f; >> >>e should be a value copy of the local reference array f and hence >>accessible from any place. But a BadPlaceException is currently thrown >>due to the bug. Is my understanding correct? >> >>Thanks, >>Aniruddha >> >>-----Original Message----- >>From: Igor Peshansky >>Sent: Wednesday, April 04, 2007 1:04 PM >>To: Shet, Aniruddha G. >>Cc: x10-users<at>lists.sourceforge.net >>Subject: Re: [X10-users] Array assignment & update/overlay >> >>Igor Peshansky wrote on 04/04/2007 12:24:30 PM: >> >> >> >>>Aniruddha, >>> >>>No, b *is* a copy, but not a value array. >>> >>>This is actually a bug in the X10 runtime libraries' implementation. >>>The restriction ("|") operator does not create a value array, even if >>>applied to a value array. That's why you get the place checks, etc. >>>We'll need to fix this. >>> >>>In the meantime, you can turn off place checks using the >>>-BAD_PLACE_RUNTIME_CHECK=false runtime option. If you don't want to >>>do that, you can make sure a value copy is created by using the >>>following snippet: >>> >>>final double value [.] a_sub = a | subD; final double value [.] b >>>(point p) { return a_sub[p]; }; >>> >>> >>Sorry, I meant >> >>final double value[] b = new double[a_sub.distribution] (point p) { >>return a_sub[p]; }; >> >> >> >>>(Vijay will, hopefully, correct me if this is wrong). >>> Igor >>> >>>"Shet, Aniruddha G." wrote on 04/04/2007 11:09:29 AM: >>> >>> >>> >>>>Igor, >>>> >>>>In the code that I sent, if b were declared as >>>> >>>>final double value [.] b = a | subD; >>>> >>>>can I expect a local copy to be created or is b treated only as a >>>>reference to a section of a? I see that a BadPlaceException is >>>>thrown when I try to access an element in b, which indicates that no >>>> >>>> >>>>local >>>> >>>> >>copy >> >> >>>>is created. >>>> >>>>Thanks, >>>>Aniruddha >>>> >>>>-----Original Message----- >>>>From: Igor Peshansky >>>>Sent: Wednesday, April 04, 2007 1:13 AM >>>>To: Shet, Aniruddha G. >>>>Cc: x10-users<at>lists.sourceforge.net >>>>Subject: RE: [X10-users] Array assignment & update/overlay >>>> >>>>Aniruddha, >>>> >>>>Thanks for the detailed report. I've reproduced the first problem >>>> >>>> >>here. >> >> >>>>We'll debug it and get back >>>>to you. In the meantime, since you're on an SMP, you can turn off >>>>BadPlaceExceptions by using the -BAD_PLACE_RUNTIME_CHECK=false >>>> >>>> >>option. >> >> >>>>The second problem is a bug, but only because the code to throw the >>>>appropriate kind of exception never got written, so an assertion is >>>>tripped instead. >>>> Igor >>>> >>>>"Shet, Aniruddha G." wrote on 04/03/2007 11:20:10 PM: >>>> >>>> >>>> >>>>>Hi Igor, >>>>> >>>>>In the foll piece of code, the activity at place 0 is trying to >>>>> >>>>> >>update >> >> >>>>>a locally allocated reference array with a block from a >>>>>distributed value >>>>>array:- >>>>> >>>>>public class test { >>>>> final region R = [1:20, 1:20]; >>>>> final dist D = dist.factory.block(R); >>>>> final double value [.] a = new double value [D] (point >>>>> >>>>> >>[i,j]) >> >> >>>>>{return i+j;}; >>>>> >>>>> public void run() { >>>>> async(here) { >>>>> double [.] b = new double [ [15:19, 1:5] >>>>> >>>>> >>]; >> >> >>>>> final dist subD = D | [15:19, 1:5]; >>>>> b.update(a | subD); >>>>> } >>>>> } >>>>> >>>>> public static void main(String[] args) { >>>>> new test().run(); >>>>> } >>>>>} >>>>> >>>>>This code throws the foll error when run with 4 places:- >>>>> >>>>>Exception in thread "pool-0-thread-0: Main Activity" >>>>>BadPlaceException(dist. array, var location=place(id=2) access at >>>>>place=place(id=0)) >>>>> at x10.lang.Runtime.hereCheckPlace(Runtime.java:313) >>>>> at x10.array.DoubleArray.get(DoubleArray.java:103) >>>>> at x10.array.DoubleArray.get(DoubleArray.java:100) >>>>> at x10.array.DoubleArray.update(DoubleArray.java:389) >>>>> at test$2.runX10Task(test.java:133) >>>>> at >>>>> >>>>> >>>>> >>x10.runtime.InvocationStrategy$DefaultStrategy.invokeX10Task(Invocatio >> >> >>>>>nS >>>>>trategy.java:57) >>>>> at x10.runtime.Activity.run(Activity.java:192) >>>>> at >>>>> >>>>> >>>>> >>java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecu >> >> >>>>>to >>>>>r.java:665) >>>>> at >>>>> >>>>> >>>>> >>java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor. >> >> >>>>>ja >>>>>va:690) >>>>> at java.lang.Thread.run(Thread.java:799) >>>>> >>>>> >>>>> >>>>>I would like some more clarifications here -- >>>>> >>>>>-- If I were to def b as "double [.] b = new double [ [1:5, 1:5] >>>>> >>>>> >>]" >> >> >>>>>and leave subD unchanged, then I get the error:- >>>>> >>>>>Exception in thread "pool-0-thread-0: Main Activity" >>>>>java.lang.AssertionError >>>>> at x10.array.DoubleArray.update(DoubleArray.java:382) >>>>> at test$2.runX10Task(test.java:133) >>>>> at >>>>> >>>>> >>>>> >>x10.runtime.InvocationStrategy$DefaultStrategy.invokeX10Task(Invocatio >> >> >>>>>nS >>>>>trategy.java:57) >>>>> at x10.runtime.Activity.run(Activity.java:192) >>>>> at >>>>> >>>>> >>>>> >>java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecu >> >> >>>>>to >>>>>r.java:665) >>>>> at >>>>> >>>>> >>>>> >>java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor. >> >> >>>>>ja >>>>>va:690) >>>>> at java.lang.Thread.run(Thread.java:799) >>>>> >>>>>b here has the same shape and size as before, but a different >>>>>index >>>>> >>>>> >>>>set. >>>> >>>> >>>>>I feel that such a capability is desirable. >>>>> >>>>>-- Correct me if I am wrong in saying that if two arrays have >>>>>identical regions but different distributions, then >>>>>assignment/update/overlay operations should run correctly so long >>>>>as >>>>> >>>>> >>>>>the locality rule is not violated. >>>>> >>>>>Thanks, >>>>>Aniruddha >>>>>----------------------------------------------------------- >>>>>Aniruddha G. Shet |Email: sh...@or... >>>>>Oak Ridge National Laboratory |Phone: +1 (865) 576 5606 >>>>>http://www.csm.ornl.gov/~anish12/ |Fax: +1 (865) 576 5491 >>>>>----------------------------------------------------------- >>>>> >>>>>-----Original Message----- >>>>>From: Igor Peshansky >>>>>Sent: Tuesday, April 03, 2007 9:41 PM >>>>>To: Shet, Aniruddha G. >>>>>Cc: x10-users<at>lists.sourceforge.net >>>>>Subject: Re: [X10-users] Array assignment & update/overlay >>>>> >>>>>Shet, Aniruddha G. wrote on 04/03/2007 09:25:03 PM: >>>>> >>>>> >>>>> >>>>>>Hi, >>>>>> >>>>>>My understanding is that array assignment and update/overlay >>>>>>operations are not designed to operate on arrays that do not >>>>>> >>>>>> >>having >> >> >>>>>>matching distributions, even though they may have matching >>>>>> >>>>>> >>regions? >> >> >>>>>>I am seeing that an activity that tries to update a local >>>>>> >>>>>> >>reference >> >> >>>>>>type array with a subdistribution of a global array that is >>>>>>final value type fails with BadPlaceException. The local array >>>>>>and the subdistribution have identical regions. The locality >>>>>>rule is not being >>>>>> >>>>>> >>>>>>violated here. Is the mismatch of distributions the reason for >>>>>> >>>>>> >>>>>failure? >>>>> >>>>>Hi, Aniruddha, >>>>> >>>>>This behavior sounds like a bug. The way you described it, it >>>>>certainly does not correspond to the X10 language definition. >>>>> >>>>>It would help greatly in debugging this problem if you could >>>>>reduce >>>>> >>>>> >>it >> >> >>>>>to a simple (and preferably short) test case. Feel free to post >>>>>it >>>>> >>>>> >>to >> >> >>>>>the list or enter it in Bugzilla. It would also help if you could >>>>> >>>>> >>>>>show the full stack trace of the BadPlaceException you're getting. >>>>> Igor >>>>> >>>>> > > > -- X10: Programming parallel machines, productively (http://x10.sf.net) |
|
From: Igor P. <ig...@us...> - 2007-04-11 02:34:03
|
Aniruddha,
Actually, this looks like a different bug. When processing local
declarations, the compiler does not check the "value"ness of the local
being declared, and so e ends up referencing the same object as f (which
is not a value array). Thanks for the report.
Igor
"Shet, Aniruddha G." wrote on 04/10/2007 09:15:07 PM:
> Igor,
>
> This probably is the same problem, but just to be sure...
>
> double [.] f = new double [ [1:5, 1:5] ];
> final double value [.] e = f;
>
> e should be a value copy of the local reference array f and hence
> accessible from any place. But a BadPlaceException is currently thrown
> due to the bug. Is my understanding correct?
>
> Thanks,
> Aniruddha
>
> -----Original Message-----
> From: Igor Peshansky
> Sent: Wednesday, April 04, 2007 1:04 PM
> To: Shet, Aniruddha G.
> Cc: x10-users<at>lists.sourceforge.net
> Subject: Re: [X10-users] Array assignment & update/overlay
>
> Igor Peshansky wrote on 04/04/2007 12:24:30 PM:
>
> > Aniruddha,
> >
> > No, b *is* a copy, but not a value array.
> >
> > This is actually a bug in the X10 runtime libraries' implementation.
> > The restriction ("|") operator does not create a value array, even if
> > applied to a value array. That's why you get the place checks, etc.
> > We'll need to fix this.
> >
> > In the meantime, you can turn off place checks using the
> > -BAD_PLACE_RUNTIME_CHECK=false runtime option. If you don't want to
> > do that, you can make sure a value copy is created by using the
> > following snippet:
> >
> > final double value [.] a_sub = a | subD; final double value [.] b
> > (point p) { return a_sub[p]; };
>
> Sorry, I meant
>
> final double value[] b = new double[a_sub.distribution] (point p) {
> return a_sub[p]; };
>
> > (Vijay will, hopefully, correct me if this is wrong).
> > Igor
> >
> > "Shet, Aniruddha G." wrote on 04/04/2007 11:09:29 AM:
> >
> > > Igor,
> > >
> > > In the code that I sent, if b were declared as
> > >
> > > final double value [.] b = a | subD;
> > >
> > > can I expect a local copy to be created or is b treated only as a
> > > reference to a section of a? I see that a BadPlaceException is
> > > thrown when I try to access an element in b, which indicates that no
>
> > > local
> copy
> > > is created.
> > >
> > > Thanks,
> > > Aniruddha
> > >
> > > -----Original Message-----
> > > From: Igor Peshansky
> > > Sent: Wednesday, April 04, 2007 1:13 AM
> > > To: Shet, Aniruddha G.
> > > Cc: x10-users<at>lists.sourceforge.net
> > > Subject: RE: [X10-users] Array assignment & update/overlay
> > >
> > > Aniruddha,
> > >
> > > Thanks for the detailed report. I've reproduced the first problem
> here.
> > >
> > > We'll debug it and get back
> > > to you. In the meantime, since you're on an SMP, you can turn off
> > > BadPlaceExceptions by using the -BAD_PLACE_RUNTIME_CHECK=false
> option.
> > >
> > > The second problem is a bug, but only because the code to throw the
> > > appropriate kind of exception never got written, so an assertion is
> > > tripped instead.
> > > Igor
> > >
> > > "Shet, Aniruddha G." wrote on 04/03/2007 11:20:10 PM:
> > >
> > > > Hi Igor,
> > > >
> > > > In the foll piece of code, the activity at place 0 is trying to
> update
> > >
> > > > a locally allocated reference array with a block from a
> > > > distributed value
> > > > array:-
> > > >
> > > > public class test {
> > > > final region R = [1:20, 1:20];
> > > > final dist D = dist.factory.block(R);
> > > > final double value [.] a = new double value [D] (point
> [i,j])
> > > > {return i+j;};
> > > >
> > > > public void run() {
> > > > async(here) {
> > > > double [.] b = new double [ [15:19, 1:5]
> ];
> > > > final dist subD = D | [15:19, 1:5];
> > > > b.update(a | subD);
> > > > }
> > > > }
> > > >
> > > > public static void main(String[] args) {
> > > > new test().run();
> > > > }
> > > > }
> > > >
> > > > This code throws the foll error when run with 4 places:-
> > > >
> > > > Exception in thread "pool-0-thread-0: Main Activity"
> > > > BadPlaceException(dist. array, var location=place(id=2) access at
> > > > place=place(id=0))
> > > > at x10.lang.Runtime.hereCheckPlace(Runtime.java:313)
> > > > at x10.array.DoubleArray.get(DoubleArray.java:103)
> > > > at x10.array.DoubleArray.get(DoubleArray.java:100)
> > > > at x10.array.DoubleArray.update(DoubleArray.java:389)
> > > > at test$2.runX10Task(test.java:133)
> > > > at
> > > >
> x10.runtime.InvocationStrategy$DefaultStrategy.invokeX10Task(Invocatio
> > > > nS
> > > > trategy.java:57)
> > > > at x10.runtime.Activity.run(Activity.java:192)
> > > > at
> > > >
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecu
> > > > to
> > > > r.java:665)
> > > > at
> > > >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.
> > > > ja
> > > > va:690)
> > > > at java.lang.Thread.run(Thread.java:799)
> > > >
> > > >
> > > >
> > > > I would like some more clarifications here --
> > > >
> > > > -- If I were to def b as "double [.] b = new double [ [1:5, 1:5]
> ]"
> > > > and leave subD unchanged, then I get the error:-
> > > >
> > > > Exception in thread "pool-0-thread-0: Main Activity"
> > > > java.lang.AssertionError
> > > > at x10.array.DoubleArray.update(DoubleArray.java:382)
> > > > at test$2.runX10Task(test.java:133)
> > > > at
> > > >
> x10.runtime.InvocationStrategy$DefaultStrategy.invokeX10Task(Invocatio
> > > > nS
> > > > trategy.java:57)
> > > > at x10.runtime.Activity.run(Activity.java:192)
> > > > at
> > > >
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecu
> > > > to
> > > > r.java:665)
> > > > at
> > > >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.
> > > > ja
> > > > va:690)
> > > > at java.lang.Thread.run(Thread.java:799)
> > > >
> > > > b here has the same shape and size as before, but a different
> > > > index
> > > set.
> > > > I feel that such a capability is desirable.
> > > >
> > > > -- Correct me if I am wrong in saying that if two arrays have
> > > > identical regions but different distributions, then
> > > > assignment/update/overlay operations should run correctly so long
> > > > as
>
> > > > the locality rule is not violated.
> > > >
> > > > Thanks,
> > > > Aniruddha
> > > > -----------------------------------------------------------
> > > > Aniruddha G. Shet |Email: sh...@or...
> > > > Oak Ridge National Laboratory |Phone: +1 (865) 576 5606
> > > > http://www.csm.ornl.gov/~anish12/ |Fax: +1 (865) 576 5491
> > > > -----------------------------------------------------------
> > > >
> > > > -----Original Message-----
> > > > From: Igor Peshansky
> > > > Sent: Tuesday, April 03, 2007 9:41 PM
> > > > To: Shet, Aniruddha G.
> > > > Cc: x10-users<at>lists.sourceforge.net
> > > > Subject: Re: [X10-users] Array assignment & update/overlay
> > > >
> > > > Shet, Aniruddha G. wrote on 04/03/2007 09:25:03 PM:
> > > >
> > > > > Hi,
> > > > >
> > > > > My understanding is that array assignment and update/overlay
> > > > > operations are not designed to operate on arrays that do not
> having
> > > > > matching distributions, even though they may have matching
> regions?
> > > > >
> > > > > I am seeing that an activity that tries to update a local
> reference
> > > > > type array with a subdistribution of a global array that is
> > > > > final value type fails with BadPlaceException. The local array
> > > > > and the subdistribution have identical regions. The locality
> > > > > rule is not being
> > > >
> > > > > violated here. Is the mismatch of distributions the reason for
> > > > failure?
> > > >
> > > > Hi, Aniruddha,
> > > >
> > > > This behavior sounds like a bug. The way you described it, it
> > > > certainly does not correspond to the X10 language definition.
> > > >
> > > > It would help greatly in debugging this problem if you could
> > > > reduce
> it
> > >
> > > > to a simple (and preferably short) test case. Feel free to post
> > > > it
> to
> > >
> > > > the list or enter it in Bugzilla. It would also help if you could
>
> > > > show the full stack trace of the BadPlaceException you're getting.
> > > > 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/)
|
|
From: Shet, A. G. <sh...@or...> - 2007-04-11 01:14:31
|
Igor,
=20
This probably is the same problem, but just to be sure...
double [.] f =3D new double [ [1:5, 1:5] ];=20
final double value [.] e =3D f;
e should be a value copy of the local reference array f and hence
accessible from any place. But a BadPlaceException is currently thrown
due to the bug. Is my understanding correct?
Thanks,
Aniruddha=20
=20
-----Original Message-----
From: Igor Peshansky [mailto:ig...@us...]=20
Sent: Wednesday, April 04, 2007 1:04 PM
To: Shet, Aniruddha G.
Cc: x10...@li...
Subject: Re: [X10-users] Array assignment & update/overlay
Igor Peshansky wrote on 04/04/2007 12:24:30 PM:
> Aniruddha,
>=20
> No, b *is* a copy, but not a value array.
>=20
> This is actually a bug in the X10 runtime libraries' implementation.
> The restriction ("|") operator does not create a value array, even if=20
> applied to a value array. That's why you get the place checks, etc.
> We'll need to fix this.
>=20
> In the meantime, you can turn off place checks using the=20
> -BAD_PLACE_RUNTIME_CHECK=3Dfalse runtime option. If you don't want to =
> do that, you can make sure a value copy is created by using the=20
> following snippet:
>=20
> final double value [.] a_sub =3D a | subD; final double value [.] b=20
> (point p) { return a_sub[p]; };
Sorry, I meant
final double value[] b =3D new double[a_sub.distribution] (point p) {
return a_sub[p]; };
> (Vijay will, hopefully, correct me if this is wrong).
> Igor
>=20
> "Shet, Aniruddha G." wrote on 04/04/2007 11:09:29 AM:
>=20
> > Igor,
> >=20
> > In the code that I sent, if b were declared as
> >=20
> > final double value [.] b =3D a | subD;
> >=20
> > can I expect a local copy to be created or is b treated only as a=20
> > reference to a section of a? I see that a BadPlaceException is=20
> > thrown when I try to access an element in b, which indicates that no
> > local
copy
> > is created.
> >=20
> > Thanks,
> > Aniruddha
> >=20
> > -----Original Message-----
> > From: Igor Peshansky
> > Sent: Wednesday, April 04, 2007 1:13 AM
> > To: Shet, Aniruddha G.
> > Cc: x10-users<at>lists.sourceforge.net
> > Subject: RE: [X10-users] Array assignment & update/overlay
> >=20
> > Aniruddha,
> >=20
> > Thanks for the detailed report. I've reproduced the first problem
here.
> >=20
> > We'll debug it and get back
> > to you. In the meantime, since you're on an SMP, you can turn off=20
> > BadPlaceExceptions by using the -BAD_PLACE_RUNTIME_CHECK=3Dfalse
option.
> >=20
> > The second problem is a bug, but only because the code to throw the=20
> > appropriate kind of exception never got written, so an assertion is=20
> > tripped instead.
> > Igor
> >=20
> > "Shet, Aniruddha G." wrote on 04/03/2007 11:20:10 PM:
> >=20
> > > Hi Igor,
> > >=20
> > > In the foll piece of code, the activity at place 0 is trying to
update
> >=20
> > > a locally allocated reference array with a block from a=20
> > > distributed value
> > > array:-
> > >=20
> > > public class test {
> > > final region R =3D [1:20, 1:20];
> > > final dist D =3D dist.factory.block(R);
> > > final double value [.] a =3D new double value [D] (point
[i,j])=20
> > > {return i+j;};
> > >=20
> > > public void run() {
> > > async(here) {
> > > double [.] b =3D new double [ [15:19, 1:5]
];
> > > final dist subD =3D D | [15:19, 1:5];
> > > b.update(a | subD);
> > > }
> > > }
> > >=20
> > > public static void main(String[] args) {
> > > new test().run();
> > > }
> > > }
> > >=20
> > > This code throws the foll error when run with 4 places:-
> > >=20
> > > Exception in thread "pool-0-thread-0: Main Activity"
> > > BadPlaceException(dist. array, var location=3Dplace(id=3D2) access =
at
> > > place=3Dplace(id=3D0))
> > > at x10.lang.Runtime.hereCheckPlace(Runtime.java:313)
> > > at x10.array.DoubleArray.get(DoubleArray.java:103)
> > > at x10.array.DoubleArray.get(DoubleArray.java:100)
> > > at x10.array.DoubleArray.update(DoubleArray.java:389)
> > > at test$2.runX10Task(test.java:133)
> > > at
> > >=20
x10.runtime.InvocationStrategy$DefaultStrategy.invokeX10Task(Invocatio
> > > nS
> > > trategy.java:57)
> > > at x10.runtime.Activity.run(Activity.java:192)
> > > at
> > >=20
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecu
> > > to
> > > r.java:665)
> > > at
> > >=20
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.
> > > ja
> > > va:690)
> > > at java.lang.Thread.run(Thread.java:799)
> > >=20
> > >=20
> > >=20
> > > I would like some more clarifications here --
> > >=20
> > > -- If I were to def b as "double [.] b =3D new double [ [1:5, 1:5]
]"=20
> > > and leave subD unchanged, then I get the error:-
> > >=20
> > > Exception in thread "pool-0-thread-0: Main Activity"
> > > java.lang.AssertionError
> > > at x10.array.DoubleArray.update(DoubleArray.java:382)
> > > at test$2.runX10Task(test.java:133)
> > > at
> > >=20
x10.runtime.InvocationStrategy$DefaultStrategy.invokeX10Task(Invocatio
> > > nS
> > > trategy.java:57)
> > > at x10.runtime.Activity.run(Activity.java:192)
> > > at
> > >=20
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecu
> > > to
> > > r.java:665)
> > > at
> > >=20
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.
> > > ja
> > > va:690)
> > > at java.lang.Thread.run(Thread.java:799)
> > >=20
> > > b here has the same shape and size as before, but a different=20
> > > index
> > set.
> > > I feel that such a capability is desirable.
> > >=20
> > > -- Correct me if I am wrong in saying that if two arrays have=20
> > > identical regions but different distributions, then=20
> > > assignment/update/overlay operations should run correctly so long=20
> > > as
> > > the locality rule is not violated.
> > >=20
> > > Thanks,
> > > Aniruddha
> > > -----------------------------------------------------------
> > > Aniruddha G. Shet |Email: sh...@or...
> > > Oak Ridge National Laboratory |Phone: +1 (865) 576 5606
> > > http://www.csm.ornl.gov/~anish12/ |Fax: +1 (865) 576 5491
> > > -----------------------------------------------------------
> > >=20
> > > -----Original Message-----
> > > From: Igor Peshansky
> > > Sent: Tuesday, April 03, 2007 9:41 PM
> > > To: Shet, Aniruddha G.
> > > Cc: x10-users<at>lists.sourceforge.net
> > > Subject: Re: [X10-users] Array assignment & update/overlay
> > >=20
> > > Shet, Aniruddha G. wrote on 04/03/2007 09:25:03 PM:
> > >=20
> > > > Hi,
> > > >=20
> > > > My understanding is that array assignment and update/overlay=20
> > > > operations are not designed to operate on arrays that do not
having=20
> > > > matching distributions, even though they may have matching
regions?
> > > >=20
> > > > I am seeing that an activity that tries to update a local
reference=20
> > > > type array with a subdistribution of a global array that is=20
> > > > final value type fails with BadPlaceException. The local array=20
> > > > and the subdistribution have identical regions. The locality=20
> > > > rule is not being
> > >=20
> > > > violated here. Is the mismatch of distributions the reason for
> > > failure?
> > >=20
> > > Hi, Aniruddha,
> > >=20
> > > This behavior sounds like a bug. The way you described it, it=20
> > > certainly does not correspond to the X10 language definition.
> > >=20
> > > It would help greatly in debugging this problem if you could=20
> > > reduce
it
> >=20
> > > to a simple (and preferably short) test case. Feel free to post=20
> > > it
to
> >=20
> > > the list or enter it in Bugzilla. It would also help if you could
> > > show the full stack trace of the BadPlaceException you're getting.
> > > 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/)
|
|
From: Shet, A. G. <sh...@or...> - 2007-04-10 13:56:12
|
=20
Thanks, a CVS checkout now compiles future.forced().
-Aniruddha
-----Original Message-----
From: Igor Peshansky [mailto:ig...@us...]=20
Sent: Monday, April 09, 2007 11:23 PM
To: Shet, Aniruddha G.
Cc: Nate Nystrom; x10...@li...
Subject: Re: [X10-users] Error in future.forced()
Igor Peshansky wrote on 04/09/2007 04:51:40 PM:
> Nate Nystrom wrote on 04/09/2007 04:20:09 PM:
>=20
> > Shet, Aniruddha G. wrote:
> > > Hi,
> > >=20
> > > I am trying to do a forced() on a future, but the compiler=20
> > > complains saying no valid method call found for forced(). I am=20
> > > able to do a
> > > force() though. Is this a case of missing functionality?
> > >=20
> >=20
> > Aniruddha,
> >=20
> > It seems so. x10/lang/Future.java doesn't have a forced() method.=20
> > I'm
> > not sure if this was intentional or just an oversight.
>=20
> Moreover, the compiler representation of future types doesn't seem to=20
> have a "forced" method in it either. So, if it's an oversight, it is=20
> a rather global one. I'll see if I can make a quick fix.
> Igor
Done. CVS HEAD should now understand future.forced().
Igor
P.S. It was an oversight.
--
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/)
|
|
From: Vijay S. <vi...@sa...> - 2007-04-10 09:51:05
|
Igor Peshansky wrote: >>Moreover, the compiler representation of future types doesn't seem to >>have a "forced" method in it either. So, if it's an oversight, it is >>a rather global one. I'll see if I can make a quick fix. >> Igor >> >> > >Done. CVS HEAD should now understand future.forced(). > Igor >P.S. It was an oversight. > > >not sure if this was intentional or just an oversight. > > Thanks for fixing it Igor. -- X10: Programming parallel machines, productively (http://x10.sf.net) |
|
From: Igor P. <ig...@us...> - 2007-04-10 03:22:50
|
Igor Peshansky wrote on 04/09/2007 04:51:40 PM:
> Nate Nystrom wrote on 04/09/2007 04:20:09 PM:
>
> > Shet, Aniruddha G. wrote:
> > > Hi,
> > >
> > > I am trying to do a forced() on a future, but the compiler complains
> > > saying no valid method call found for forced(). I am able to do a
> > > force() though. Is this a case of missing functionality?
> > >
> >
> > Aniruddha,
> >
> > It seems so. x10/lang/Future.java doesn't have a forced() method. I'm
> > not sure if this was intentional or just an oversight.
>
> Moreover, the compiler representation of future types doesn't seem to
> have a "forced" method in it either. So, if it's an oversight, it is
> a rather global one. I'll see if I can make a quick fix.
> Igor
Done. CVS HEAD should now understand future.forced().
Igor
P.S. It was an oversight.
--
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/)
|
|
From: Igor P. <ig...@us...> - 2007-04-09 20:52:49
|
Nate Nystrom wrote on 04/09/2007 04:20:09 PM:
> Shet, Aniruddha G. wrote:
> > Hi,
> >
> > I am trying to do a forced() on a future, but the compiler complains
> > saying no valid method call found for forced(). I am able to do a
> > force() though. Is this a case of missing functionality?
> >
>
> Aniruddha,
>
> It seems so. x10/lang/Future.java doesn't have a forced() method. I'm
> not sure if this was intentional or just an oversight.
Moreover, the compiler representation of future types doesn't seem to
have a "forced" method in it either. So, if it's an oversight, it is
a rather global one. I'll see if I can make a quick fix.
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/)
|
|
From: Nate N. <na...@na...> - 2007-04-09 20:20:37
|
Shet, Aniruddha G. wrote: > Hi, > > I am trying to do a forced() on a future, but the compiler complains > saying no valid method call found for forced(). I am able to do a > force() though. Is this a case of missing functionality? > Aniruddha, It seems so. x10/lang/Future.java doesn't have a forced() method. I'm not sure if this was intentional or just an oversight. Cheers, Nate |
|
From: Shet, A. G. <sh...@or...> - 2007-04-09 20:01:37
|
Hi, I am trying to do a forced() on a future, but the compiler complains saying no valid method call found for forced(). I am able to do a force() though. Is this a case of missing functionality? Thanks, Aniruddha ----------------------------------------------------------- Aniruddha G. Shet |Email: sh...@or... Oak Ridge National Laboratory |Phone: +1 (865) 576 5606 http://www.csm.ornl.gov/~anish12/ |Fax: +1 (865) 576 5491 -----------------------------------------------------------=20 |
107 messages has been excluded from this view by a project administrator.