Date: Sun, 4 Mar 2001 12:28:51 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: Farooq Mela <fmela0@sm.socccd.cc.ca.us> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: pthread_exit proto Message-ID: <20010304122851.R8663@fw.wintelcom.net> In-Reply-To: <3AA2A268.111D5261@sm.socccd.cc.ca.us>; from fmela0@sm.socccd.cc.ca.us on Sun, Mar 04, 2001 at 12:15:36PM -0800 References: <3AA29546.7D709D6@sm.socccd.cc.ca.us> <20010304115811.Q8663@fw.wintelcom.net> <3AA2A268.111D5261@sm.socccd.cc.ca.us>
next in thread | previous in thread | raw e-mail | index | archive | help
* Farooq Mela <fmela0@sm.socccd.cc.ca.us> [010304 12:14] wrote: > Alfred Perlstein wrote: > > > Is '__dead2' a GNU C thing? or is in any sort of standard? > > See /usr/include/sys/cdefs.h > > __dead2 is defined to __attribute__((__noreturn__)) if a suitable > version of GCC is being used. > > > Generally there's some resistance to putting GNU C specific > > code into the base system, is there a portable way to do this? > > It's not actually gcc-specific code, its more of a hint to the compiler > to not warn about something like, main() "falling off the end" when > there is actually an exit(0); at the end of it. If GCC knows exit() > never returns to its caller it doesnt warn. I understood what it did, I just needed some reference to make sure it was being used in other places as an acceptable option. Thanks, this is what I was expecting you to provide, I'll commit the fix rsn. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010304122851.R8663>