You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks to @itzmeanjan contributions, we're now supporting more targets, which is very exciting. This also adds some complexity (maintenance, testing, ...), so I'm wondering at which point we should start using a "real library" for getting cycle count.
There's https://cpucycles.cr.yp.to/ which looks like good piece of work; however, I'm not sold on the idea of requiring installation of this library prior to using dudect. It would be great to have dudect standalone. Maybe we can take some ideas from there though.
Opening this issue for discussion. I'd say it's a low-priority issue to work on right now.
The text was updated successfully, but these errors were encountered:
It's possible to add features based on third-party libraries while keeping the core functionality self-contained, as long as such dependencies are optional.
We could place those features inside blocks guarded by conditional compilation directives inside dudect.h, or in a separate header file.
Thanks to @itzmeanjan contributions, we're now supporting more targets, which is very exciting. This also adds some complexity (maintenance, testing, ...), so I'm wondering at which point we should start using a "real library" for getting cycle count.
There's https://cpucycles.cr.yp.to/ which looks like good piece of work; however, I'm not sold on the idea of requiring installation of this library prior to using dudect. It would be great to have dudect standalone. Maybe we can take some ideas from there though.
Opening this issue for discussion. I'd say it's a low-priority issue to work on right now.
The text was updated successfully, but these errors were encountered: