https://bugzilla.suse.com/show_bug.cgi?id=1220589 https://bugzilla.suse.com/show_bug.cgi?id=1220589#c5 Richard Biener <rguenther@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jan.hubicka@suse.com --- Comment #5 from Richard Biener <rguenther@suse.com> --- In a local build I see [ 322s] virtual memory exhausted: Cannot allocate memory [3629437.381626] mmap: lto1-wpa (18542): VmData 43446743040 exceed data ulimit 43445233664. Update limits or use boot option ignore_rlimit_data. which is around 40GB. Uncommenting the existing #%%define _lto_cflags %%{nil} makes it work. If you saw it back in February the issue was present in GCC 13 as well. Note that when LTOing a large application a lot of memory can be needed (though 40GB is definitely excessive). Closer investigation might be interesting but shouldn't be priority. I suggest to disable the use of LTO for this package. I'm CCing Honza who's always on the look out for programs blowing up LTO. -- You are receiving this mail because: You are on the CC list for the bug.