dwarf-2 problem on cc1

[Jeffrey A Law]

  In message < 19990613001932.A23053@rjlhome.sco.com >you write:
  > Ben, how would you and Jeff about using a post 2.13 autoconf for 2.95?
My only worry is that by not currently being in the tree it isn't being
tested.  Switching the mainline tree to a newer version seems like a reasonable
thing though.  If these older versions of autoconf are causing problems, then
adding a AC_PREREQ to all the configure.in files seems like a good idea too.

  > I was really suprised that the third-stage cc1 contained references to
  > memset and memcpy but apparently there was a use somewhere that just
  > couldn't be inlined so we get into the weirdness of mixing native and
  > gcc objects.
Not a total suprise.  Sometimes gcc will determine that the system provided
mem* str* functions are better than inlining.  For example unaligned with
a large (or unknown) size will often kick to the library version instead of
inlining.

What I do not get is why an autoconf bug is causing a dwarf2 code generation
problem.  That seems awful weird.
jeff