You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for reporting this. I am just curious, do you have a reason for using GNU C++ instead of clang? While we try to maintain the ability to compile using GNU C++, we don't use it for our builds.
I use gcc out of inertia. I will switch to clang, for now. I suspect that
more work has gone into gcc-11 (and gcc-10) than clang for the arm64 port,
but can not back that up with any hard data.
On Tue, May 18, 2021 at 7:56 AM Jan Vorlicek ***@***.***> wrote:
Thank you for reporting this. I am just curious, do you have a reason for
using GNU C++ instead of clang? While we try to maintain the ability to
compile using GNU C++, we don't use it for our builds.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#52914 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABBLLY2HQ5TBKPKKRVJIROTTOJ5YLANCNFSM45CVZV3Q>
.
The
runtime/src/coreclr/pal/src/CMakeLists.txt
Line 116 in 279ce14
contains the line:
add_compile_options(-Wa,--divide)
which is triggered for GNU CXX invocations.
Unfortunately, the gnu assembler only accepts the --divide flag for i386 style processor targets.
This means that the runtime does not build out of the box natively on ubuntu arm64 machines.
The text was updated successfully, but these errors were encountered: