<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic wglShareLists does not apply to fragment shaders? in Developing Games on Intel Graphics</title>
    <link>https://community.intel.com/t5/Developing-Games-on-Intel/wglShareLists-does-not-apply-to-fragment-shaders/m-p/907946#M680</link>
    <description>Hi,
&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;
&lt;DIV&gt;developing a GPGPU application that makes use of OpenGL pbuffers on Intel 945 GMA, I noticed that I have to run each ARBFP1.0 fragment shader through the assembler/compiler individually for each OpenGL context associated to a pbuffer.&lt;/DIV&gt;
&lt;DIV&gt;This creates some extra overhead and consumes more memory.&lt;/DIV&gt;
&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;
&lt;DIV&gt;The wglShareLists() API call works with textures and other OpenGL objects, but apparently shaders are not included.&lt;/DIV&gt;
&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;
&lt;DIV&gt;Is this by design or is this a driver bug?&lt;/DIV&gt;
&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;
&lt;DIV&gt;With kind regards,&lt;/DIV&gt;
&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;
&lt;DIV&gt; Christian Buchner&lt;/DIV&gt;
&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;</description>
    <pubDate>Tue, 10 Feb 2009 13:34:43 GMT</pubDate>
    <dc:creator>christianbuchner</dc:creator>
    <dc:date>2009-02-10T13:34:43Z</dc:date>
    <item>
      <title>wglShareLists does not apply to fragment shaders?</title>
      <link>https://community.intel.com/t5/Developing-Games-on-Intel/wglShareLists-does-not-apply-to-fragment-shaders/m-p/907946#M680</link>
      <description>Hi,
&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;
&lt;DIV&gt;developing a GPGPU application that makes use of OpenGL pbuffers on Intel 945 GMA, I noticed that I have to run each ARBFP1.0 fragment shader through the assembler/compiler individually for each OpenGL context associated to a pbuffer.&lt;/DIV&gt;
&lt;DIV&gt;This creates some extra overhead and consumes more memory.&lt;/DIV&gt;
&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;
&lt;DIV&gt;The wglShareLists() API call works with textures and other OpenGL objects, but apparently shaders are not included.&lt;/DIV&gt;
&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;
&lt;DIV&gt;Is this by design or is this a driver bug?&lt;/DIV&gt;
&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;
&lt;DIV&gt;With kind regards,&lt;/DIV&gt;
&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;
&lt;DIV&gt; Christian Buchner&lt;/DIV&gt;
&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 10 Feb 2009 13:34:43 GMT</pubDate>
      <guid>https://community.intel.com/t5/Developing-Games-on-Intel/wglShareLists-does-not-apply-to-fragment-shaders/m-p/907946#M680</guid>
      <dc:creator>christianbuchner</dc:creator>
      <dc:date>2009-02-10T13:34:43Z</dc:date>
    </item>
    <item>
      <title>Re: wglShareLists does not apply to fragment shaders?</title>
      <link>https://community.intel.com/t5/Developing-Games-on-Intel/wglShareLists-does-not-apply-to-fragment-shaders/m-p/907947#M681</link>
      <description>&lt;DIV style="margin:0px;"&gt;&lt;/DIV&gt;
&lt;BR /&gt;It should. Which part are you trying to use this call on?</description>
      <pubDate>Wed, 04 Mar 2009 19:22:03 GMT</pubDate>
      <guid>https://community.intel.com/t5/Developing-Games-on-Intel/wglShareLists-does-not-apply-to-fragment-shaders/m-p/907947#M681</guid>
      <dc:creator>Chuck_De_Sylva</dc:creator>
      <dc:date>2009-03-04T19:22:03Z</dc:date>
    </item>
  </channel>
</rss>

