Jaron Kent-Dobias <ja...@kent-dobias.com> wrote:

> On Monday, 3 April 2023 at 08:58 (+0000), u...@net9.ga wrote:
> >I haven't tried all the 6.2.*. Only some of the earliest, and some of 
> >the latest. v6.2.9, at this time. I could build the earliest v6.1.*. 
> >And also v6.1.12. Which is arch latest v6.1.*, doesn't it? I got what 
> >looks to me a similar issue with v6.1.7, if I remember correctly. As of 
> >v6.2.7 and v6.2.9, I get:
> >
> >    $ cat -n linux-6.2.9.arch1-1-x86_64-build.log | tail
> >     19288     AR      arch/x86/video/built-in.a
> >     19289     AR      built-in.a
> >     19290     AR      vmlinux.a
> >     19291     LD      vmlinux.o
> >     19292   vmlinux.o: warning: objtool: hyperv_init+0x42f: unreachable 
> > instruction
> >     19293   make[1]: *** Deleting file 'vmlinux.o'
> >     19294   make[1]: *** [scripts/Makefile.vmlinux_o:61: vmlinux.o] 
> > Interrupt
> >     19295   make: *** [Makefile:1245: vmlinux_o] Interrupt
> >     19296   
> >     19297   ==> ERROR: Aborted by user! Exiting...
> >
> >After it stalled for a long time at line #19291, or at line #19292, I 
> >interrupted it, ^c, manually. I forgot to look at the resource usage 
> >before interrupting v6.2.9 build. For some of the prevoius versions it 
> >happend, I saw the LD proccess consumed almost all of the machine free 
> >memory. And also a lot of swap. Which happend right at the LD 
> >operation, not before. It is only a desktop, Only 4G RAM.
> 
> Have you modified the config at all? If you have, seeing the modified 
> config would be helpful.

I have tried v6.2.9 with default arch config.
In the past, I used a trimmed down configuration. And got a similar issue 
starting with some of v6.1.* arch source. With earlier v6.1.*, and before, 
I always could built arch linux source with my trimmed down configuration. 
In fact, I was surprised I could built 6.1.12. With my trimmed down 
configuration, if I remember correctly.

> 
> A very sure way to use a lot of memory (well over 4G) at linking is if 
> you have enabled LTO in the kernel config. Perhaps this is the culprit?
> 

Default arch config. No LTO, as far as I can tell.

    $ grep LTO config
    CONFIG_ARCH_SUPPORTS_LTO_CLANG=y
    CONFIG_ARCH_SUPPORTS_LTO_CLANG_THIN=y
    CONFIG_LTO_NONE=y
    CONFIG_HID_WALTOP=m

> Jaron

--
u34

Reply via email to