<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - r300g: GL_COMPRESSED_RED_RGTC1 / ATI1N support broken" href="https://bugs.freedesktop.org/show_bug.cgi?id=89156#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - r300g: GL_COMPRESSED_RED_RGTC1 / ATI1N support broken" href="https://bugs.freedesktop.org/show_bug.cgi?id=89156">bug 89156</a> from <a class="email" href="mailto:stefandoesinger@gmx.at" title="Stefan Dösinger <stefandoesinger@gmx.at>"> Stefan Dösinger</a> <pre>(In reply to Marek Olšák from <a href="show_bug.cgi?id=89156#c5">comment #5</a>) > So it's a compiler bug. In which sense? Is there something in the spec that tells me I should expect garbage when I use texture2D().xxxx? Or is this something the driver tells the compiler and the compiler is supposed to generate a swizzle-free texture2D statement? > > static const char ati1n_data[] = > > { > > /* A 4x4 texture with the color component at 50%. */ > > 0x7f, 0x7f, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, > > }; > > That's expected. ATI1N operates at lower precision. I'm afraid I can't > change that. Windows gives me a proper value (0x7f, which is pretty close to 0x80). Do you have any idea how it does that? I can try to find a scheme behind the imprecision if it helps you. There may be something like an off by one error that the driver can account for.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>