Open curiousdev opened 10 months ago
Hi @curiousdev, do you have a minimal project or set of commands we could use to reproduce your issue?
So the issue is this:
The .net 7 release and beyond introduced clr-runtime performance optimizations that will reorder read-write memory operations. This re-ordering optimization is apparently incompatible with some emulation frameworks like QEMU and Rosetta.
I'll try to author and small reproduction, however given this is a on-the-fly perf optimization. I'm concerned it will not always be consistent. Especially if I shrink the console app to something very small.
The workaround is to disable this performance optimization. Not ideal.
Here's a link to the conversation thread at the dotnet project.
https://github.com/dotnet/sdk/issues/37169#issuecomment-1830372715
Hi! Any updates on this?
Hi,
I have a similar issue compiling Nginx and OpenSSL and theLink-Time Optimization (LTO) process
.
I tend to think the issue should be raised with Apple / Rosetta?
objs/addon/src/ngx_http_modsecurity_log.o \
objs/addon/src/ngx_http_modsecurity_rewrite.o \
objs/ngx_modules.o \
-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -pie -lpthread -lcrypt -lmodsecurity -lpcre2-8 /home/eng/openssl/.openssl/lib/libssl.a /home/eng/openssl/.openssl/lib/libcrypto.a -lpthread -lz \
-Wl,-E
during IPA pass: static-var
lto1: internal compiler error: in return_token, at opts-common.cc:2135
0x19bb73a internal_error(char const*, ...)
???:0
0x683a32 fancy_abort(char const*, int, char const*)
???:0
0x6ba314 lto_main()
???:0
Please submit a full bug report, with preprocessed source (by using -freport-bug).
Please include the complete backtrace with any bug report.
See <file:///usr/share/doc/gcc-13/README.Bugs> for instructions.
lto-wrapper: fatal error: /usr/bin/cc returned 1 exit status
compilation terminated.
/usr/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status
Description
Describe the bug
Using SDK 8.0 image, run a
RUN dotnet test...
in your dockerfile.To Reproduce
--platform=linux/amd64
in your docker build command.Use Rosetta for x86/amd64 emulation on Apple Silicon
feature is checked in docker engine.Exceptions
Further technical details
Reproduce
Describe the bug
Using SDK 8.0 image, run a
RUN dotnet test...
in your dockerfile.To Reproduce
--platform=linux/amd64
in your docker build command.Use Rosetta for x86/amd64 emulation on Apple Silicon
feature is checked in docker engine.Exceptions
Further technical details
Expected behavior
I should be able to build docker amd64 images with rosetta emulation.
docker version
docker info
Diagnostics ID
BCE2C6D2-92E8-45E9-A41B-8830A46D5474/20231128000102
Additional Info
No response