From: Paul Eggert Date: Tue, 12 Jul 2011 08:06:42 +0000 (-0700) Subject: obstack: use _Noreturn X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e55e4a839e8bb240b507217fdf04c85879d98300;p=pspp obstack: use _Noreturn * lib/obstack.c (__attribute__): Remove macro. (print_and_abort): Use _Noreturn. --- diff --git a/ChangeLog b/ChangeLog index ae4504d3a9..a8a00cadd5 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,9 @@ 2011-07-12 Paul Eggert + obstack: use _Noreturn + * lib/obstack.c (__attribute__): Remove macro. + (print_and_abort): Use _Noreturn. + c-stack: use _Noreturn * lib/c-stack.c (die, overflow_handler, segv_handler): Use _Noreturn rather than __attribute__((noreturn)). diff --git a/lib/obstack.c b/lib/obstack.c index f31a2e999c..a73d6edb26 100644 --- a/lib/obstack.c +++ b/lib/obstack.c @@ -401,15 +401,7 @@ _obstack_memory_used (struct obstack *h) # include # endif -# ifndef __attribute__ -/* This feature is available in gcc versions 2.5 and later. */ -# if __GNUC__ < 2 || (__GNUC__ == 2 && __GNUC_MINOR__ < 5) -# define __attribute__(Spec) /* empty */ -# endif -# endif - -static void -__attribute__ ((noreturn)) +static _Noreturn void print_and_abort (void) { /* Don't change any of these strings. Yes, it would be possible to add