MAP specific issues
This section includes details about known issues with Linaro MAP.
- MPI wrapper libraries
- Thread support limitations
- No thread activity while blocking on an MPI call
- I am not getting enough samples
- I just see main (external code) and nothing else
- Linaro MAP reports time spent in a function definition
- Linaro MAP does not correctly identify vectorized instructions
- Linking with the static Linaro Forge sampler library fails with FDE overlap errors
- Linking with the static Linaro Forge sampler library fails with an undefined references to “__real_dlopen”
- Linaro MAP adds unexpected overhead to my program
- Linaro MAP takes an extremely long time to gather and analyze my OpenBLAS-linked application
- Linaro MAP over-reports MPI, Input/Output, accelerator or synchronization time
- Linaro MAP collects very deep stack traces with boost::coroutine