From bc0ff407ce8e111f5867f6f49030a2aa6bdb535e Mon Sep 17 00:00:00 2001 From: Hans-Peter Nilsson Date: Sun, 12 Oct 2003 16:08:10 +0000 Subject: [PATCH] extend.texi (Function Attributes): Mention the exceptional path for noreturn-marked functions. * doc/extend.texi (Function Attributes): Mention the exceptional path for noreturn-marked functions. From-SVN: r72401 --- gcc/ChangeLog | 5 +++++ gcc/doc/extend.texi | 4 ++++ 2 files changed, 9 insertions(+) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 47f03e5871c..5f64e151d85 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,8 @@ +2003-10-12 Hans-Peter Nilsson + + * doc/extend.texi (Function Attributes): Mention the exceptional + path for noreturn-marked functions. + 2003-10-12 Jan Hubicka * cgraphunit.c (cgraph_decide_inlining): Fix uninitialized variable diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index d2f417da782..d24a725555a 100644 --- a/gcc/doc/extend.texi +++ b/gcc/doc/extend.texi @@ -2020,6 +2020,10 @@ would happen if @code{fatal} ever did return. This makes slightly better code. More importantly, it helps avoid spurious warnings of 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. + Do not assume that registers saved by the calling function are restored before calling the @code{noreturn} function.