News for hackers. Stuff that matters.

A comment on AMA: Explaining my 750 line compiler+runtime designed to GPU self-host APL. Parent comment

Re:AMA: Explaining my 750 line compiler+runtime designed to ... by arcfide on Monday March 06, 2017 @12:14AM (#13800837)
If I were to expand that idea a bit more and remark on the biggest class of bug that causes segfaults for me in ArrayFire, it would be the requirement for explicit data type casting using as() to avoid problems. I wouldn't want this to go away at the cost of performance, but....
[ Parent | on HN ]
Re:AMA: Explaining my 750 line compiler+runtime designed to ... by pavanky on Monday March 06, 2017 @12:25AM (#13800864)
Hmm this is the down side of using a dynamic typed array class. While the functions to handle the type checking of the host pointers can be done in C++, it would not be so easy to implement it in the C layer.

And since it looks like you are using the C++ api anyway, can you open an issue on github so this will be looked at?

[ Parent | on HN ]
Re:AMA: Explaining my 750 line compiler+runtime designed to ... by arcfide on Monday March 06, 2017 @12:51PM (#13804466)
I will see if I can remember to do this. Thanks for the contributions!
[ Parent | on HN ]