On 5/24/2021 4:43 PM, Gabe Black wrote: > I don't think LTO strips debug symbols... But yes, LTO does significantly > increase link time if your machine doesn't have lots of cores to parallelize > the link. It slows it down in general, but with gcc you can parallelize the > link with LTO where you can't without LTO for some reason, and that > outweighs the other overhead if you have enough cores to throw at it.
Earlier editions of Gem5 build gem5.fast.unstripped using LTO. > Especially when running in a virtual machine, you might just be running out > of memory. LTO will use more ram, and if you run out things will fail in > potentially strange ways. While I give the machine a fair amount of RAM, I will try giving it more. > It sounds like you have a workaround for now so this may be a moot point, > but in general, when you report compiler errors (or errors in general) it's > very helpful to provide the error output instead of just describing the > errors. That provides a lot of helpful detail which can make diagnosing the > problem much easier. Well, the workaround is not to optimize, though I have also seen builds fail that way too. (I am going all the way back to deleting the the whole build/ hierarchy and seeing if that avoids the problems.) Thanks for your help. If it continues to break, I will post the entire log of the build. Regards - Eliot _______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
