Very odd, never seen anything like that. Is there a malloc445 function in your codebase?
Can use EMCC_DEBUG and llvm -print-after-all to see which IR pass makes that change, if not. - Alon On Tue, Mar 4, 2014 at 6:05 AM, Bruce Mitchener <[email protected]>wrote: > Hello, > > I have some code using the old compiler (but on incoming) and I'm seeing > _malloc get renamed (but not _free). > > Some examples ... in the LLVM IR, it is fine: > > %944 = call i8* @malloc(i32 4) nounwind optsize > > But then I call emcc on that and here's the first stage afterwards: > > r7=_malloc445(8); > > I'm calling emcc as follows: > > /usr/bin/python third-party/emscripten/emcc \ > -v \ > --llvm-opts 0 \ > -O2 \ > -s ASM_JS=0 \ > -s RELOOP=1 \ > -s TARGET_X86=0 \ > -s TARGET_LE32=1 \ > -s ALLOW_MEMORY_GROWTH=1 \ > -s ASSERTIONS=0 \ > -s "EXPORTED_FUNCTIONS=['_main', '_malloc', '_free']" \ > -s SHELL_FILE="'/Users/bruce/Development/.../EmscriptenShell.js.shell'" > build/Emscripten.opt.ll -o build/Emscripten.raw.js > > The EXPORTED_FUNCTIONS setting doesn't matter. I added it, but the problem > happened without it as well. > > Can anyone explain why this is happening? This and one other issue are > blocking me. > > - Bruce > > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
