-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can coreclr compile their code with debuginfod? #1924
Comments
Aside: src/coreclr, and src/libraries (and soon src/installer: #1753) do compile with gcc, in addition to clang: runtime/eng/native/gen-buildsys.sh Lines 66 to 67 in 1cb1285
|
That is good news. Is this a new change? If it possible can we compare benchmark? I feel GCC is what dotnet should use to ship binary since gcc in my experience generates more efficient and icache friendly code. |
it is relatively new: the support was added around v3.0 release to bring up coreclr on more platforms like smartos (solaris based); where llvm toolchain is not readily available (e.g. lldb is still not available on pkgsrc for smartos). some caveats:
src/coreclr/build.sh -gcc -cmakeargs -DCMAKE_CXX_FLAGS=-Wno-class-memaccess |
update: we can now pass various arguments from top-level scripts for native compilation: cd runtime
# compile coreclr, installer and libraries using gcc 7
./build.sh --gcc7 --cmakeargs -DFeatureX=1 -cmakeargs -DFeatureY=0
# compile only coreclr using clang
./build.sh --subsetCategory coreclr --clang --cmakeargs -DFeatureX=1 -cmakeargs -DFeatureY=0 |
I would love to see this implemented for .NET core symbols as many Linux tools already include debuginfod support. |
debuginfod
is the symbol server equivalent for elf/dbg files.Seems like requires gcc. another reason why Coreclr should be compilable with gcc.
The text was updated successfully, but these errors were encountered: