I think that's reasonable. I didn't think the performance difference would be as much as it is, since my machine has more cores than that, 12 with 2 threads per core. It actually speeds up the build for people who have enough cores which offset the extra work the linker has to do, but I suspect those people are not the common case. We should still make it possible to use a flag to enable LTO explicitly for a given build, so basically switch the polarity of the default and the override flag.
Gabe On Tue, Apr 20, 2021 at 7:54 AM Jason Lowe-Power via gem5-dev < gem5-dev@gem5.org> wrote: > Hi all, > > It seems the recent change to enable LTO by default is causing more harm > than good. Especially for people debugging, it's a large overhead to wait > 2-5 minutes for gem5 to link in opt mode. I even have encountered this with > a 6 core 3.5+GHz Ryzen. It's quite annoying. We've gotten at least 3 > different posts on gem5-users and gem5-dev complaining about this. I think > this is a strong sign we need to change something. > > I suggest *only enabling* LTO for fast builds and not for any other. > > Thoughts? > > Jason > _______________________________________________ > gem5-dev mailing list -- gem5-dev@gem5.org > To unsubscribe send an email to gem5-dev-le...@gem5.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
_______________________________________________ gem5-dev mailing list -- gem5-dev@gem5.org To unsubscribe send an email to gem5-dev-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
