https://bugs.freedesktop.org/show_bug.cgi?id=89156
--- Comment #6 from Stefan Dösinger <stefandoesinger at gmx.at> ---
(In reply to Marek Olšák from comment #5)
> 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.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150226/04f6519d/attachment.html>
