Skip to content
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

use libcpucycles? #38

Open
oreparaz opened this issue Jan 30, 2024 · 1 comment
Open

use libcpucycles? #38

oreparaz opened this issue Jan 30, 2024 · 1 comment

Comments

@oreparaz
Copy link
Owner

oreparaz commented Jan 30, 2024

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.

@ShamrockLee
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants