Yeah, we'd want to call a C function that did a certain amount of work, with the only ints being a simple vint that incremented a ticks var. Something like that. How about those old BYTE benchmarks?Stef wrote:From my last checks out was getting worse, but maybe absolute latter version are better, I've to admit I didn't checked from sometime now.
Of course for better test you need to benchmark 100% C code, I say that because sgdk uses assembly sometime.
Compatibility with C++
Moderator: Stef
-
Chilly Willy
- Very interested
- Posts: 2996
- Joined: Fri Aug 17, 2007 9:33 pm
-
Stef
- Very interested
- Posts: 3131
- Joined: Thu Nov 30, 2006 9:46 pm
- Location: France - Sevres
- Contact:
Yeah that could be a good solution.
It's better to have different kind of benchmark (memory copy / memory compare, basic operation, line drawing...).
Maybe i could integrate a benchmark sample in SGDK (based on what we can find around) so who want to test the compiler and flags optimization impact could use it =)
It's better to have different kind of benchmark (memory copy / memory compare, basic operation, line drawing...).
Maybe i could integrate a benchmark sample in SGDK (based on what we can find around) so who want to test the compiler and flags optimization impact could use it =)
-
Chilly Willy
- Very interested
- Posts: 2996
- Joined: Fri Aug 17, 2007 9:33 pm