On Thu, Sep 3, 2020 at 10:49 AM Jakub Jelinek via Gcc-patches <gcc-patches@gcc.gnu.org> wrote: > > On Thu, Sep 03, 2020 at 03:53:35PM +0200, Richard Biener wrote: > > On Thu, 3 Sep 2020, Jakub Jelinek wrote: > > But is that an issue in practice? I usually do not do make -j32 cc1plus > > in a tree that was configured for bootstrap, nor do I use > > --enable-link-serialization in that case. > > Guess most often true, but one could still do it when debugging some > particular problem during bootstrap. > > > Btw, do you plan to keep --enable-link-mutex the way it is? What it > > provides ontop of --enable-link-serialization is that progress > > metering for very long running LTO link stages. Not sure if that > > works for the last LTO link or only when there's some other link > > waiting.
Only when there's another link waiting. > I kept it as is for now. Primarily I didn't want to use > --enable-linux-mutex for the new thing when it has nothing to do with a > mutex. I think with both options together it will just print useless > message that it acquired the lock immediately in each case. Yes. For this to replace --enable-link-mutex for me, I'd want it to work with plain 'make' in the gcc directory, not just at top level. Jason
