From: Joseph Myers <jsm@polyomino.org.uk>
Date: Fri, 24 Sep 2004 20:27:25 +0000 (+0100)
Subject: re PR c/12713 (Document interaction of attribute noreturn and longjmp)
X-Git-Tag: releases/gcc-4.0.0~4616
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=2e9522f436a2312555dc3d6fe81a991219e1cfc8;p=thirdparty%2Fgcc.git

re PR c/12713 (Document interaction of attribute noreturn and longjmp)

	PR c/12713
	* doc/extend.texi: Document interaction of attribute noreturn and
	longjmp.

From-SVN: r88070
---

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 070d85c8254c..52be1847a041 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,9 @@
+2004-09-24  Joseph S. Myers  <jsm@polyomino.org.uk>
+
+	PR c/12713
+	* doc/extend.texi: Document interaction of attribute noreturn and
+	longjmp.
+
 2004-09-24  Richard Henderson  <rth@redhat.com>
 
 	PR rtl-opt/17503
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index a407663ae103..f7f52f186b0f 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -2015,7 +2015,7 @@ uninitialized variables.
 
 The @code{noreturn} keyword does not affect the exceptional path when that
 applies: a @code{noreturn}-marked function may still return to the caller
-by throwing an exception.
+by throwing an exception or calling @code{longjmp}.
 
 Do not assume that registers saved by the calling function are
 restored before calling the @code{noreturn} function.