Hi Mikael, On 12/10/19 1:21 PM, Simberg Mikael wrote: > You'll also want to export APEX_OTF2=1 to actually generate the OTF2 > files. It should end up in OTF2_archive/APEX.otf2 in the directory that > you run the executable. Let us know if that doesn't work. Also keep in > mind that to get meaningful names for your tasks you'll want to annotate > them with e.g. hpx::util::annotated_function (wrap your functions at > hpx::async/apply callsites).
Indeed, I normally also use APEX_OTF2=1. But with HPX 1.3.0 I didn't have to annotate my tasks explicitly to generate a (limited) trace. I have the impression something has changed in that area. But maybe I am wrong. Thank you for you suggestion, I will look into annotating my tasks explicitly. BTW, I am very happy with the streamlined build process of 1.4.0. It seems to be easier to integrate HPX with my own project than it was before. Kor _______________________________________________ hpx-users mailing list [email protected] https://mail.cct.lsu.edu/mailman/listinfo/hpx-users
