Hi Kor,
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). Mikael ________________________________ From: hpx-users-boun...@stellar.cct.lsu.edu <hpx-users-boun...@stellar.cct.lsu.edu> on behalf of Jong, K. de (Kor) <k.dejo...@uu.nl> Sent: Tuesday, December 10, 2019 11:23:12 AM To: hpx-users@stellar.cct.lsu.edu Subject: Re: [hpx-users] HPX 1.4.0 release candidate 2 On 12/6/19 5:28 PM, Simberg Mikael wrote: > APEX integration has also > been updated and can be enabled with -DHPX_WITH_APEX=ON and > -DHPX_WITH_APEX_TAG=develop. The latter option will be unnecessary for > the final release. I am interested in generating traces in OTF2 format to load into Vampir. For that I am testing 1.4.0-rc2 with support for APEX and OTF2. Building HPX with support for APEX works fine, great! I have also built OTF2 (version 2.2) and passed in the APEX_WITH_OTF2 flag. I noticed that otf2_listener.cpp.o was being built. I have no reason to believe the resulting HPX does not have support for APEX+OTF2. Also: ./fibonacci --hpx:info | grep APEX HPX_WITH_APEX=ON HPX_WITH_APEX_NO_UPDATE=OFF When I try this, no trace is printed, though: APEX_SCREEN_OUTPUT=1 ./fibonacci When I try this, a trace is printed: APEX_SCREEN_OUTPUT=1 ./apex_fibonacci I expected the first command to also print a trace. Is automatic instrumentation of HPX with APEX maybe not working yet in 1.4.0-rc2? Kor _______________________________________________ hpx-users mailing list hpx-users@stellar.cct.lsu.edu https://mail.cct.lsu.edu/mailman/listinfo/hpx-users
_______________________________________________ hpx-users mailing list hpx-users@stellar.cct.lsu.edu https://mail.cct.lsu.edu/mailman/listinfo/hpx-users
