Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> I have also realized that there is a lot out there in the world besides video games, and getting all in a huff about it isn’t worth my time or energy.

I'd really love to try AMD as a daily driver. For me CUDA is the showstopper. There's really nothing comparable in the AMD camp.



ROCM is, to some degree and in some areas, a pretty decent alternative. Developing with it is often times a horrible experience, but once something works, it works fine.


> but once something works, it works fine.

Is there "forwards compatibility" to the same code working on the next cards yet like PTX provided Nvidia?

Last time (4 years ago?) I looked into ROCM, you seemed to have to compile for each revision of each architecture.


I'm decently sure you have to compile separately for each architecture, and if you elect to compile for multiple architectures up front, you'll have excruciating compile times. You'd think that would be annoying, but it ends up not really mattering since AMD completely switches out the toolchain about every graphics generation anyway. That's not a good reason to not have forwards compatibility, but it is a reason.

The reason I'm not completely sure is because I'm just doing this as a hobby, and I only have a single card, and that single card has never seen a revision. I think that's generally the best way to be happy with ROCM. Accept that it's at the abstraction level of embedded programming, any change in the hardware will have to result in a change in the software.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: