Bug 103115 - [BSW BXT GLK] dEQP-VK.spirv_assembly.instruction.compute.sconvert.int32_to_int64
Summary: [BSW BXT GLK] dEQP-VK.spirv_assembly.instruction.compute.sconvert.int32_to_int64
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Matt Turner
QA Contact: Intel 3D Bugs Mailing List
Depends on:
Blocks: mesa-17.3
  Show dependency treegraph
Reported: 2017-10-05 19:57 UTC by Mark Janes
Modified: 2017-11-14 18:57 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Mark Janes 2017-10-05 19:57:06 UTC
This test and three others regressed at 
mesa 2572c2771d0cab0b9bc489d354ede44dfc88547b
Author:     Matt Turner <mattst88@gmail.com>
i965: Validate "Special Requirements for Handling Double Precision Data Types"

I did not implement:

   CNL's restriction on 64-bit int + align16, because I don't think
   we'll ever use this combination regardless of hardware generation.

   The restriction on immediate DF -> F conversions, because there's no
   reason to ever generate that, and I don't even know how DF -> F
   conversions are supposed to work in Align16 since (1) the dst stride
   must be 1, but (2) the dst stride would have to be 2 for src and dst
   strides to be aligned.


deqp-vk: /home/jenkins/workspace/Leeroy_2/repos/mesa/src/intel/compiler/brw_fs_generator.cpp:2203: int fs_generator::generate_code(const cfg_t*, int): Assertion `validated' failed.
Comment 1 Matt Turner 2017-11-08 23:21:39 UTC
Testing a fix.
Comment 2 Matt Turner 2017-11-09 21:42:52 UTC
Patch on the list to fix this:

i965/fs: Split all 32->64-bit MOVs on CHV, BXT, GLK

Also fixes

Comment 3 Matt Turner 2017-11-14 18:57:14 UTC
commit cfcfa0b9cd1b1d563a988b1250950057c4612ac9
Author: Matt Turner <mattst88@gmail.com>
Date:   Wed Nov 8 15:14:19 2017 -0800

    i965/fs: Split all 32->64-bit MOVs on CHV, BXT, GLK

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.