> The amounts of data we're sorting would only trigger the memory problem on a system
> with less than 8 MB or so.
>
> So, I know it's irresistable, but can we stop playing "I gotcha'ed the only remaining
> dev stupid enough to read MW!" and get back to providing actual factual evidence that
> the qsort is the reason for the alleged cross-OS difference?
I was just providing evidence to the original poster's claim that qsort *can* produce different results because it's inherently not a stable sort algorithm.
In practice, due to the way that MAME uses qsort, I don't know if it actually *does* produce different output. Re-reading the original post, I'm not sure that he's even claiming that it actually *is* producing different output.
I guess we need for him to come back and provide some proof.
GroovyMAME support forum on BYOAC
|
Previous 
Index 
Next 
Flat 
Re: bug: chdman output depends on system qsort() implementation
Reply
Re: bug: chdman output depends on system qsort() implementation
