sucessful make profiledboostrap of gcc-4.6-20110115 on i686-{any}-linux
Hi.
I would like to tell that profiledboostrap does compile on 32 bit intel for
current 4.6 tree snapshot
and therefore 4.6 branch is not affected by this problem -
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43085
evironment:
AFLAGS="-O2 -march=pentium4 -msse2"
export CXXFLAGS_FOR_BUILD=${AFLAGS}
export CFLAGS_FOR_BUILD=${AFLAGS}
export BOOT_CFLAGS=${AFLAGS}
export LIBCFLAGS=${AFLAGS}
export LIBCXXFLAGS=${AFLAGS}
export CXXFLAGS_FOR_TARGET=${AFLAGS}
export CFLAGS_FOR_TARGET=${AFLAGS}
export CFLAGS=${AFLAGS}
export CXXFLAGS=${CFLAGS}
export JCFLAGS="-O2"
export FCFLAGS="-O2"
configure arguments:
--host=i686-pc-linux --build=i686-pc-linux --disable-nls --with-cpu=core2
--with-arch=pentium4 --enable-languages=c,c++,fortran,go
--disable-stage1-checking --enable-checking=release --enable-threads
--enable-tls --enable-lto --with-fpmath=sse
~ cheers.
Re: Number of ALU in la464.md
You are right, I just added it before, but I didn't see the performance
improvement,
so I didn't change this place.
在 2022/9/25 下午7:28, Xi Ruoyao 写道:
Hi,
According to the schematic
(https://loongson.github.io/LoongArch-Documentation/Loongson-3A5000-usermanual-EN.html#la464-processor-core,
Figure 5) we have 4 ALUs in LA464, but in la464.md we only define
la464_alu1 and la464_alu2.
Should we add la464_alu{3,4} as well, or am I missing something here?
