--
You received this message because you are subscribed to the Google Groups "Native-Client-Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to native-client-di...@googlegroups.com.
To post to this group, send email to native-cli...@googlegroups.com.
Visit this group at http://groups.google.com/group/native-client-discuss.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to native-client-discuss+unsub...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to native-client-discuss+unsub...@googlegroups.com.
Just curious: are the GCC/LLVM vector extensions by now available in pepper_canary? I have been looking out for a header file defining the PNaCl-specific "generic" SIMD intrinsics but wasn't able to find one.The native client source has a file simd.h, which comes with a fairly comprehensive set of "builtin" intrinsics. Will these be the ones that make it into pepper?
--
You received this message because you are subscribed to a topic in the Google Groups "Native-Client-Discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/native-client-discuss/CgLtRlGIDIU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to native-client-di...@googlegroups.com.
To post to this group, send email to native-cli...@googlegroups.com.
Visit this group at http://groups.google.com/group/native-client-discuss.
For more options, visit https://groups.google.com/d/optout.
Fantastic! That’s (almost) everything I need for now. Using some quirks, I think I can work around the missing intrinsics (like for _mm_min_pd, _mm_max_pd, _m_psadbw, etc. from xmmintrin.h/emmintrin.h) and still be faster than the scalar operations.
Other than that, I wonder if you can provide compatibility wrappers for the non-portable x86 SIMD (for now, the 128 bit MMX and SSE variants) intrinsics. I understand that portability is a design goal. Then again, most legacy code using platform-specific SIMD intrinsics would probably have an x86 variant. Not sure to what extent the NEON, AltiVec and whatever-the-MIPS-SIMD-instruction-set is named can be mapped to MMX/SSE or had to be emulated.
And btw, is this now also supported in the current Chrome Canary?
On a remotely related note: are there plans to also support OpenCL in PNaCl at some point? WebCL does not seem to be going anywhere (happy to be educated otherwise) and doing GPGPU based on OpenGL ES/WebGL is somewhat painful.
--
You received this message because you are subscribed to the Google Groups "Native-Client-Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to native-client-di...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to native-client-discuss+unsub...@googlegroups.com.
> Thanks heaps - it's in pepper_canary since yesterday - great work! I had some initial success with some toy examples, which do compile. One useful addition was to support the ternary ?: operator with vector types, which works in g++ (not in gcc for some reason) - see here: http://gcc.gnu.org/onlinedocs/gcc/Vector-Extensions.html.
That's a limitation of Clang, probably not hard to fix but either approach should generate the same code, otherwise it's a performance bug that should be fixed too.
We're finishing up a few more things for the Chrome 36 release, I can look at this afterwards. It should only be a frontend change, so Chrome version won't matter much (any fix there will be usable from pepper canary, and work in older Chrome).
> If it's merely syntactic sugar, it may not be worthwhile in the first place.
>
> On a different note, I could compile some code with added vector instructions, but was unable to run it in Chrome Canary (Mac, 36.0.1973.2 canary). I get an error on the Javascript console stating "NativeClient: PnaclCoordinator: PNaCl Translator Error: Unknown type code in type table: 12" which I assume means that this version of Chrome doesn't have vector support as yet...
I assume so, but to be sure do you have a way we can reproduce this?
> If it's merely syntactic sugar, it may not be worthwhile in the first place.
>
> On a different note, I could compile some code with added vector instructions, but was unable to run it in Chrome Canary (Mac, 36.0.1973.2 canary). I get an error on the Javascript console stating "NativeClient: PnaclCoordinator: PNaCl Translator Error: Unknown type code in type table: 12" which I assume means that this version of Chrome doesn't have vector support as yet...I assume so, but to be sure do you have a way we can reproduce this?
--
You received this message because you are subscribed to the Google Groups "Native-Client-Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to native-client-di...@googlegroups.com.
Hi Soeren,
The PNaCl translator component is updated separately from the rest of Chrome. The dev and canary channels should now be getting the updates automatically. Check your PNaCl translator version in chrome://nacl and look for a version >= 0.1.0.13104. If you don't have that you can try checking chrome://components and click the "check for update" button under pnacl (then you'll just have to wait a bit: it's not a fantastic UI) but you should get the update fairly quickly then.
On Sun May 04 2014 at 6:18:03 PM, Soeren Balko <soe...@zfaas.com> wrote:
I tried with the simple-most program conceivable - please see here for the source: http://pastebin.com/D11C6GdAThe versions of Chrome I tried are Chromium 36.0.1975.0 (268124) and Chrome 36.0.1974.2 canary (all on OSX). Will try on Ubuntu later today to confirm. I reckon this is a simple issue of the feature not having progressed to the canary builds.Soeren--
On Monday, May 5, 2014 3:45:15 AM UTC+10, JF Bastien wrote:Just to clarify, 12 is indeed naclbitc::TYPE_CODE_VECTOR so it does look like the error you'd get.> If it's merely syntactic sugar, it may not be worthwhile in the first place.
>
> On a different note, I could compile some code with added vector instructions, but was unable to run it in Chrome Canary (Mac, 36.0.1973.2 canary). I get an error on the Javascript console stating "NativeClient: PnaclCoordinator: PNaCl Translator Error: Unknown type code in type table: 12" which I assume means that this version of Chrome doesn't have vector support as yet...I assume so, but to be sure do you have a way we can reproduce this?
You received this message because you are subscribed to the Google Groups "Native-Client-Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to native-client-discuss+unsub...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to native-client-di...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to native-client-discuss+unsubscri...@googlegroups.com.
To post to this group, send email to native-cli...@googlegroups.com.
Visit this group at http://groups.google.com/group/native-client-discuss.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to native-client-discuss+unsubscri...@googlegroups.com.
To post to this group, send email to native-cli...@googlegroups.com.
Visit this group at http://groups.google.com/group/native-client-discuss.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Native-Client-Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to native-client-discuss+unsub...@googlegroups.com.
To post to this group, send email to native-cli...@googlegroups.com.
Visit this group at http://groups.google.com/group/native-client-discuss.
For more options, visit https://groups.google.com/d/optout.