On Fri, 2024-01-05 at 00:26 +0800, Xi Ruoyao wrote: > On Thu, 2024-01-04 at 16:57 +0800, Huacai Chen wrote: > > On Wed, Dec 27, 2023 at 7:06 PM Xi Ruoyao <xry111@xxxxxxxxxxx> wrote: > > > > > > On Wed, 2023-12-27 at 15:03 +0800, WANG Xuerui wrote: > > > > And even though the kernel is built with relaxation disabled, so > > > > far a small number of R_LARCH_RELAX marker relocs are still emitted as > > > > part of la.* pseudo instructions in assembly. > > > > > > I'd consider it a toolchain bug... Is there a reproducer? > > Any updates? Should I apply this patch for loongarch-next? > > Tiezhu told me this should be reproducible with GCC 14 and Binutils-2.42 > development snapshots and defconfig. I'm trying... Unfortunately I still cannot reproduce the issue (with GCC 14.0.0 20231208, binutils 2.41.50.20240104, and defconfig). One possibility is this was already fixed somehow, another is the issue was triggered with a GCC snapshot > 20231208 but I think this very unlikely. Xuerui: can you find the guilty .o file containing R_LARCH_RELAX and/or R_LARCH_ALIGN? Then you can just run "make path/to/something.s" (replace ".o" with ".s") to produce the assembly file and send it to me for further investigation. -- Xi Ruoyao <xry111@xxxxxxxxxxx> School of Aerospace Science and Technology, Xidian University
