vkd3d-shader/dxil: Implement the DXIL BINOP instruction.
Compare changes
Files
16- Conor McCarthy authored
+ 228
− 0
@@ -242,6 +242,45 @@ enum dxil_shader_properties_tag
@@ -242,6 +242,45 @@ enum dxil_shader_properties_tag
@@ -1463,6 +1502,11 @@ static inline bool sm6_type_is_integer(const struct sm6_type *type)
@@ -1463,6 +1502,11 @@ static inline bool sm6_type_is_integer(const struct sm6_type *type)
@@ -2634,6 +2678,187 @@ static struct sm6_block *sm6_block_create()
@@ -2634,6 +2678,187 @@ static struct sm6_block *sm6_block_create()
- Comment on lines +2840 to +2854
This really makes me think that it's time to unlock VSIR from SM4 and let it live its own life. We shouldn't block the MR on this, sure, and separating VSIR and SM4 will probably be a pain because of the disassembler, but I don't think the disassembler should be the main decision factor for an IR.
enum dx_intrinsic_opcode op, const struct sm6_value **operands, struct vkd3d_shader_instruction *ins)
@@ -3233,6 +3458,9 @@ static enum vkd3d_result sm6_parser_function_init(struct sm6_parser *sm6, const
@@ -3233,6 +3458,9 @@ static enum vkd3d_result sm6_parser_function_init(struct sm6_parser *sm6, const