On Tue, 04 Jun 2013 at 14:58:34 +0100, Simon McVittie wrote:
> What I'm more concerned about is whether the PowerPC JIT for the Quake 3
> bytecode language (code/qcommon/vm_powerpc*) emits Altivec opcodes - I
> have no idea how I'd determine that. That's why I'm specifically asking
> for testing wi
On 04/06/13 15:37, thinkbr...@gmail.com wrote:
> I did some tinkering with runtime detection when I was working on
> getting PPC64 support under Quake II, so I'll see if I can make
> something work. Maybe *ppcaltivec.so, *ppc.so, and *ppc64.so
The reason I suggested that *ppc.so should be the Alt
Hi,
I'm a porter of ppc64 port.
Unluckyly, ppc64 buildd nodes and my machines are shifting of place,
and they are offline now.
(If no trouble, plobably they will revive to online
on 2013-06-16.)
So, this build test cannot be done now,
but on ppc64 port, the packages have been tested
to be built
On Tue, Jun 4, 2013 at 9:58 AM, Simon McVittie wrote:
> On 04/06/13 13:58, thinkbr...@gmail.com wrote:
>> One thing I'd suggest is that
>> altivec is enabled based on the CPU itself, and not just PPC vs PPC64.
>
> Sorry, I'm not going to do significant development on this myself, but
> if you or a
On 04/06/13 13:58, thinkbr...@gmail.com wrote:
> One thing I'd suggest is that
> altivec is enabled based on the CPU itself, and not just PPC vs PPC64.
Sorry, I'm not going to do significant development on this myself, but
if you or another powerpc porter want to put a patchset together,
upstream
5 matches
Mail list logo
