- User Since
- Nov 2 2017, 3:15 PM (168 w, 22 h)
So the lit invocations are in a script of some sort, right? Such a script could perform a feature test to handle this use case: if --no-indirectly-run-check is supported, add it to some lit options variable used by all relevant lit invocations in the script, and do not otherwise. Is that difficult to do?
Can you explain the use case a bit more? I don't find myself moving between old and new versions of lit very often. Perhaps I'm naive, but it seems like it should be easy enough to just not specify --no-indirectly-run-check when using the old version.
Thu, Jan 7
Thanks, I like this change as well.
Nov 10 2020
Here are some examples of using this patch:
Oct 16 2020
Oct 15 2020
Oct 14 2020
Thanks for working on this. Sorry to take so long to review. Before I try to digest the code, I have a few high-level questions.
Oct 13 2020
Thanks for working on this. I'm sorry to start reviewing so late. I haven't digested the implementation fully yet, but I have a few comments to get started.
Aug 20 2020
Aug 19 2020
Does this mean we officially no longer support python 2, which this change breaks?
Aug 11 2020
Aug 6 2020
Aug 5 2020
Don't examine LIBOMPTARGET_DEBUG=1 output in the test. It doesn't work in release builds.
Thanks for the quick reviews!
Add user diagnostic for mapping extension. Use PRId64 where appropriate.
Aug 4 2020
This patch fixes DeviceTy::getTgtPtrBegin to return null when
target_data_update is the caller. I'm wondering if it should do the
same for more callers.
Thanks for the quick review.
Jul 30 2020
Thanks for the review.
Jul 29 2020
Jul 28 2020
Thanks for the review.
Adjust the fixme as requested.
Should this patch be marked NFC?
Adjusted logic for rejecting present as requested. Rebased.
Replaced SeparateBeginEnd parameter with new TargetDataInfo field as requested. Rebased.
Are you following an existing TableGen emitter as a precedent for this kind of thin wrapper design?
Sure. Thanks for the reply.
I've pushed it to master as 9b4826d18b5f.
Jul 27 2020
not expects a non-zero exit not a signal. Adding --crash adjusts the expectation.
Rewrite patch as discussed: instead of generating different runtime calls for the end of an omp target data vs. the beginning of an omp target exit data so that the runtime can determine when to ignore present, change Clang to filter present from the map types at the end of an omp target data.
Other than the nit I just added about comment duplication, this LGTM. Thanks. However, let's a wait a couple of days in case anyone else has an opinion.
This change broke a number of libomptarget tests. Adding --crash to the %libomptarget-run-fail-* definitions in openmp/libomptarget/test/lit.cfg fixes that for me. Any objections?