alloca is NOT machine dependent; it has exactly the same

effective result.  its use is NOT discouraged -- it is not
common, but when you need it, there is nothing else that will do.

1 files changed, 3 insertions, 7 deletions

diff --git a/src/lib/libc/stdlib/alloca.3 b/src/lib/libc/stdlib/alloca.3
index d7fddb04c2..8cc5c42ff5 100644
--- a/src/lib/libc/stdlib/alloca.3
+++ b/src/lib/libc/stdlib/alloca.3
@@ -25,9 +25,9 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.\"     $OpenBSD: alloca.3,v 1.11 2007/05/31 19:19:31 jmc Exp $
+.\"     $OpenBSD: alloca.3,v 1.12 2012/04/12 15:46:57 deraadt Exp $
 .\"
-.Dd $Mdocdate: May 31 2007 $
+.Dd $Mdocdate: April 12 2012 $
 .Dt ALLOCA 3
 .Os
 .Sh NAME
@@ -54,10 +54,6 @@ function returns a pointer to the beginning of the allocated space.
 .Xr calloc 3 ,
 .Xr malloc 3 ,
 .Xr realloc 3
-.Sh BUGS
-The
-.Fn alloca
-function is machine dependent; its use is discouraged.
 .\" .Sh HISTORY
 .\" The
 .\" .Fn alloca
@@ -66,7 +62,7 @@ function is machine dependent; its use is discouraged.
 .\" The function appeared in 32v, pwb and pwb.2 and in 3bsd 4bsd
 .\" The first man page (or link to a man page that I can find at the
 .\" moment is 4.3...
-.Pp
+.Sh BUGS
 The
 .Fn alloca
 function is slightly unsafe because it cannot ensure that the pointer