sbc100 added a comment. At least for WebAssembly object files, it looks like the symbol table now contains (what look like) demangled symbols. e.g.:
$ llvm-nm /tmp/emscripten_temp/command_0.o 00003ef5 D __odr_asan_gen__numargs 000041a6 D __odr_asan_gen__stdcmd<1068>::init 000041c3 D __odr_asan_gen__stdcmd<1069>::init 000041e0 D __odr_asan_gen__stdcmd<1070>::init 000041fd D __odr_asan_gen__stdcmd<1071>::init 0000421a D __odr_asan_gen__stdcmd<1073>::init 0000423f D __odr_asan_gen__stdcmd<1074>::init 0000425c D __odr_asan_gen__stdcmd<1075>::init 00004279 D __odr_asan_gen__stdcmd<1076>::init 0000429e D __odr_asan_gen__stdcmd<1077>::init 000042bc D __odr_asan_gen__stdcmd<1078>::init Symbol names with colon in them currently cause issues with the emscripten compiler (when parsing the output of `llvm-nm`). If this is intensional we can look into re-working the parser, but I just wanted to check if this was indented behaviour? Are these character allows in symbol names? Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D137227/new/ https://reviews.llvm.org/D137227 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
