"Actual Bugs" in gcc.texi

["Joseph S. Myers" <jsm28 at cam dot ac dot uk>]

gcc.texi lists some "Actual Bugs" that may well have been fixed long ago.  
For each of the following from "Actual Bugs", could anyone who has been in
GCC development for long enough state, if they know, (a) what the problem
was and (b) whether it ever has any relevance to the current GCC
implementation (even if only relevant when running GCC on very old
systems):

@item
The @code{fixincludes} script interacts badly with automounters; if the
directory of system header files is automounted, it tends to be
unmounted while @code{fixincludes} is running.  This would seem to be a
bug in the automounter.  We don't know any good way to work around it.

@item
The @code{fixproto} script will sometimes add prototypes for the
@code{sigsetjmp} and @code{siglongjmp} functions that reference the
@code{jmp_buf} type before that type is defined.  To work around this,
edit the offending file and place the typedef in front of the
prototypes.

@item
When @samp{-pedantic-errors} is specified, GCC will incorrectly give
an error message when a function name is specified in an expression
involving the comma operator.

@item
Loop unrolling doesn't work properly for certain C++ programs.  This is
a bug in the C++ front end.  It sometimes emits incorrect debug info, and
the loop unrolling code is unable to recover from this error.

-- 
Joseph S. Myers
jsm28@cam.ac.uk