🚀 go-pugleaf

   To: help-gcc@prep.ai.mit.edu
   Date: Thu, 26 Nov 1992 01:34:10 GMT
   Organization: Lynx Real-Time Systems, Inc.
   From: bitbug@netcom.com (James Buster)
   Subject: Re: gnu, malloc, and "zero'd" memory
   
   Which version of gcc are you using? I know for sure that g++ 1.42 depends
   upon its malloc'ed memory being zeroed. I had to modify xmalloc() to
   memset() the memory to zeroes before letting the compiler use it. I didn't
   track down exactly where such dependencies were, however. gcc 1.42 (at
   lease on our platform) doesn't seem to need this, but the fact that g++
   needs this casts doubt upon gcc.
   -- 
   				James Buster
   			     bitbug@netcom.com

If you found that changing xmalloc in the way you described changed
the behavior of the compiler, then you have found a bug.  By not
reporting the bug in the proper fashion, you leave yourself and others
open to potential problems in the future.  This is irresponsible.

Without knowledge of what is the exact bug in G++ 1.42, I don't see
why you choose to cast doubt on GCC 1.42.  That does nothing but cast
doubt onto all GNU software--doubt which stems from ignorance, not
inference nor intelligence.

Michael