This patch adds a move_alloc implementation to the flang runtime.
Most of the checks required by the standard for move_alloc are
done by semenatic analysis; these checks are not replicated here.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
flang/runtime/allocatable.cpp | ||
---|---|---|
48 | RUNTIME_CHECK() is the macro to use here. This check will not catch a discrepancy in derived types. You should confirm that both d'tors are allocatables. | |
50 | Deallocate won't run finalizers (7.5.6.3 p2). You want int stat{to.Destroy()}; return ReturnError(...); } | |
58 | swap() doesn't know how large the descriptors are. You want memcpy(to, from, from.SizeInBytes()) followed by from.raw.base_address = nullptr. | |
69 | In the case of MOVE_ALLOC(x,x), it must be the case that x is in the deallocated state and nothing happens. Is that true with this implementation? If not, you'll need to check for this condition. | |
flang/unittests/Runtime/Allocatable.cpp | ||
55 | Braced initialization, please. | |
75 | Other tests: ensure that FINAL procedures are called; ensure that MOVE_ALLOC(x,x) is allowed only with x in a deallocated state. |
Use Destroy over Deallocate
Don't swap the descriptors
Add handling for MOVE_ALLOC(x,x)
Thanks for the review!
flang/runtime/allocatable.cpp | ||
---|---|---|
48 | I don't think it's possible in the general case to detect discrepancies in derived types here, because the requirement for derived types is that they're compatible, not that they're identical. This check should be done at semantic analysis, I only added the assert here as an extra precaution. | |
58 | std::swap() just calls the assignment operator, which I performs the memcpy you are describing internally. I agree that it isn't actually necessary to do the swap though, so I've changed to just use the assignment operator once and set from to nullptr as you suggested. | |
flang/unittests/Runtime/Allocatable.cpp | ||
75 | I had trouble writing the test for FINAL procedures as it would require creating a derived type and associating a finalizer with it from the C++ side here; do you know if there are any other tests that do this that I can use as a reference? |
flang/runtime/allocatable.cpp | ||
---|---|---|
53 | The case where neither is allocated should already fall through to the return at the end, and do nothing. I believe this is what is required in the standard. |
flang/runtime/allocatable.cpp | ||
---|---|---|
59 | if (stat != StatOk) should be used for readability so that one doesn't need to know that Fortran's successful status value is zero. |
Hello David,
I am getting the following error with -DBUILD_SHARED_LIBS=OFF build and make check-flang:
ld.lld: error: undefined symbol: mlir::SuccessorRange::SuccessorRange(mlir::Operation*) >>> referenced by Operation.h:549 (/llvm-project/llvm/../mlir/include/mlir/IR/Operation.h:549) >>> CMakeFiles/FlangRuntimeTests.dir/Allocatable.cpp.o:(mlir::Operation::getSuccessors())
flang/runtime/allocatable.cpp | ||
---|---|---|
47 | This is not the case when one of the descriptor is polymorphic or unlimited polymorphic. |
flang/runtime/allocatable.cpp | ||
---|---|---|
47 | An example can be found here: https://github.com/llvm/llvm-project/issues/60250 |
handled*