文件最后提交记录最后更新时间
[OpenMP][OMPT] Indicate loop schedule for worksharing-loop events (#97429) Use more specific values from ompt_work_t to allow the tool identify the schedule of a worksharing-loop. With this patch, the runtime will report the schedule chosen by the runtime rather than necessarily the schedule literally requested by the clause. E.g., for guided + just one iteration per thread, the runtime would choose and report static. Fixes issue #639041 年前
[OpenMP][OMPT] Indicate loop schedule for worksharing-loop events (#97429) Use more specific values from ompt_work_t to allow the tool identify the schedule of a worksharing-loop. With this patch, the runtime will report the schedule chosen by the runtime rather than necessarily the schedule literally requested by the clause. E.g., for guided + just one iteration per thread, the runtime would choose and report static. Fixes issue #639041 年前
[OpenMP][OMPT] Indicate loop schedule for worksharing-loop events (#97429) Use more specific values from ompt_work_t to allow the tool identify the schedule of a worksharing-loop. With this patch, the runtime will report the schedule chosen by the runtime rather than necessarily the schedule literally requested by the clause. E.g., for guided + just one iteration per thread, the runtime would choose and report static. Fixes issue #639041 年前
[OpenMP][OMPT] Indicate loop schedule for worksharing-loop events (#97429) Use more specific values from ompt_work_t to allow the tool identify the schedule of a worksharing-loop. With this patch, the runtime will report the schedule chosen by the runtime rather than necessarily the schedule literally requested by the clause. E.g., for guided + just one iteration per thread, the runtime would choose and report static. Fixes issue #639041 年前
[OpenMP][OMPT] Indicate loop schedule for worksharing-loop events (#97429) Use more specific values from ompt_work_t to allow the tool identify the schedule of a worksharing-loop. With this patch, the runtime will report the schedule chosen by the runtime rather than necessarily the schedule literally requested by the clause. E.g., for guided + just one iteration per thread, the runtime would choose and report static. Fixes issue #639041 年前
[OpenMP][OMPT] Indicate loop schedule for worksharing-loop events (#97429) Use more specific values from ompt_work_t to allow the tool identify the schedule of a worksharing-loop. With this patch, the runtime will report the schedule chosen by the runtime rather than necessarily the schedule literally requested by the clause. E.g., for guided + just one iteration per thread, the runtime would choose and report static. Fixes issue #639041 年前
[OMPT] Fix parallel_id and task_id in loop_end with schedule static For serialized parallel regions, wrong ids were reported. Now the same code is used as in kmp_dispatch.cpp which emits the correct ids. Differential Revision: http://reviews.llvm.org/D18348 llvm-svn: 26426610 年前
[OMPT] Fix parallel_id and task_id in loop_end with schedule static For serialized parallel regions, wrong ids were reported. Now the same code is used as in kmp_dispatch.cpp which emits the correct ids. Differential Revision: http://reviews.llvm.org/D18348 llvm-svn: 26426610 年前
[OMPT] Add annotations to testcases that are expected to fail when using certain compilers Reasons for expected failures are mainly bugs when using lables in OpenMP regions or missing support of some OpenMP features. For some worksharing clauses, support to distinguish the kind of workshare was added just recently. If an issue was fixed in a minor release version of a compiler, we flag the test as unsupported for this compiler version to avoid false positives. Same for fixes that where backported to older compiler versions. Differential Revision: https://reviews.llvm.org/D40384 llvm-svn: 3212628 年前
[OMPT] Fix parallel_id and task_id in loop_end with schedule static For serialized parallel regions, wrong ids were reported. Now the same code is used as in kmp_dispatch.cpp which emits the correct ids. Differential Revision: http://reviews.llvm.org/D18348 llvm-svn: 26426610 年前
[OpenMP][OMPT] Indicate loop schedule for worksharing-loop events (#97429) Use more specific values from ompt_work_t to allow the tool identify the schedule of a worksharing-loop. With this patch, the runtime will report the schedule chosen by the runtime rather than necessarily the schedule literally requested by the clause. E.g., for guided + just one iteration per thread, the runtime would choose and report static. Fixes issue #639041 年前
[OMPT] Add annotations to testcases that are expected to fail when using certain compilers Reasons for expected failures are mainly bugs when using lables in OpenMP regions or missing support of some OpenMP features. For some worksharing clauses, support to distinguish the kind of workshare was added just recently. If an issue was fixed in a minor release version of a compiler, we flag the test as unsupported for this compiler version to avoid false positives. Same for fixes that where backported to older compiler versions. Differential Revision: https://reviews.llvm.org/D40384 llvm-svn: 3212628 年前
[OpenMP][OMPT] Indicate loop schedule for worksharing-loop events (#97429) Use more specific values from ompt_work_t to allow the tool identify the schedule of a worksharing-loop. With this patch, the runtime will report the schedule chosen by the runtime rather than necessarily the schedule literally requested by the clause. E.g., for guided + just one iteration per thread, the runtime would choose and report static. Fixes issue #639041 年前
[OpenMP][OMPT] Indicate loop schedule for worksharing-loop events (#97429) Use more specific values from ompt_work_t to allow the tool identify the schedule of a worksharing-loop. With this patch, the runtime will report the schedule chosen by the runtime rather than necessarily the schedule literally requested by the clause. E.g., for guided + just one iteration per thread, the runtime would choose and report static. Fixes issue #639041 年前
[OpenMP][OMPT] Indicate loop schedule for worksharing-loop events (#97429) Use more specific values from ompt_work_t to allow the tool identify the schedule of a worksharing-loop. With this patch, the runtime will report the schedule chosen by the runtime rather than necessarily the schedule literally requested by the clause. E.g., for guided + just one iteration per thread, the runtime would choose and report static. Fixes issue #639041 年前
[OpenMP][OMPT] Indicate loop schedule for worksharing-loop events (#97429) Use more specific values from ompt_work_t to allow the tool identify the schedule of a worksharing-loop. With this patch, the runtime will report the schedule chosen by the runtime rather than necessarily the schedule literally requested by the clause. E.g., for guided + just one iteration per thread, the runtime would choose and report static. Fixes issue #639041 年前
[OMPT] Fix parallel_id and task_id in loop_end with schedule static For serialized parallel regions, wrong ids were reported. Now the same code is used as in kmp_dispatch.cpp which emits the correct ids. Differential Revision: http://reviews.llvm.org/D18348 llvm-svn: 26426610 年前
[OMPT] Fix parallel_id and task_id in loop_end with schedule static For serialized parallel regions, wrong ids were reported. Now the same code is used as in kmp_dispatch.cpp which emits the correct ids. Differential Revision: http://reviews.llvm.org/D18348 llvm-svn: 26426610 年前
Update implementation of OMPT to the specification OpenMP 5.0 Preview 1 (TR4). The code is tested to work with latest clang, GNU and Intel compiler. The implementation is optimized for low overhead when no tool is attached shifting the cost to execution with tool attached. This patch does not implement OMPT for libomptarget. Patch by Simon Convent and Joachim Protze Differential Revision: https://reviews.llvm.org/D38185 llvm-svn: 3170858 年前