On Tuesday, March 2, 2021, Riccardo Mottola <riccardo.mott...@libero.it>
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 issues as explained
> in my previous mail.

ouch.  seems like an autoconf test is needed, at least.  and an upstream
bugreport to gcc.

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 "gcc -mg3 -maltivec" and this should
definitely cause gcc to raise an error, is that correct?

l.




-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68

Reply via email to