|
|
Re: I may get flamed for this, but this IS the loony bin so... (Retroarch Bounty)
10/08/18 10:15 PM
|
|
|
> > From what I just read they think the CPU emu is a drop in.
>
> LOL
>
> > 1600 buck *is* a lot of money.
>
> Hahaha....
>
> > But that is basically 3-6 days of 8 hour days of work.
>
> Bwahahahaha....
>
> If there's one thing I've always wished I had time to do, it was an A64 backend for
> MAME's DRC. A64 is a slick architecture and super nice for dynamic codegen. It would
> be a fun project.
>
> But let's be honest, $1600 is chump change for any kind of financial incentive. It
> would take me (who wrote MAME's DRC system in the first place, including both x86 and
> x64 backends, AND who has written two A64 backends for commercial work) waaay longer
> than 3-6 days to complete and debug. 3-6 weeks, maybe, not even factoring in the long
> tail of bugs.
1600 is a lot of money to a lot of people. I sure would not turn it down... But your and my point is it is nowhere *near* enough to accomplish it. I was also being *very* 'nice' with the per hour rate to make the 'customers' money last longer. However, for someone who knows how to do a task like this, I am 100% sure I am off by a factor of at least 2x-3x on cost. The money would probably run out in less than 2 days. I was back of the envelop specing 2-3 months to get it right. Probably less if you know what you are doing (like you do).
Even then I would probably start with putting the thing in a hotspot analyzer and see if there is any low hanging fruit for some easy gains. Then see if there is any data arrangement that could help with cache hits. Then look to seeing if you can eliminate any unneeded branching. You know, typical optimization stuff. Only then would I reach for a full out alg restructure such as dyn-rec.
But yeah probably would be fun to do.
Edited by lharms (10/08/18 10:27 PM)
|
|
Index 
Flat 
Re: I may get flamed for this, but this IS the loony bin so... (Retroarch Bounty)
Reply
