On 16/01/15 06:28 PM, DRC wrote: > I ended up having to fix this in a more robust way, since the issue > apparently doesn't just affect SPECviewperf 9+ -- it also affects a > commercial application (FEMFAT visualizer) that one of my customers uses. > > Check out the code in trunk or the binaries from here: > http://www.virtualgl.org/DeveloperInfo/PreReleases > > and let me know if I've broken anything. I've only tested it against > SPECviewperf 11-- haven't tested 9 or 10, but I assume they will work.
I reverted my "disable PBOs if the app has been naughty" patch and applied your "look up the real PBO symbols if the app has been naughty" patch. Testing viewperf 9 works fine. I can't find a vp10 at the moment, but I see from when I looked earlier in this thread the code was essentially the same. I see from your patch that you're optimistic this is only ever going to happen to PBO functions. I'll go on the record predicting that one day CHECKPBOSYM will be renamed CHECKVGLREQUIREDSYM and moved to faker-sym.* Call me a pessimist. :) -Nathan ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ VirtualGL-Devel mailing list VirtualGL-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-devel
