-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Melt windows fix #137
Melt windows fix #137
Conversation
Discussion:
|
e9db293
to
36cad91
Compare
36cad91
to
476d626
Compare
476d626
to
7856a33
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This all looks reasonable and in agreement with what we discussed in the meeting, thanks!
The remaining thing to do is to document this, as mentioned in the checklist for the PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Discussed in meeting, small comments on looking at the code, looks like just docs left.
thanks. Just done in d64358c |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding the docs, @TomMelt. Just one minor request then good to go!
594e938
to
4d66327
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple of suggestions on phrasing, but not blocking.
Should be OK with this being added once #168 is approved and merged
8afc2d0
to
b233133
Compare
Integer size for FTorch can now be controlled using parameter `ftorch_int`. Currently, the default is set to `int32` but this could be changed if required. This fixes an issue on windows with the latest version of ifx/ifort which builds with a different integer type leading to the following error: ``` error #6284: There is no matching specific function for this generic function reference. [TORCH_TENSOR_FROM_ARRAY] in_tensors(1) = torch_tensor_from_array(in_data, tensor_layout, torch_kCPU) -------------------^ ```
b233133
to
d3d8865
Compare
fixes [#183](#183) There is an issue when building on mac (arm_64) or windows. The version of `libtorch` exposes a torch tensors shape (`t->sizes().data()`) as a `const long long int*` instead of just a `const long int*` like on linux and mac (x86). This commit adds preprocessor macro to switch between implementations automatically detecting the correct version at CMake build stage.
Co-authored-by: Jack Atkinson <[email protected]>
d3d8865
to
e82816e
Compare
the only test that fails is in the static analysis when running |
fixes #124
Windows was not previously exporting the library symbols and creating the
dll
correctly.This is now resolved by the following addition to
CMakeLists.txt
FTorch/src/CMakeLists.txt
Lines 6 to 9 in 7856a33
Furthemore, there was an issue that the library was built with a different integer size than that used when compiling example programs, despite no difference in compiler option. We have now forced the library to use
int32
explicitly. This can be modified by the user, modifying the following lineFTorch/src/ftorch.fypp
Line 34 in 7856a33
Tasks:
int64
/int32
issue properly (we have decided to build int32 by default. Can be overridden by user.