Hi!
On 2023-04-12 1:18 p.m., Jakub Jelinek wrote:
> On Wed, Apr 12, 2023 at 01:05:14PM +0100, Pedro Alves wrote:
>>> I thought Ben has posted the details.
>>> In memory they look the same as 0 based arrays, but they often have
>>> different calling conventions (argument passing, returning), they s
On 2023-04-06 12:03 p.m., Jakub Jelinek via Dwarf-discuss wrote:
> In GCC, one uses vector_size attribute to define such types, so say
> typedef int V __attribute__((vector_size (64)));
> where 64 is number of bytes the vector has (so for 4 byte int it is 16
> elements).
> I think Clang supports b
On Wed, Apr 12, 2023 at 01:05:14PM +0100, Pedro Alves wrote:
> > I thought Ben has posted the details.
> > In memory they look the same as 0 based arrays, but they often have
> > different calling conventions (argument passing, returning), they support
> > various arithmetic operations on them, in
On 2023-04-06 1:03 p.m., Jakub Jelinek via Dwarf-discuss wrote:
> On Thu, Apr 06, 2023 at 07:52:32AM -0400, Ron Brender wrote:
>>> And we almost certainly want to allow vectors on DWARF expression stack;
>>
>> What is so special about vector types in this regard. What do you have
>> against values
On 2023-04-06 12:03 p.m., Jakub Jelinek via Dwarf-discuss wrote:
>> define fixed-length vectors as special built-in types or is the goal to
>> support
>> arbitrary vector lengths?
>>
>> It might be good to maintain an upper limit on the size of a stack entry.
> I think it is better if consumers si
