Thank you for the BZ link. Actually my problem was configuring GCC build with --with-build-config=bootstrap-lto and --enable-lto. I'm researching compiler theory (reading the Dragon book now) and I would like to contribute to our lovely compiler(s), specially gfortran.
On Mon, Sep 16, 2024 at 10:01 PM David Malcolm <dmalc...@redhat.com> wrote: > On Sun, 2024-09-15 at 15:20 +0330, Ghorban M. Tavakoly via Gcc wrote: > > Hi > > > > On Sun, Sep 15, 2024 at 11:59 AM Jan Hubicka <hubi...@ucw.cz> wrote: > > > > > > On Sat, Sep 14, 2024 at 1:17 PM Ghorban M. Tavakoly via Gcc > > > > <gcc@gcc.gnu.org> wrote: > > > > > > > > > > > > Is there any change to have some LTO progress indicator > > > > > > > information > > > in > > > > > upstream GCC output? Do I need to report a bug? > > > > > Is there any chance ... (sorry for typo) > > > > > > > > You can add -Q to the command line which makes GCC output some > > > > sort > > > > of progress indication. Otherwise no - we do not really know how > > > > long a > > > > compile will take so a true progress indicator isn't possible. > > > > > > For ltrans we do make estimate used by partitioning, so for large > > > projects that consits of many functions we may be able to do some > > > sort > > > of progress info on ltrans stage. > > > > > > But indeed, when waiting for large copmiles, I use -Q to make > > > myself > > > entertained :) > > > > > Actually my script on the first email creates a progressbar from > > /tmp/*ltrans* files. > > > FWIW there's an RFE in our bugzilla here: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85716 > that captures some ideas about progress bars and "why is the compiler > taking so long?" (I just added some more) > > Dave > >
