This bugzilla service is closed. All entries have been migrated to https://gitlab.com/libeigen/eigen
Bug 1552 - Enhancement : Adding support for ROCm/HIP in Eigen (analogous to the existing CUDA support)
Summary: Enhancement : Adding support for ROCm/HIP in Eigen (analogous to the existing...
Status: NEW
Alias: None
Product: Eigen
Classification: Unclassified
Component: Core - general (show other bugs)
Version: 3.4 (development)
Hardware: Other Linux
: Normal Feature Request
Assignee: Nobody
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-01 16:10 UTC by Deven Desai
Modified: 2019-12-04 17:40 UTC (History)
3 users (show)



Attachments

Description Deven Desai 2018-06-01 16:10:42 UTC
Hi Eigen-Developersm

I am a software development engineer at AMD, and we are currently in the process of implementing support for the ROCm/HIP in the Eigen codebase. This support will be analogous to what is currently present for CUDA.

At this point we are ready to submit an initial PR so that you can have a chance to review the changes we have made so far. I do not know what is the process that we need to follow here, and hence filing this bug. 

Please let me know if we can proceed with the PR or if there is something more that needs to be done before that.

Thanks

deven
Comment 1 Christoph Hertzberg 2018-06-05 16:46:38 UTC
Making a PR sounds like a good idea, if you have some working/reviewable changes. If you are more at a proof-of-concept phase, I'd suggest just publishing a URL to  a fork.
Both preferably also on the public mailing list, because barely anyone is following the bug-tracker.

How much changes is it?
If it mostly requires re-defining EIGEN_DEVICE, I see no reason to block this.
Comment 2 Nobody 2019-12-04 17:40:56 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to gitlab.com's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.com/libeigen/eigen/issues/1552.

Note You need to log in before you can comment on or make changes to this bug.