https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85716
--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> --- More from #gcc on freenode: <TemptorSent> dmalcolm - A flag to have gcc spit out what it's doing on long-runnign compiles would be immensely useful! I'm still trying to debug compile runs with checking=all running incredibly slowly, and haven't been able to bifurcate a particular test yet. <TemptorSent> ...perhaps a flag to echo the checking in progress and statistics as it runs? [...reference to this PR...] <TemptorSent> I think the timestamp logging would be great, as well as a marker for transitions between compilation phases. <dmalcolm> TemptorSent: OK if I paste this IRC log into that BZ, or do you want to add a comment to it? <dmalcolm> also, do you need absolute timestamps, or is relative-to-start-of-cc1 ok? <dmalcolm> (I was just going to use relative to start of cc1) <dmalcolm> (or cc1plus, whatever) <TemptorSent> Relative should be fine, although tagging the start time with the absolute time may be useful.
