🚀 go-pugleaf

This problem has been fixed.  The next version of gcc should work
better.  Here are the patches if you would like to have it working
before then.

--------------
Doing diffs in cp-typeck.c.~1~:
*** cp-typeck.c.~1~	Thu Apr  2 13:38:20 1992
--- cp-typeck.c	Thu Apr  9 01:57:08 1992
***************
*** 1884,1891 ****
  	  TREE_USED (function) = 1;
  	}
  
!       function = build1 (ADDR_EXPR, build_pointer_type (TREE_TYPE (function)),
! 			 function);
      }
    else
      {
--- 1884,1893 ----
  	  TREE_USED (function) = 1;
  	}
  
!       fntype = build_type_variant (TREE_TYPE (function),
! 				   TREE_READONLY (function),
! 				   TREE_THIS_VOLATILE (function));
!       function = build1 (ADDR_EXPR, build_pointer_type (fntype), function);
      }
    else
      {


> Date: Mon, 6 Apr 92 11:41:47 EDT
> From: purtill%idacrd@uunet.uu.net (Mark Purtill)
> Message-Id: <9204061541.AA24193@>
> To: bug-gcc@prep.ai.mit.edu
> Subject: Bug report
> Resent-From: bug-gcc-request@prep.ai.mit.edu

> On a Sparcstation 2 (which is not connected to the outside;  I'm
> typing this in from a printed transcript, so I might err).
> % gcc -v
> Reading specs from /usr/local/lib/gcc-lib/sparc-sun-sunos4.1/2.1/specs
> gcc version 2.1
> % more /etc/motd
> SunOS Release 4.1.1 (CARS_2) #3: Thu Aug 15 10:35:49 EDT 1991
> % cat >bugs.C
> volatile void abort() ;
> volatile void oink() ;
>     void
> oink() {
>     abort() ;
>     }
> ^D
> % gcc -c bugs.C
> bugs.C: In function `void  oink ()':
> bugs.C:6: warning: `volatile' function does return
> %
> 	Of course, the warning is erroneous, since oink calls abort,
> which doesn't return, so `oink' doesn't either.  This problem did not
> occur on g++ 1.37.1 (I think), which we had here until recently.