-
```
What steps will reproduce the problem?
I go to
https://naclports.storage.googleapis.com/builds/pepper_41/trunk-176-g9b9e342/pub
lish/devenv/pnacl/app/bash.html (this page is linked from
https:/…
-
```
What steps will reproduce the problem?
I go to
https://naclports.storage.googleapis.com/builds/pepper_41/trunk-176-g9b9e342/pub
lish/devenv/pnacl/app/bash.html (this page is linked from
https:/…
-
```
What steps will reproduce the problem?
I go to
https://naclports.storage.googleapis.com/builds/pepper_41/trunk-176-g9b9e342/pub
lish/devenv/pnacl/app/bash.html (this page is linked from
https:/…
-
pepper.js doesn't seem to be getting the love and attention that it deserves from the Native Client team (1 developer, no commits for 2 months).
This project needs to folded into the main Native Clie…
-
https://codereview.chromium.org/76153002/#ps170001
Thoughts on this?
-
Chrome will be releasing a video encoding pepper API for with Chrome 45. Since using Chrome's Portable Native Extensions (PNaCl) is invisible to the user (no installation steps necessary), I think it …
-
This is definitely a _long term_ effort. Ideally, the frontend would not need to be concerned with calling convention details. Achieving this is harder than it first appears, and probably requires an …
-
I think you have problem on load:
`ret = mount("", "/", "html5fs", 0, "type=PERSISTENT");
if(ret) {
printf("mount() html5fs fial %s\n",strerror(errno));
return ret;
}
ret = chdir("/tmp");…
-
Error in PageSpeed background page:Pagespeed module has an error: NaCl module load failed: PnaclCoordinator: Compile stream init failed: reply not received from PNaCl translator (it probably crashed) …
-
| | |
| --- | --- |
| Bugzilla Link | [18863](https://llvm.org/bz18863) |
| Version | 3.4 |
| OS | All |
| Blocks | llvm/llvm-project#15837 |
| Attachments | [sret.cpp](https://user-images.githubus…