[OMPT] Print two more addresses in print_fuzzy_address_block()
The two more outputs are needed to match the return addresses when using the Intel Compiler, as it generates more instructions between the fuzzy-printing of the address and the runtime call. Patch by Simon Convent Reviewed By: protze.joachim, hbae Differential Revision: https://reviews.llvm.org/D49373 git-svn-id: https://llvm.org/svn/llvm-project/openmp/trunk@338144 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
@@ -183,11 +183,14 @@ ompt_label_##id:
|
||||
// to include or discard the new number of nibbles!
|
||||
#define FUZZY_ADDRESS_DISCARD_NIBBLES 2
|
||||
#define FUZZY_ADDRESS_DISCARD_BYTES (1 << ((FUZZY_ADDRESS_DISCARD_NIBBLES) * 4))
|
||||
#define print_fuzzy_address_blocks(addr) \
|
||||
printf("%" PRIu64 ": fuzzy_address=0x%" PRIx64 " or 0x%" PRIx64 " (%p)\n", \
|
||||
ompt_get_thread_data()->value, \
|
||||
((uint64_t)addr) / FUZZY_ADDRESS_DISCARD_BYTES - 1, \
|
||||
((uint64_t)addr) / FUZZY_ADDRESS_DISCARD_BYTES, addr)
|
||||
#define print_fuzzy_address_blocks(addr) \
|
||||
printf("%" PRIu64 ": fuzzy_address=0x%" PRIx64 " or 0x%" PRIx64 \
|
||||
" or 0x%" PRIx64 " or 0x%" PRIx64 " (%p)\n", \
|
||||
ompt_get_thread_data()->value, \
|
||||
((uint64_t)addr) / FUZZY_ADDRESS_DISCARD_BYTES - 1, \
|
||||
((uint64_t)addr) / FUZZY_ADDRESS_DISCARD_BYTES, \
|
||||
((uint64_t)addr) / FUZZY_ADDRESS_DISCARD_BYTES + 1, \
|
||||
((uint64_t)addr) / FUZZY_ADDRESS_DISCARD_BYTES + 2, addr)
|
||||
|
||||
static void
|
||||
on_ompt_callback_mutex_acquire(
|
||||
|
||||
Reference in New Issue
Block a user