All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH] MIPS: Transform old-style macros to newer "__noreturn" standard.
Date: Fri, 25 May 2007 12:38:11 -0700	[thread overview]
Message-ID: <46573B23.1090700@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0705251458440.13906@localhost.localdomain>

Robert P. J. Day wrote:
>
> 
>   f() __attribute__((noreturn)) ;
> 
> you get:
> 
>   warning: data definition has no type or storage class
> 
> but gcc doesn't complain if you declare it thusly:
> 
>   __attribute__((noreturn)) f() ;
> 
> that strikes me as a flaw in gcc, no?
> 

Doesn't matter.  gcc accepts "void __attribute__((noreturn)) f();", and
thus, one can define:

#define __noreturn void __attribute__((noreturn))

... and declare functions as:

__noreturn f();

... which is the syntactially sane way of doing it.

	-hpa

  reply	other threads:[~2007-05-25 19:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-25 18:32 [PATCH] MIPS: Transform old-style macros to newer "__noreturn" standard Robert P. J. Day
2007-05-25 18:40 ` H. Peter Anvin
2007-05-25 19:04   ` Robert P. J. Day
2007-05-25 19:38     ` H. Peter Anvin [this message]
2007-05-25 21:10       ` Robert P. J. Day
2007-05-25 21:43         ` H. Peter Anvin
2007-05-25 22:16           ` Satyam Sharma
2007-05-25 22:25             ` H. Peter Anvin
2007-05-25 22:35               ` Satyam Sharma
2007-05-25 22:46                 ` H. Peter Anvin
2007-05-25 22:56                   ` Satyam Sharma
2007-05-26 13:33       ` Robert P. J. Day
2007-05-26 18:10         ` H. Peter Anvin
2007-05-26 23:29           ` H. Peter Anvin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46573B23.1090700@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=rpjday@mindspring.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.