search for: pnacl

Hello, Following an earlier email ( http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-June/063010.html), we've published an initial version of the PNaCl bitcode reference manual online - http://www.chromium.org/nativeclient/pnacl/bitcode-abi. The PNaCl bitcode is a restricted subset of LLVM IR. The reference manual is quite terse, so for the bigger picture I'll repost links to the design document: * PDF: https://docs.google.com/a/chromium.org/...

I'm not familiar with PNaCl but, FWIW, I'd say the three main advancements the CLR made over the JVM are: . Structs (aka value types). . Reified generics. http://research.microsoft.com/pubs/64031/designandimplementationofgenerics.p df . Tail call elimination. http://research.microsoft.com/pubs/6913...

On 2013-07-30 22:11, Eli Bendersky wrote: > we've published an initial version of the PNaCl bitcode reference > manual online - > http://www.chromium.org/nativeclient/pnacl/bitcode-abi. The PNaCl > bitcode is a restricted subset of LLVM IR. > > Any comments would be most welcome. Hi Eli, I appreciate you for opening the process for input and comments. One question stood...

The PNaCl project has implemented various IR simplification passes that simplify LLVM IR by lowering complex features to simpler features. We'd like to upstream some of these IR passes to LLVM. We'd like to explore if this acceptable, and if so, how we should go about doing this. The immediate rea...

On Wed, Jul 31, 2013 at 11:55 PM, Travis Cross <tc at travislists.com> wrote: > On 2013-07-30 22:11, Eli Bendersky wrote: > > we've published an initial version of the PNaCl bitcode reference > > manual online - > > http://www.chromium.org/nativeclient/pnacl/bitcode-abi. The PNaCl > > bitcode is a restricted subset of LLVM IR. > > > > Any comments would be most welcome. > > Hi Eli, > > I appreciate you for opening the process f...

Hello, [The first paragraph is safe to skip if you already know what PNaCl is.] The Portable Native Client (PNaCl) project is a toolchain for producing portable bitcode from C and C++ code and running in securely and efficiently on the web via Native Client. For more details see this presentation from the last Google I/O: https://developers.google.com/events/io/sessions/3...

Hi Eli, Recently, I proposed some changes to LLVM to do more lowering of illegal types (like i128 or i17) and other things within the LLVM IR layer, and the proposal was roundly rejected by the LLVM community: http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-April/061567.html PNaCl is essentially doing what my proposal described. How do you expect to reconcile the community's desire to avoid doing lowering on LLVM IR with PNaCl's design that is built on doing lowering on LLVM IR? Dan On Tue, Jul 30, 2013 at 3:11 PM, Eli Bendersky <eliben at google.com> wrote:...

Is it possible to use PNaCl infrastructure (i.e. translation and execution in a sandbox) without a Chrome ? I mean a something like a standalone VM like Java or Mono/C#. Dmitri Am 18.06.2013 17:22, schrieb Eli Bendersky: > Hello, > > [The first paragraph is safe to skip if you already know what PNaCl is.] > Th...

> From the provided documentation I understood that in memory data > structures of a PNaCl program are incompatible to the host program because > ABIs are different (e.g. PNaCl pointers are always 32-bit even when running > on x86_64 platform). > So PNaCl program can't access any data structures of the host program > directly. The only communication way is by using syscal...

On 18 June 2013 15:27, Dmitri Rubinstein <dmitri.rubinstein at googlemail.com>wrote: > Is it possible to use PNaCl infrastructure (i.e. translation and execution > in a sandbox) without a Chrome ? > > I mean a something like a standalone VM like Java or Mono/C#. > Yes. The NaCl tool 'sel_ldr' will run a program inside a sandbox outside of the web browser. We do a lot of the testing of PNa...

Am 19.06.2013 18:01, schrieb JF Bastien: > > From the provided documentation I understood that in memory data > structures of a PNaCl program are incompatible to the host program > because ABIs are different (e.g. PNaCl pointers are always 32-bit > even when running on x86_64 platform). > So PNaCl program can't access any data structures of the host > program directly. The only communication way is...

