News for hackers. Stuff that matters.

A comment on Intel Confronts Potential ‘PR Nightmare’ With Reported Chip Flaw. Parent comment

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by bunderbunder on Wednesday January 03, 2018 @12:17PM (#16062809)
In other words, don't worry - pretty much all the key performance bottlenecks most of us deal with at work will be getting tighter, but at least our video games will still run OK.
[ Parent | on HN ]
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by user5994461 on Thursday January 04, 2018 @12:40AM (#16068310)
Well, sounds like that time when there is no water left but there are still beers in the fridge.

At least we can play our sorrows away.

[ Parent | on HN ]
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by josefx on Wednesday January 03, 2018 @01:13PM (#16063426)
Right now I am just hoping that it wont add significant overhead to OpenGL. My application already has a bottleneck on changing OpenGL states and issuing render commands and I have no idea how much of that time is spend making syscalls.
[ Parent | on HN ]
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by elFarto on Wednesday January 03, 2018 @01:34PM (#16063638)
OpenGL implementations shouldn't be effected by syscall overhead. Historically it's been DirectX that had a syscall per draw call, but I believe both now just write the command to GPU RAM directly.
[ Parent | on HN ]
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by bartread on Wednesday January 03, 2018 @01:56PM (#16063895)
That's at least somewhat encouraging. Nevertheless, it sounds rather like the old, "Yes, but will it run Crysis?" question will perhaps have renewed relevance.
[ Parent | on HN ]