https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114978
--- Comment #26 from chenglulu <chenglulu at loongson dot cn> --- (In reply to Tianyang Chou from comment #24) > (In reply to Chen Chen from comment #0) > > Sorry to talk about something unrelated to this bug. I tried running 548 on > CPU loongson 3A6000 with the same compiler version and compiler options as > you but the score is only 8.5, so could you please tell me what am I > missing? I just can't reproduce your performance result. > > The gcc compiler source code is downloaded from the github repo > AOSC-Tracking/gcc(13.2.0), configure it with parameters: > > "--enable-shared --enable-threads=posix --with-system-zlib > --enable-gnu-indirect-function --enable-__cxa_atexit > --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch > --disable-libssp --enable-gnu-unique-object --enable-linker-build-id > --enable-lto --enable-plugin --enable-install-libiberty --disable-multilib > --disable-werror --enable-pie --enable-checking=release > --enable-libstdcxx-dual-abi --with-default-libstdcxx-abi=new > --enable-default-pie --enable-default-ssp --enable-bootstrap > --enable-languages=c,c++,fortran,lto --with-abi=lp64d > --with-arch=loongarch64 --with-tune=la664 --build=loongarch64-aosc-linux-gnu" Setting -mtune=la464 during compilation, I discovered that the score decreases with -mtune=la664.
