On Saturday, March 6, 2021, Riccardo Mottola
wrote:
> Hi Luke,
>
>
> Luke Kenneth Casson Leighton wrote:
>>
>> just to confirm: that's definitely "setting machine to capabilities that
the machine doesn't have, then requesting that feature and gcc 10 says
'ok'" yes?
>>
>> i do not know the exact
Hi Luke,
Luke Kenneth Casson Leighton wrote:
just to confirm: that's definitely "setting machine to capabilities
that the machine doesn't have, then requesting that feature and gcc 10
says 'ok'" yes?
i do not know the exact machine, let us assume it is -mg3.
the options being passed are
On Tuesday, March 2, 2021, Luke Kenneth Casson Leighton
wrote:
>
>
> 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
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
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.
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
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,
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,
On Mon, Mar 1, 2021 at 3:39 AM Gabriel Paubert wrote:
>
> On Sun, Feb 28, 2021 at 11:52:12PM +, Luke Kenneth Casson Leighton wrote:
> > On Monday, March 1, 2021, Riccardo Mottola
> > wrote:
> > ...
> > Tulio Magno Quites Machado Filho is currently working on glibc6 patches
> > which reverse
On Monday, March 1, 2021, Gabriel Paubert wrote:
> On Mon, Mar 01, 2021 at 12:22:22PM +, Luke Kenneth Casson Leighton
wrote:
>> ---
>> crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
>>
>> On Mon, Mar 1, 2021 at 8:39 AM Gabriel Paubert wrote:
>>
>> > Beware that VSX
On Mon, Mar 01, 2021 at 12:22:22PM +, Luke Kenneth Casson Leighton wrote:
> ---
> crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
>
> On Mon, Mar 1, 2021 at 8:39 AM Gabriel Paubert wrote:
>
> > Beware that VSX is not Altivec. Altivec was called VMX by IBM and
> > VSX
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Mon, Mar 1, 2021 at 8:39 AM Gabriel Paubert wrote:
> Beware that VSX is not Altivec. Altivec was called VMX by IBM and
> VSX is a superset of Altivec (IIRC).
>
> G4 and G5 do not have VSX.
apologies i tend to lump
On Sun, Feb 28, 2021 at 11:52:12PM +, Luke Kenneth Casson Leighton wrote:
> On Monday, March 1, 2021, Riccardo Mottola
> wrote:
>
> > A quick solution would to have this configure as a convenience, but have
> a way to pass an --enable-altivec and -disable-altivec (or with/without?)
>
On Monday, March 1, 2021, Riccardo Mottola
wrote:
> A quick solution would to have this configure as a convenience, but have
a way to pass an --enable-altivec and -disable-altivec (or with/without?)
parameter to configure.
EABI v2.0 rather unfortunately, despite it being optional in the
Hello,
I was checkin gout a specific patch Adrian made for Firefox, which
should help building on non-Altivec capable CPUs.
https://github.com/mozilla/gecko-dev/commit/c6b39f0f902898988ca7793af56307640ff81362
I have imported it in ArcticFox with this commit and tested it.
15 matches
Mail list logo
