This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/85716] No easy way for end-user to tell what GCC is doing when compilation is slow
- From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 09 May 2018 18:24:04 +0000
- Subject: [Bug other/85716] No easy way for end-user to tell what GCC is doing when compilation is slow
- Auto-submitted: auto-generated
- References: <bug-85716-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85716
--- Comment #4 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
<TemptorSent> Also, I'm not sure if it's available, but if we could print the
parent process and commandline passed at the beginning of an error report, and
tag the output for the error report with the PIDs, it would make tracking
things in parallel builds much easier.