Summary: | [HSW bisected] integer multiplication bug | ||
---|---|---|---|
Product: | Mesa | Reporter: | Tapani Pälli <lemody> |
Component: | Drivers/DRI/i965 | Assignee: | Matt Turner <mattst88> |
Status: | RESOLVED FIXED | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Severity: | normal | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | test |
Description
Tapani Pälli
2015-05-22 07:35:43 UTC
Created attachment 115967 [details]
test
piglit shader_test case to hit the bug
Following conformance test hits this issue: ES3-CTS.shaders.loops.for_constant_iterations.unconditional_break_fragment Oops, the test I posted actually fails like this: ---8< --- shader_runner: brw_fs_generator.cpp:106: brw_reg brw_reg_from_fs_reg(fs_reg*): Assertion `reg->type == reg->fixed_hw_reg.type' failed. Aborted (core dumped) ---8< --- with some changes it failed like in comment #1, I can try to get them back. (In reply to Tapani Pälli from comment #3) > with some changes it failed like in comment #1, I can try to get them back. nope, that only happens when bisecting between commits which I believe fix this thing, so the relevant error is what comes with the current master: shader_runner: brw_fs_generator.cpp:106: brw_reg brw_reg_from_fs_reg(fs_reg*): Assertion `reg->type == reg->fixed_hw_reg.type' failed. Aborted (core dumped) Oh wow, we end up propagating the conditional_mod to an integer multiply that we'll have to lower:
> { 1} 2: mul.le.f0.0(8) null:D, vgrf0:D, vgrf0:D
which then doesn't work. Thanks for the report. I'll see what I can do.
Patch on the list:
> i965/fs: Fix lowering of integer multiplication with cmod.
Fixed with commit 0596134410a0decc2f6bba77bfedb82d308aabbe Author: Matt Turner <mattst88@gmail.com> Date: Wed May 27 10:44:45 2015 -0700 i965/fs: Fix lowering of integer multiplication with cmod. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.