- User Since
- Sep 24 2015, 4:45 AM (146 w, 5 d)
The change is symetric with what is implemented for cuda.
Thu, Jul 5
Tue, Jul 3
As discussed on the mailing list, the flag should only be dropped on Mac OS. My pragmatic solution would be:
Wed, Jun 20
Mon, Jun 18
The OMPT tool can decide at multiple points to be inactive, here we look at:
The problem, which gets visible in this test case is the use of builtin_frame_address(1), which is documented to be not safe.
Is there a better way to get the canonical frame address of the calling function? Also the address returned by builtin_frame_address seems to be different from the canonical frame address. How can we get the requested address?
Jun 7 2018
taskloop is actually a tasking construct and explicitly no worksharing construct. So, please move the test in the task directory.
Jun 4 2018
May 27 2018
May 10 2018
@dvyukov thanks for the detailed reasoning.
May 7 2018
Result of discussion in Tools WG was that the spec will keep omp_frame_t. I will submit this patch together with D43568
Apr 23 2018
Reasons to keep the name archer (or archer-rt):
- We already have that name, we don't need to come up with a new name :)
- You can easily find related publications under that name, which explain the reasoning behind the library
- The programmer should never see the name, once the tool is integrated into the runtime workflow
Apr 20 2018
Apr 17 2018
I added a testcase. I added it just for Linux, because I have no machine ready to test dl-loading on other OS.
Apr 11 2018
Mar 25 2018
I updated this differential to only export the function.
Feb 28 2018
Feb 23 2018
The idea was that the WAIT in line 11 should ensure that both initial threads arrived.
But actually the runtime is not initialized before line 11. To fix the race, we need to call into the runtime in a way, that makes both threads initial threads before the SIGNAL in line 9.
Feb 22 2018
As far as I know, the current implementation is very close to the specification in TR6.
Here we have a tiny diff between the spec and the implementation. I agree that we should not apply this patch if we will roll back the change in the spec.
Feb 19 2018
Use the captured pattern as pointed out by Olga
Feb 17 2018
The initial issue in this patch is resolved by D43195. So removed the additionally printed address for AARCH64, but still allow the testcases to match any printed address.
I applied clang-format on commit.
Feb 14 2018
This behavior is right (p.417,l.5):
Feb 9 2018
Feb 6 2018
Jan 30 2018
Jan 25 2018
NEEDS must be REQUIRES
NEEDS replaced by REQUIRES
It was defined in https://reviews.llvm.org/D42432
@omalyshe do you have any advice, what is needed to make the omp_control_tool symbol available on Windows?
Jan 23 2018
Assuming we have pthread on all platforms but Windows
Jan 17 2018
Still surprised that this is necessary for void function calls, but with that change the tests also succeed for intel compiler.
We discussed to relax the wording in the OpenMP spec, so that any implementation that provides ompt_mutex_impl_unknown with value 0 is complying. This will include #define, enum or "static const" values.
Jan 11 2018
Ah, I think I understand your plan now.
Jan 10 2018
Ok, I think, I now understood the change.
Jan 9 2018
@omalyshe AFAIK this issue is Case#: 03138964
I would have expected, that
printf("%" PRIu64 ": &lock: %lu\n", ompt_get_thread_data()->value, (unsigned long) &lock);
would also fix the issue.
As I understand the issue, this is not a fault in the test code, but the value provided by parallel-begin is wrong? In that case, I suggest to pass NULL for this architecture/compiler.
Jan 8 2018
Jan 2 2018
Updated the README
Updated the README
Dec 24 2017
Removed 32 bit ARM from the list of supported architectures until it is tested.
Dec 23 2017
I added the requirement for hardware architecture support to LIBOMP_HAVE_OMPT_SUPPORT.
This way one would also get an error when manually turing LIBOMP_OMPT_SUPPORT=on on an unsupported architecture.
Dec 22 2017
Dec 21 2017
I think, the address needs to be reset on return. Please include commit 45a3a39 to this patch.
Dec 13 2017
This change is more a performace optimization. (reset the bit in the bitmap to 0)
The callback was set to NULL before and all callback invocation checks for the NULL-pointer.
Dec 8 2017
Dec 7 2017