This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: warnings patch for top level gcc directory
- To: egcs-patches at cygnus dot com, rth at cygnus dot com
- Subject: Re: warnings patch for top level gcc directory
- From: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Date: Mon, 19 Oct 1998 10:05:02 -0400 (EDT)
> From: Richard Henderson <rth@cygnus.com>
>
> On Sat, Oct 17, 1998 at 11:14:39AM -0400, Kaveh R. Ghazi wrote:
> > Also, I'm doing the
> > libgcc2.a reversion of noreturn because on OSF4 it (falsely IMHO) claims
> > it returns. Don't know why, but I wanted to play it safe.
>
> The claim that it returns is correct. It doesn't return to where it
> was called from, but it does return. Which means the full epilogue
> code _must_ be generated, which would not happen for a real noreturn
> function.
> r~
Okay, but why then does it *only* claim to return on OSF4? Is
that a fluke / bug in the flow code again?
Hmm, if a function calls longjmp() as its last statement, is
it safe to mark as `noreturn' or do we need to generate the full
epilogue there too?
--Kaveh
--
Kaveh R. Ghazi Engagement Manager / Project Services
ghazi@caip.rutgers.edu Icon CMT Corp.