On Fri, Feb 17, 2023 at 9:11 AM Stan Srednyak <stan.sr...@gmail.com> wrote:
>
> thanks for your reply.
> The Mmap functionality is crucial for my app. I am dealing with large binary 
> trees that do not fit RAM. I implemented them on disk, and for this, Mmap is 
> crucial.
>
> Now I have a client that wants to run the app from inside a virtual box, and 
> for security reason, they want .wasm code.

Sorry, I have no idea whether this is possible using wasm.  I suspect
that it is not but I am not an expert.

Ian


> On Fri, Feb 17, 2023 at 11:14 AM Ian Lance Taylor <i...@golang.org> wrote:
>>
>> On Fri, Feb 17, 2023, 6:47 AM Stan Srednyak <stan.sr...@gmail.com> wrote:
>>>
>>> I have a Go code that I am trying to compile to .wasm. The code uses 
>>> syscall.Mmap.
>>>
>>> I am getting  undefined: syscall.Mmap
>>>
>>>
>>> What is this error and what do I do with it?
>>
>>
>> The syscall package provides system dependent functionality.  Wasm does not 
>> support memory mapping, so syscall.Mmap does not exist on Wasm.
>>
>> In order to make any useful suggestions we would have to know why your Go 
>> code is calling Mmap.
>>
>> Ian

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/CAOyqgcX-2SgB%3Dq9bPKSxugfKD4-yTNFPUmSsF8zA5mdfzOrYrw%40mail.gmail.com.

Reply via email to