i386 LIBGCC1

[Golubev I. N.]

Version: 2.95.3
Platform: any i386 target

Why does not gcc set `LIBGCC1=' (empty) in Makefile?  Instead, it
compiles `libgcc1.a', possibly with gcc itself (another compiler may
be not available), consuming unnecessary time and space and causing
people to worry about what happens if we compile it with gcc.  In fact
it appears that gcc never generates references to stuff defined in
`libgcc1.a'.  (This also means that there is no infinite recursion in
`libgcc1.a', so compiling it with gcc is safe.)