| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[NFC][OpenMP] Add several use_device_ptr/addr tests. (#154939) Most tests are either compfailing or runfailing. They should start passing once we start using ATTACH map-type based codegen. (#153683) Even after they start passing, there are a few places where the EXPECTED and actual CHECKs are different, due to two main issues: * use_device_ptr translation on &p[0] is not succeeding in looking-up a previously mapped &p[1] * privatization of byref use_device_addr operands is not happening correctly. The above should be fixed as separate standalone changes. | 11 个月前 | |
[NFC][OpenMP] Add use_device_ptr/addr tests for when the lookup fails. (#169428) As per OpenMP 5.1, the pointers are expected to retain their original values when a lookup fails and there is no device pointer to translate to. | 8 个月前 | |
[NFC][OpenMP] Add several use_device_ptr/addr tests. (#154939) Most tests are either compfailing or runfailing. They should start passing once we start using ATTACH map-type based codegen. (#153683) Even after they start passing, there are a few places where the EXPECTED and actual CHECKs are different, due to two main issues: * use_device_ptr translation on &p[0] is not succeeding in looking-up a previously mapped &p[1] * privatization of byref use_device_addr operands is not happening correctly. The above should be fixed as separate standalone changes. | 11 个月前 | |
[NFC][OpenMP] Add several use_device_ptr/addr tests. (#154939) Most tests are either compfailing or runfailing. They should start passing once we start using ATTACH map-type based codegen. (#153683) Even after they start passing, there are a few places where the EXPECTED and actual CHECKs are different, due to two main issues: * use_device_ptr translation on &p[0] is not succeeding in looking-up a previously mapped &p[1] * privatization of byref use_device_addr operands is not happening correctly. The above should be fixed as separate standalone changes. | 11 个月前 | |
[NFC][OpenMP] Add several use_device_ptr/addr tests. (#154939) Most tests are either compfailing or runfailing. They should start passing once we start using ATTACH map-type based codegen. (#153683) Even after they start passing, there are a few places where the EXPECTED and actual CHECKs are different, due to two main issues: * use_device_ptr translation on &p[0] is not succeeding in looking-up a previously mapped &p[1] * privatization of byref use_device_addr operands is not happening correctly. The above should be fixed as separate standalone changes. | 11 个月前 | |
[NFC][OpenMP] Add small class-member use_device_ptr/addr unit tests. (#164039) Two of the tests are currently asserting, and two are emitting unexpected results. The asserting tests will be fixed using the ATTACH-style codegen from #153683. The other two involve use_device_addr on byrefs, and need more follow-up codegen changes, that have been noted in a FIXME comment. | 9 个月前 | |
[NFC][OpenMP] Add small class-member use_device_ptr/addr unit tests. (#164039) Two of the tests are currently asserting, and two are emitting unexpected results. The asserting tests will be fixed using the ATTACH-style codegen from #153683. The other two involve use_device_addr on byrefs, and need more follow-up codegen changes, that have been noted in a FIXME comment. | 9 个月前 | |
[NFC][OpenMP] Update a test that was failing on aarch64. (#164456) The failure was reported here: https://github.com/llvm/llvm-project/pull/164039#issuecomment-3425429556 The test was checking for the "bad" behavior so as to keep track of it, but there seem to be some issues with the pointer arithmetic specific to aarch64. The update for now is to not check for the "bad" behavior fully. We may need to debug further if similar issues are encountered eventually once the codegen has been fixed. | 9 个月前 | |
[NFC][OpenMP] Add small class-member use_device_ptr/addr unit tests. (#164039) Two of the tests are currently asserting, and two are emitting unexpected results. The asserting tests will be fixed using the ATTACH-style codegen from #153683. The other two involve use_device_addr on byrefs, and need more follow-up codegen changes, that have been noted in a FIXME comment. | 9 个月前 | |
[NFC][OpenMP] Add several use_device_ptr/addr tests. (#154939) Most tests are either compfailing or runfailing. They should start passing once we start using ATTACH map-type based codegen. (#153683) Even after they start passing, there are a few places where the EXPECTED and actual CHECKs are different, due to two main issues: * use_device_ptr translation on &p[0] is not succeeding in looking-up a previously mapped &p[1] * privatization of byref use_device_addr operands is not happening correctly. The above should be fixed as separate standalone changes. | 11 个月前 | |
[NFC][OpenMP] Add use_device_ptr/addr tests for when the lookup fails. (#169428) As per OpenMP 5.1, the pointers are expected to retain their original values when a lookup fails and there is no device pointer to translate to. | 8 个月前 | |
[NFC][OpenMP] Add several use_device_ptr/addr tests. (#154939) Most tests are either compfailing or runfailing. They should start passing once we start using ATTACH map-type based codegen. (#153683) Even after they start passing, there are a few places where the EXPECTED and actual CHECKs are different, due to two main issues: * use_device_ptr translation on &p[0] is not succeeding in looking-up a previously mapped &p[1] * privatization of byref use_device_addr operands is not happening correctly. The above should be fixed as separate standalone changes. | 11 个月前 | |
[NFC][OpenMP] Add several use_device_ptr/addr tests. (#154939) Most tests are either compfailing or runfailing. They should start passing once we start using ATTACH map-type based codegen. (#153683) Even after they start passing, there are a few places where the EXPECTED and actual CHECKs are different, due to two main issues: * use_device_ptr translation on &p[0] is not succeeding in looking-up a previously mapped &p[1] * privatization of byref use_device_addr operands is not happening correctly. The above should be fixed as separate standalone changes. | 11 个月前 | |
[NFC][OpenMP] Add several use_device_ptr/addr tests. (#154939) Most tests are either compfailing or runfailing. They should start passing once we start using ATTACH map-type based codegen. (#153683) Even after they start passing, there are a few places where the EXPECTED and actual CHECKs are different, due to two main issues: * use_device_ptr translation on &p[0] is not succeeding in looking-up a previously mapped &p[1] * privatization of byref use_device_addr operands is not happening correctly. The above should be fixed as separate standalone changes. | 11 个月前 | |
[NFC][OpenMP] Add several use_device_ptr/addr tests. (#154939) Most tests are either compfailing or runfailing. They should start passing once we start using ATTACH map-type based codegen. (#153683) Even after they start passing, there are a few places where the EXPECTED and actual CHECKs are different, due to two main issues: * use_device_ptr translation on &p[0] is not succeeding in looking-up a previously mapped &p[1] * privatization of byref use_device_addr operands is not happening correctly. The above should be fixed as separate standalone changes. | 11 个月前 | |
[NFC][OpenMP] Add several use_device_ptr/addr tests. (#154939) Most tests are either compfailing or runfailing. They should start passing once we start using ATTACH map-type based codegen. (#153683) Even after they start passing, there are a few places where the EXPECTED and actual CHECKs are different, due to two main issues: * use_device_ptr translation on &p[0] is not succeeding in looking-up a previously mapped &p[1] * privatization of byref use_device_addr operands is not happening correctly. The above should be fixed as separate standalone changes. | 11 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 11 个月前 | ||
| 8 个月前 | ||
| 11 个月前 | ||
| 11 个月前 | ||
| 11 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 9 个月前 | ||
| 11 个月前 | ||
| 8 个月前 | ||
| 11 个月前 | ||
| 11 个月前 | ||
| 11 个月前 | ||
| 11 个月前 | ||
| 11 个月前 |