This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: c/3764: Gcc incorrectly complains that a noreturn function returns

To: Phil Edwards <pedwards at disaster dot jaj dot com>
Subject: Re: c/3764: Gcc incorrectly complains that a noreturn function returns
From: Richard Henderson <rth at redhat dot com>
Date: Mon, 23 Jul 2001 03:40:47 -0700
Cc: Erik Mouw <J dot A dot K dot Mouw at ITS dot TUDelft dot NL>, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org
References: <20010723045818.7148.qmail@sourceware.cygnus.com> <20010723101707.E17535@arthur.ubicom.tudelft.nl> <20010723013553.A14153@redhat.com> <20010723052352.A15554@disaster.jaj.com>

On Mon, Jul 23, 2001 at 05:23:52AM -0400, Phil Edwards wrote:
> So if the code in question concluded with
> 
>     ... some weird memory assignment ...
> 
>     exit(1);  /* NOTREACHED */
>    }
> 
> then it would recognize that this function isn't coming back?

Or, more simply,

	while (1);


r~

References:
- Re: c/3764: Gcc incorrectly complains that a noreturn function returns
  - From: rth
- Re: c/3764: Gcc incorrectly complains that a noreturn function returns
  - From: Erik Mouw
- Re: c/3764: Gcc incorrectly complains that a noreturn function returns
  - From: Richard Henderson
- Re: c/3764: Gcc incorrectly complains that a noreturn function returns
  - From: Phil Edwards

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]