Jeff Law writes:
> On 10/5/19 5:29 AM, Richard Sandiford wrote:
>>
>> Sure. This message is going to go to the other extreme, sorry, but I'm
>> not sure which part will be the most convincing (if any).
> No worries. Worst case going to the other extreme is I have to read it
> more than once aft
On 10/5/19 5:29 AM, Richard Sandiford wrote:
>
> Sure. This message is going to go to the other extreme, sorry, but I'm
> not sure which part will be the most convincing (if any).
No worries. Worst case going to the other extreme is I have to read it
more than once after nodding off halfway thro
Jeff Law writes:
> On 9/26/19 6:04 AM, Richard Sandiford wrote:
>> Although it's possible to define the SVE intrinsics in a normal header
>> file, it's much more convenient to define them directly in the compiler.
>> This also speeds up compilation and gives better error messages.
>>
>> The idea
On 9/26/19 6:04 AM, Richard Sandiford wrote:
> Although it's possible to define the SVE intrinsics in a normal header
> file, it's much more convenient to define them directly in the compiler.
> This also speeds up compilation and gives better error messages.
>
> The idea is therefore for arm_sve.
