On Wed, May 6, 2020 at 11:29 PM Uros Bizjak via Gcc <gcc@gcc.gnu.org> wrote: > > On Thu, May 7, 2020 at 8:16 AM Richard Biener > <richard.guent...@gmail.com> wrote: > > > > On May 6, 2020 11:15:08 PM GMT+02:00, Uros Bizjak via Gcc <gcc@gcc.gnu.org> > > wrote: > > >Hello! > > > > > >I wonder, if the build process really needs to build all multilibs in > > >stage-1 bootstrap build. IIRC, stage-1 uses system compiler to build > > >stage-1 gcc, so there is no need for multilibs, apart from library > > >that will be used by stage-1 gcc during compilation of stage-2 > > >compiler. > > > > Correct. Only stage3 needs those. But IIRC we already avoid building them? > > Likewise we avoid building libsanitizer and friends in stage 1/2 unless > > ubsan bootstrap is enabled. > > Looking at: > > [gcc-build]$ ls stage1-x86_64-pc-linux-gnu/32/ > libgcc libgomp libstdc++-v3 > > it seems that 32bit multilibs are built anyway, also in stage2: > > [gcc-build]$ ls prev-x86_64-pc-linux-gnu/32/ > libgcc libgomp libstdc++-v3
How does the build infrastructure know which multi-lib is being used to compile GCC here? I can think of an example where the normal multi-libs are ilp32/lp64 but GCC defaults to ilp32. So it is hard to tell that from the normal build infastructure really. Thanks, Andrew Pinski > > Uros.
