By: Klimax (danklima.delete@this.gmail.com), July 14, 2013 9:59 pm
Room: Moderated Discussions
Steve (sberens.Throwaway.delete@this.gmail.com) on July 14, 2013 8:16 pm wrote:
> Wilco (Wilco.Dijkstra.delete@this.ntlworld.com) on July 12, 2013 11:59 am wrote:
> > AnTuTu apparently fixed their benchmark: http://www.eetimes.com/author.asp?section_id=36&doc_id=1318894&
> >
> > The RAM score halves on Atom but ARM scores remain the same. Apparently they
> > still use ICC, but hopefully AnTuTu will review this given this debacle.
> >
> > Wilco
> >
>
> Funny how it is only the ICC compiler from Intel that dropped code that tested the RAM.
>
> It was an Intel problem all along not AnTuTu.
>
> Intel: opps got caught cheating again so now direct flack to AnTuTu
Since when removal of code, whose results are unused is cheating? (All compilers do it, just degree is different depending how advanced detection is)
So far nobody have proven it was cheating and not valid optimization, assertions notwithstanding.
So far only bug in benchmark.
> Wilco (Wilco.Dijkstra.delete@this.ntlworld.com) on July 12, 2013 11:59 am wrote:
> > AnTuTu apparently fixed their benchmark: http://www.eetimes.com/author.asp?section_id=36&doc_id=1318894&
> >
> > The RAM score halves on Atom but ARM scores remain the same. Apparently they
> > still use ICC, but hopefully AnTuTu will review this given this debacle.
> >
> > Wilco
> >
>
> Funny how it is only the ICC compiler from Intel that dropped code that tested the RAM.
>
> It was an Intel problem all along not AnTuTu.
>
> Intel: opps got caught cheating again so now direct flack to AnTuTu
Since when removal of code, whose results are unused is cheating? (All compilers do it, just degree is different depending how advanced detection is)
So far nobody have proven it was cheating and not valid optimization, assertions notwithstanding.
So far only bug in benchmark.