alberthrocks

IRC logs for Emscripten bug

Jan 28th, 2012
248
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.64 KB | None | 0 0
  1. [18:53:29] <alberthrocks> azakai|2: I've implemented those funcs, but now when trying to run it, it fails with "array initialiser too large".
  2. [20:54:36] <azakai|2> alberthrocks: pastebin the .cpp, .ll and .js and i'll take a look
  3. [20:56:15] <alberthrocks> woo, you're here! :D
  4. [20:56:31] <alberthrocks> Let's see.... the JS would be kinda big, so...
  5. [20:56:46] <alberthrocks> I'm going to gzip it and throw it up on my mercurial repo, if it's alright with you.
  6. [21:08:57] <azakai|2> ok
  7. [21:09:31] <azakai|2> alberthrocks: or give me the patch with the funcs, and the source c++ and i'll compile it myself
  8. [21:15:28] <alberthrocks> heh too late :P
  9. [21:15:54] <alberthrocks> source+binaries (gzipped binaries): http://code.google.com/p/sdlwabbitemu/source/checkout
  10. [21:16:00] * Geri has quit (Quit: -)
  11. [21:17:43] <azakai|2> heh
  12. [21:18:09] <azakai|2> alberthrocks: which file should i get?
  13. [21:18:24] <azakai|2> the .gz files?
  14. [21:18:31] <alberthrocks> yup
  15. [21:18:48] <alberthrocks> also, http://pastebin.com/YM5dLB3c and https://github.com/alberthrocks/emscripten
  16. [21:19:46] <alberthrocks> (for those func changes)
  17. [21:20:03] <azakai|2> hmm
  18. [21:20:20] <alberthrocks> sdlwabbitemu.web.html runs fine in Chrome, not in FF9.0.1
  19. [21:20:36] <azakai|2> i guess this is running into a js engine bug, or rather limitation, with the size of arrays
  20. [21:20:46] <alberthrocks> although to be fair, Chrome does warn about extending the array mem
  21. [21:21:08] <azakai|2> what does it say?
  22. [21:21:17] <azakai|2> oh, the "this is slow" warning?
  23. [21:21:41] <alberthrocks> yeah
  24. [21:21:54] <azakai|2> that's an internal emscripten runtime warning, not a chrome thing
  25. [21:22:13] <azakai|2> it's a response to your using a lot of memory in this code ;)
  26. [21:22:36] <azakai|2> ok, i definitely need to fix this bug, we need to note create a single huge array like that, split it up somehow
  27. [21:22:47] <alberthrocks> memory? :P
  28. [21:23:03] <azakai|2> "fake" memory ;)
  29. [21:23:48] <alberthrocks> ahh :) I was going to say that 4.5 MBs of memory isn't much :P
  30. [21:24:01] <alberthrocks> (0.3% of 1.5GB reported by top)
  31. [21:24:02] <azakai|2> can you file a github issue to remind me to fix this? (i have to finish some other stuff first). with a link to the .js gzip file?
  32. [21:24:42] <alberthrocks> sure :)
  33. [21:24:57] <alberthrocks> should I copy and paste this chat log?
  34. [21:24:58] <azakai|2> yeah, 4.5 isn't much ;) but it's more than the default memory emscripten allocates, since we don't want to use a lot of memory even for a tiny compiled code. so we enlarge the memory at runtime when necessary. (that warning is only shown in -O0 builds, not optimized ones btw)
  35. [21:25:17] <azakai|2> sure, yeah
Advertisement
Add Comment
Please, Sign In to add comment