[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: GCC pure64 for building numeric stuff and GCC

> That doxygen instance has had 90 minutes of the 3000+ processor time so far,
> so I haven't got as far as the torture testing which is done later on in 
> the build.

I've used doxygen for a completely unrelated project and sometimes had
it chew up huge amounts of CPU cycles.  Eventually I tracked it down to
handling of self-referential symbolic links.  (A symlink in a directory
pointing to ".".)  Doxygen would just keep following the symlink and
re-making the same docs over and over, until it hit a maximum depth
and then just stop, but it would take a very very long time to do so.

This was a couple of years ago, and I don't know if it still does this,
but you may want to look and see what it's doing.


Reply to: