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: Richard Henderson <rth at cygnus dot com>
- Subject: Re: sibling/tail call opts vs sjlj EH
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Wed, 29 Mar 2000 11:37:44 -0700
- cc: gcc-patches at gcc dot gnu dot org
- Reply-To: law at cygnus dot com
In message <20000329103415.C1346@cygnus.com>you write:
> 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? ;-)
Stupidity leak. You're absolutely correct. I'll make the change locally,
perform the required testing and check it in when the testing completes.
Thanks for pointing this out -- I guess I look a whole lot like a pointy
hair today :-)
jeff