Hi,
Riccardo Mottola wrote:
>
> This causes a big issue if you want to compile a non-Altivec build on
> a capable processor like the G4: it will automatically enabled even if
> you don't want.
> E.g. if I want to build on a G4 a binary working on the G3, I can't. I
> specify -mcpu=750 -mtune=750,
Hi Gabriel,
Gabriel Paubert wrote:
> This is going to be hopelessly slow. The point of SIMD is to process
> quickly vast amounts of data, the overhead of every single emulated
> instructions is counted in hundreds of cycles.
>
> IMHO, the only solution is to:
> a) only use SIMD in library code
>
Hi Luke,
Luke Kenneth Casson Leighton wrote:
>
> 1.5 and 1.9 never had SIMD / VMX / VSX so there shouldn't be a problem
> (for G5).
>
> which, coming back to the original question, i'm not seeing a reason
> why disabling altivec should not compile.
>
> unless, of course, there have been assumptio
changing subject, for reference / background:
* Paul Mackerras is working on an experimental branch to add VSX
https://github.com/paulusmack/microwatt/blob/vecvsx/decode1.vhdl
he was experimenting to see what was needed to get Fedora booting. the
internal design is a Finite State Machine. mult
On Tuesday, March 2, 2021, Riccardo Mottola
wrote:
> actually the original point is even for PPC32, note just PPC64. The
> configure check added by Adrian in Firefox checks if the compiler
> accepts -maltivec and just enables it in the build.
> However, this assumption is not correct and causes i
5 matches
Mail list logo
