StarMirror/sandboxed-api
1
0
Fork 0
mirror of https://github.com/google/sandboxed-api.git synced 2024-03-22 13:11:30 +08:00
Code Issues Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
doinachiroiu 2020-08-20 13:15:02 +00:00
parent 726a9345ff
commit a2873ac099
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
oss-internship-2020/pffft/README.md
View File

@ -58,7 +58,7 @@ In the end, the performance of PFFFT library it is outlined by the output.*
N > 64, status not OK N > 64, status not OK
Problem on initialising sapi::StatusOr<PFFFT_Setup *> s; the memory that stays Problem on initialising sapi::StatusOr<PFFFT_Setup *> s; the memory that stays
for s is not the same with the address passed in pffft_transform function. for s is not the same with the address passed in pffft_transform function.
(sapi :: v :: GenericPtr - to be changed) (sapi::v::GenericPtr - to be changed)
Temporary solution: change the generated files to accept Temporary solution: change the generated files to accept
uintptr_t instead of PFFFT_Setup uintptr_t instead of PFFFT_Setup
@ -66,7 +66,7 @@ In the end, the performance of PFFFT library it is outlined by the output.*
Solution: using "sapi::v::RemotePtr" instead of "sapi::v::GenericPtr" Solution: using "sapi::v::RemotePtr" instead of "sapi::v::GenericPtr"
to access the memory of object s to access the memory of object s
- [Unresolved] compiling bug: "No spave left on device" - [Unresolved] compiling bug: "No space left on device"
The building process creates some `embed` files that use lots of The building process creates some `embed` files that use lots of
memory, trying to write them on /tmp. memory, trying to write them on /tmp.