This is the mail archive of the
mailing list for the GCC project.
Re: PR tree-opt/19484: noreturn vs. function pointer propagation
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: Diego Novillo <dnovillo at redhat dot com>
- Cc: gcc-patches at gcc dot gnu dot org, Richard Sandiford <rsandifo at redhat dot com>
- Date: Sat, 22 Jan 2005 11:08:24 -0500
- Subject: Re: PR tree-opt/19484: noreturn vs. function pointer propagation
- References: <firstname.lastname@example.org> <41F27889.email@example.com>
On Jan 22, 2005, at 11:00 AM, Diego Novillo wrote:
You need to remove all edges out of this block, actually. The block
may have had EH edges.
Noreturn functions are allowed to not return via a throwing an
Reading the documentation says that explicitly:
"The noreturn keyword does not affect the exceptional path when that
applies: a noreturn-marked function may still return to the caller by
throwing an exception."