- Original Message -
On 11/14/2011 10:13 PM, Jose Fonseca wrote:
- Original Message -
On 11/14/2011 09:48 PM, Christoph Bumiller wrote:
On 11/14/2011 09:24 PM, Jose Fonseca wrote:
- Original Message -
On 11/14/2011 08:23 PM, Jose Fonseca wrote:
On Sun, 2011-11-13 at 14:43 -0600, Bryan Cain wrote:
On 11/13/2011 09:06 AM, Dave Airlie wrote:
Hi guys,
Just been looking at llvmpipe integer support and it seems like we
lose some information about the type of data stored into temporaries,
after st_glsl_to_cpp we no longer know what
On Mon, 2011-11-14 at 09:42 +, Keith Whitwell wrote:
On Sun, 2011-11-13 at 14:43 -0600, Bryan Cain wrote:
On 11/13/2011 09:06 AM, Dave Airlie wrote:
Hi guys,
Just been looking at llvmpipe integer support and it seems like we
lose some information about the type of data stored
- Original Message -
On 13.11.2011 17:32, Christoph Bumiller wrote:
On 13.11.2011 17:10, Marek Olšák wrote:
I am guessing there is no type info because TGSI shaders are
allowed
to use uint, sint, and float instructions on the same register
without
type conversions (it would
- Original Message -
- Original Message -
On 13.11.2011 17:32, Christoph Bumiller wrote:
On 13.11.2011 17:10, Marek Olšák wrote:
I am guessing there is no type info because TGSI shaders are
allowed
to use uint, sint, and float instructions on the same register
On 14.11.2011 11:33, Jose Fonseca wrote:
- Original Message -
On 13.11.2011 17:32, Christoph Bumiller wrote:
On 13.11.2011 17:10, Marek Olšák wrote:
I am guessing there is no type info because TGSI shaders are
allowed
to use uint, sint, and float instructions on the same register
- Original Message -
On 14.11.2011 11:33, Jose Fonseca wrote:
- Original Message -
On 13.11.2011 17:32, Christoph Bumiller wrote:
On 13.11.2011 17:10, Marek Olšák wrote:
I am guessing there is no type info because TGSI shaders are
allowed
to use uint, sint, and
On 14.11.2011 12:28, Jose Fonseca wrote:
- Original Message -
Indirect addressing on TEMP should be forbidden and only allowed for
TEMPORARY_ARRAY, I'd very much like to know which values I can keep
in
registers and which ones I have to store to thread-local memory (I
can't
do things
- Original Message -
On 14.11.2011 12:28, Jose Fonseca wrote:
- Original Message -
Indirect addressing on TEMP should be forbidden and only allowed
for
TEMPORARY_ARRAY, I'd very much like to know which values I can
keep
in
registers and which ones I have to store
Having type info in TGSI registers is useless for llvm/llvmpipe, spite what
initial appearances may be.
Imagine indirect addressing on this hypothetical world with typed TGSI
declarations:
DCL_float TEMP[0]
DCL_int TEMP[1]
DCL_float TEMP[2]
DCL_int TEMP[3]
DCL_float TEMP[4]
- Original Message -
The next open question I have is whether this warrants additions to
the tgsi_opcode_info struct, mainly whether the return value is
uint/int/float,
and whether then src regs are uint/int/float, I'm not 100% that all
opcodes always take all int/uint/float srcs,
- Original Message -
- Original Message -
The next open question I have is whether this warrants additions to
the tgsi_opcode_info struct, mainly whether the return value is
uint/int/float,
and whether then src regs are uint/int/float, I'm not 100% that all
opcodes
On 11/14/2011 08:23 PM, Jose Fonseca wrote:
- Original Message -
The next open question I have is whether this warrants additions to
the tgsi_opcode_info struct, mainly whether the return value is
uint/int/float,
and whether then src regs are uint/int/float, I'm not 100% that all
- Original Message -
On 11/14/2011 08:23 PM, Jose Fonseca wrote:
- Original Message -
The next open question I have is whether this warrants additions
to
the tgsi_opcode_info struct, mainly whether the return value is
uint/int/float,
and whether then src regs
On 11/14/2011 09:24 PM, Jose Fonseca wrote:
- Original Message -
On 11/14/2011 08:23 PM, Jose Fonseca wrote:
- Original Message -
The next open question I have is whether this warrants additions
to
the tgsi_opcode_info struct, mainly whether the return value is
On 11/14/2011 09:48 PM, Christoph Bumiller wrote:
On 11/14/2011 09:24 PM, Jose Fonseca wrote:
- Original Message -
On 11/14/2011 08:23 PM, Jose Fonseca wrote:
- Original Message -
The next open question I have is whether this warrants additions
to
the tgsi_opcode_info
- Original Message -
On 11/14/2011 09:24 PM, Jose Fonseca wrote:
- Original Message -
On 11/14/2011 08:23 PM, Jose Fonseca wrote:
- Original Message -
The next open question I have is whether this warrants additions
to
the tgsi_opcode_info struct,
- Original Message -
On 11/14/2011 09:48 PM, Christoph Bumiller wrote:
On 11/14/2011 09:24 PM, Jose Fonseca wrote:
- Original Message -
On 11/14/2011 08:23 PM, Jose Fonseca wrote:
- Original Message -
The next open question I have is whether this
On 11/14/2011 10:13 PM, Jose Fonseca wrote:
- Original Message -
On 11/14/2011 09:48 PM, Christoph Bumiller wrote:
On 11/14/2011 09:24 PM, Jose Fonseca wrote:
- Original Message -
On 11/14/2011 08:23 PM, Jose Fonseca wrote:
- Original Message -
The next open
On 11/14/2011 10:36 PM, Christoph Bumiller wrote:
On 11/14/2011 10:13 PM, Jose Fonseca wrote:
My other reply was about this particular case.
But I'm not convinced we can ignore this case at all. I'm fine with drivers
cutting corners. By I can't accept an interface that's broken by
I am guessing there is no type info because TGSI shaders are allowed
to use uint, sint, and float instructions on the same register without
type conversions (it would be possible to generate such usage with
GL_ARB_shader_bit_enconding, also GL_NV_gpu_program4 has typeless
registers too). I think
On 13.11.2011 17:10, Marek Olšák wrote:
I am guessing there is no type info because TGSI shaders are allowed
to use uint, sint, and float instructions on the same register without
type conversions (it would be possible to generate such usage with
GL_ARB_shader_bit_enconding, also
On 13.11.2011 17:32, Christoph Bumiller wrote:
On 13.11.2011 17:10, Marek Olšák wrote:
I am guessing there is no type info because TGSI shaders are allowed
to use uint, sint, and float instructions on the same register without
type conversions (it would be possible to generate such usage with
On 11/13/2011 09:06 AM, Dave Airlie wrote:
Hi guys,
Just been looking at llvmpipe integer support and it seems like we
lose some information about the type of data stored into temporaries,
after st_glsl_to_cpp we no longer know what type the temporaries are,
and llvm would really like to
24 matches
Mail list logo
