charm AT lists.siebelschool.illinois.edu
Subject: Charm++ parallel programming system
List archive
- From: Evan Ramos <evan AT hpccharm.com>
- To: Jozsef Bakosi <jbakosi AT lanl.gov>
- Cc: "charm AT lists.cs.illinois.edu" <charm AT lists.cs.illinois.edu>
- Subject: Re: [charm] sync & threaded attributes
- Date: Tue, 12 Feb 2019 15:44:02 -0600
- Authentication-results: illinois.edu; spf=none smtp.mailfrom=evan AT hpccharm.com; dkim=pass header.d=hpccharm-com.20150623.gappssmtp.com header.s=20150623; dmarc=none
Hi Jozsef,
Unfortunately, constructors may not use the threaded attribute. The functionality that implements threaded methods requires that a chare's constructor has already run. I wrote a patch for charmxi to throw an error in this situation: https://charm.cs.illinois.edu/gerrit/c/charm/+/4948
-Evan
On Wed, Jan 30, 2019 at 9:15 AM Jozsef Bakosi <jbakosi AT lanl.gov> wrote:
Thanks, Sam. Follow-up:
Can chare array constructors be threaded? I get a compile error if I
try:
error: use of undeclared identifier 'impl_obj_void'
new (impl_obj_void) DiagCG(std::move(disc.t), std::move(fd.t));
Jozsef
On 01.30.2019 14:56, White, Samuel T wrote:
> Yes, if you make a call to a [sync] entry method from a non-[threaded] entry method, the caller will not block as intended, so if your program relies on the blocking behavior for correctness then it will be erroneous.
>
> -Sam
>
> ________________________________________
> From: Jozsef Bakosi [jbakosi AT lanl.gov]
> Sent: Wednesday, January 30, 2019 7:27 AM
> To: charm AT lists.cs.illinois.edu
> Subject: [charm] sync & threaded attributes
>
> Hi folks,
>
> Do I understand it correctly that sync entry methods should always only
> be called from threaded entry methods? Do I invite random errors when
> this is not so?
>
> Thanks,
> Jozsef
- Re: [charm] sync & threaded attributes, Evan Ramos, 02/12/2019
- Re: [charm] sync & threaded attributes, Jozsef Bakosi, 02/12/2019
Archive powered by MHonArc 2.6.19.