This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: sibcall vs attribute((noreturn))
- From: Geoff Keating <geoffk at geoffk dot org>
- To: Fergus Henderson <fjh at cs dot mu dot OZ dot AU>
- Cc: gcc at gcc dot gnu dot org
- Date: 05 Sep 2002 15:22:19 -0700
- Subject: Re: sibcall vs attribute((noreturn))
- References: <20020903181457.A21606@hg.cs.mu.oz.au><20020905215943.GB13999@ceres.cs.mu.oz.au>
Fergus Henderson <fjh@cs.mu.OZ.AU> writes:
> Is there any reason why the check for no-return functions in
> sibling call can't be just removed?
>
> --- calls.c Fri Aug 30 05:19:59 2002
> +++ calls.c.new Fri Sep 6 07:57:40 2002
> @@ -2454,7 +2454,6 @@
> before the sibcall_epilogue. */
> || fndecl == NULL_TREE
> || (flags & (ECF_RETURNS_TWICE | ECF_LONGJMP))
> - || TREE_THIS_VOLATILE (fndecl)
See
<http://gcc.gnu.org/ml/gcc-patches/2000-10/msg00180.html>
for the reason for this line.
In general, the way to find such things is to use 'cvs annotate' on
the file, in this case calls.c, then use 'cvs log' to see the CVS
commit message for that change (which should be the same as the
ChangeLog entry), then search in gcc-patches for that ChangeLog entry.
--
- Geoffrey Keating <geoffk@geoffk.org>