Bug 90337 - i965: fs_visitor::nir_emit_alu() hits assertion on a dEQP test
Summary: i965: fs_visitor::nir_emit_alu() hits assertion on a dEQP test
Status: RESOLVED INVALID
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Ian Romanick
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-06 12:18 UTC by Eduardo Lima Mitev
Modified: 2015-05-08 06:55 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Eduardo Lima Mitev 2015-05-06 12:18:16 UTC 
dEQP test 'dEQP-GLES3.functional.fbo.color.texcube.rgba32i' reaches assert in nir_emit_alu() of fs_visitor.


$ INTEL_USE_NIR=1 ./deqp-gles3 -n dEQP-GLES3.functional.fbo.color.texcube.rgba32i
dEQP Core 2014.x (0xcafebabe) starting..
  target implementation = 'Default'

Test case 'dEQP-GLES3.functional.fbo.color.texcube.rgba32i'..
deqp-gles3: brw_fs_nir.cpp:636: void fs_visitor::nir_emit_alu(nir_alu_instr*): Assertion `__builtin_popcount(instr->dest.write_mask) == 1' failed.
Aborted

Disabling NIR passes the test.
Comment 1 Eduardo Lima Mitev 2015-05-07 14:09:59 UTC 
This other dEQP test also hits the same assertion: dEQP-GLES3.functional.shaders.indexing.tmp_array.vec2_dynamic_write_static_read_fragment
Comment 2 Jason Ekstrand 2015-05-08 03:07:15 UTC 
What mesa revision are you using?  What hardware?  I built the deqp suite and I can't reproduce the crash.
Comment 3 Eduardo Lima Mitev 2015-05-08 06:55:21 UTC 
The hardware is a Haswell laptop. I was using master as of 06/05 (git~cf5e015).

But I just discovered that I had disabled many passes in brw_vec4.cpp due to my work on nir-vec4, and that was the cause. Since the assertion was in brw_fs_nir I assumed it was unrelated, but it was not.

I'm badly sorry for the noise!

Closing as invalid.

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.