-
Notifications
You must be signed in to change notification settings - Fork 3
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
[feat] Support for TornadoVM Tensor types #28
Conversation
…l generated classes
…o be serializable for XML format
…define them. TornadoVM should throw a message to assess this case.
@@ -40,6 +40,7 @@ public class TornadoSettingState implements PersistentStateComponent<TornadoSett | |||
@OptionTag(converter = JdkConverter.class) | |||
public Sdk JdkPath; | |||
public int parameterSize; | |||
public String tensorShapeDimensions; |
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.
Should we represent the dimension directly in an int
value, instead of a String
?
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.
yes, makes sense. I decided to keep it as String because I was getting exceptions due to serialization for the TornadoSettingState.java
class. I will keep a note to refactor it in future PRs.
This PR added support for the TornadoVM Tensor types (Issue #25).
Now, plugin users can define the shape for the tensor types from the plugin configuration panel, similar to the max array size. This configuration is dynamic, and users can update to run next configurations. Then the generated kernels from TornadoVM are generating the acceleration artifacts based on the user-defined shapes.
Some screenshot about the new features:

Note: If the users want to run Tensor unit-tests but they do not define any shape, the default shape set by the plugin is 0, which forwards the misconfiguration to TornadoVM. In this case, TornadoVM should throw an invalid Shape configuration exception.
To test, you can use the
runIDE
Gradle option and open the new IDE. Then set your TornadoVM directory and the plugin configurations, and try the TestTensorTypes tests.