This patch changes the -fopenmp-target-new-runtime option which controls if
the new or old device runtime is used to be true by default. Disabling this to
use the old runtime now requires using -fno-openmp-target-new-runtime.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
D114891 enables this for the amdgpu tests.
This patch will leave the nvptx tests running on the new runtime twice, and not on the old runtime at all, I think. lit.cfg should probably use old + new explicitly, instead of default + new
Oh that's definitely right.
I'm thinking we should also disable testing for the old device runtime.
perhaps we can try this patch as is, and if it passes buildbot, let the new DeviceRTL be the default upstream for all targets.
if it fails the AMDGPU buildbot, then perhaps apply the above suggested change of leaving old runtime default for now for AMD.
or consider some other soultion.
in other words, how about we land it, and be ready to revert if bot goes red?
works for me, i think Greg is ok with it too, we chatted internally an hour or so ago
Should I just land it now and sleep or wait until tomorrow? Whichever causes the least downtime for you.
like Jon said, you also have to disable the test for the "new" one because the default one now is the new one.
This will definitely break amdgpu bot without D114865 landed first.
However that patch is currently blocked by Matt, so we may want to land this and disable the amdgpu buildbot until the backend is fixed.
edit: a cleanup to do with or after this is to remove all the lines with -newRTL in them from the libomptarget test files and drop the -newRTL test target from plugins/cuda. Depending on order of patches we might want to remove it from plugins/amdgpu as well, or it might already be missing.
The consensus internally seems to be to land this and see what happens on the amdgpu buildbot. Go for it
Fails on CI pretty much like it fails locally
https://lab.llvm.org/buildbot/#/builders/193/builds/2569
thx for trying it out, please revert so we can look into it more on the AMDGPU target
Add a check for amdgcn something like this.