This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: sibling/tail call opts vs sjlj EH
- To: Jeffrey A Law <law at cygnus dot com>
- Subject: Re: sibling/tail call opts vs sjlj EH
- From: Richard Henderson <rth at cygnus dot com>
- Date: Wed, 29 Mar 2000 10:34:15 -0800
- Cc: gcc-patches at gcc dot gnu dot org
- References: <4935.954351919@upchuck>
On Wed, Mar 29, 2000 at 10:45:19AM -0700, Jeffrey A Law wrote:
> stmt_loop_nest_empty ()
> {
> ! /* cfun->stmt can be NULL if we are building a call to get the
> ! EH context for a setjmp/longjmp EH target and the current
> ! function was a deferred inline function. */
> ! return (cfun->stmt != NULL && loop_stack == NULL);
It probably doesn't make any difference in The Overall, but
shouldn't we return true if stmt is null? I.e.
cfun->stmt == NULL || loop_stack == NULL
After all, there isn't a loop_stack, so it must be empty, right? ;-)
r~