René's patch seems to have stalled, so here is an updated version of the
patch with the requested changes to his patch.
I'll note I have added an additional code change, which is to also emit a
".machine altivec" if Altivec is enabled. The problem this fixes is for
cpus like the G5, which is basi
Hi Peter,
> On Jul 12, 2024, at 23:48, Peter Bergner wrote:
>
> René's patch seems to have stalled, so here is an updated version of the
> patch with the requested changes to his patch.
Yes, sorry. Our Linux distribution grew so much in popularity the last
month that I had hard weeks keeping up
Hi Peter,
on 2024/7/13 05:48, Peter Bergner wrote:
> René's patch seems to have stalled, so here is an updated version of the
> patch with the requested changes to his patch.
>
> I'll note I have added an additional code change, which is to also emit a
> ".machine altivec" if Altivec is enabled.
On 7/18/24 4:14 AM, Kewen.Lin wrote:
>> +/* { dg-final { scan-assembler {\.\mmachine power4\M} } } */
>> +/* { dg-final { scan-assembler {\.\mmachine altivec\M} } } */
>
> Nit: Both \m looks useless and can be removed.
Fine with me. Is that because the \. acts like a \m?
>> Ok for trunk and t
On 7/18/24 9:14 AM, Peter Bergner wrote:
> On 7/18/24 4:14 AM, Kewen.Lin wrote:
>>> +/* { dg-final { scan-assembler {\.\mmachine power4\M} } } */
>>> +/* { dg-final { scan-assembler {\.\mmachine altivec\M} } } */
>>
>> Nit: Both \m looks useless and can be removed.
>
> Fine with me. Is that becau
on 2024/7/18 22:14, Peter Bergner wrote:
> On 7/18/24 4:14 AM, Kewen.Lin wrote:
>>> +/* { dg-final { scan-assembler {\.\mmachine power4\M} } } */
>>> +/* { dg-final { scan-assembler {\.\mmachine altivec\M} } } */
>>
>> Nit: Both \m looks useless and can be removed.
>
> Fine with me. Is that becau