From the provided documentation I understood that in memory data structures of a PNaCl program are incompatible to the host program because ABIs are different (e.g. PNaCl pointers are always 32-bit even when running on x86_64 platform). So PNaCl program can't access any data structures of the host program directly. The only communication way is by using syscalls, but the docu...

On Tue, Mar 4, 2014 at 6:17 PM, Chandler Carruth <chandlerc at google.com>wrote: > On Tue, Mar 4, 2014 at 1:04 PM, Mark Seaborn <mseaborn at chromium.org>wrote: > >> The PNaCl project has implemented various IR simplification passes that >> simplify LLVM IR by lowering complex features to simpler features. We'd >> like to upstream some of these IR passes to LLVM. We'd like to explore if >> this acceptable, and if so, how we should go about doi...

On 1 August 2013 00:11, Travis Cross <tc at travislists.com> wrote: > On 2013-07-30 22:11, Eli Bendersky wrote: > > we've published an initial version of the PNaCl bitcode reference > > manual online - > > http://www.chromium.org/nativeclient/pnacl/bitcode-abi. The PNaCl > > bitcode is a restricted subset of LLVM IR. > > > > Any comments would be most welcome. > > Hi Eli, > > I appreciate you for opening the process f...

...t of some refactorings I am making to BitstreamReader, I would like to simplify it by changing it to use a memory buffer directly and then removing the DataStreamer and MemoryObject interfaces. My understanding that the only significant user of that interface as designed (for network streaming) is PNaCl, however it looks like removing this interface would not impose a significant burden on that project; they are already maintaining a couple of forks of BitstreamReader [1] so it would appear that the only change necessary on their side would be to also fork the interfaces. If you are aware of any...

...nvention in the C world. > Further, I notice that the document includes > "call" but not "tail call" in the list of supported instructions. > > > That's an omission in the document. We do actually allow the "tail > call" instruction in PNaCl. Great. > However, we haven't specified any guarantees that a tail call > optimisation will happen. I suppose we could specify some > guarantees if people want this. I found a thread where Evan Cheng proposed removing -tailcallopt from LLVM. It resulted in a number of language imp...

...What I'm saying is that the approach to defining the format seems to be > basically "the format is LLVM IR, except ...". The "except ..." is > effectively a blacklist. You are starting with LLVM IR and then removing > (i.e. blacklisting certain aspects) > Well, PNaCl is defining a subset of LLVM IR. Language subsets can be defined by whitelisting or blacklisting features. Defining a subset of a language doesn't mean we're inherently doing blacklisting in PNaCl. We are deferring to LLVM's definition of the language semantics for the features that...

...am making to BitstreamReader, I would like > to simplify it by changing it to use a memory buffer directly and then > removing the DataStreamer and MemoryObject interfaces. > > My understanding that the only significant user of that interface as > designed (for network streaming) is PNaCl, however it looks like removing > this interface would not impose a significant burden on that project; they > are already maintaining a couple of forks of BitstreamReader [1] so it > would appear that the only change necessary on their side would be to also > fork the interfaces. >...

> The document is available as a PDF here: > https://docs.google.com/a/chromium.org/viewer?a=v&pid=sites&srcid=Y2hyb21pdW0ub3JnfGRldnxneDo0OWYwZjVkYWFjOWNjODE1 > > And in text here: > https://sites.google.com/a/chromium.org/dev/nativeclient/pnacl/stability-of-the-pnacl-bitcode-abi First, sorry for jumping in an old thread. I had this marked but had not been able to read it before. The document talks about ABI stability, but it is a bit unclear how far this goes. From older discussions, there are/were 3 interesting cases 1 Loading a stand...

We (PNaCl team) are in the process of removing older documentation, this is probably more accurate: https://developers.google.com/native-client/dev/ On Tue, Dec 17, 2013 at 6:50 AM, Sam Parker <S.Parker3 at lboro.ac.uk> wrote: > Check out PNaCL > http://www.chromium.org/nativeclient/pnacl >...