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>
Subject: Re: [PATCH] MIPS: Transform old-style macros to newer "__noreturn" standard.
Date: Sat, 26 May 2007 16:29:05 -0700 [thread overview]
Message-ID: <4658C2C1.7060607@zytor.com> (raw)
In-Reply-To: <4658781D.5070108@zytor.com>
H. Peter Anvin wrote:
> Robert P. J. Day wrote:
>> It does not make sense for a noreturn function to have a return type
>> other than void.
>> ^^^^^ ^^^^ ^^^^
>> ===============================================================
>>
>> so I'm just going to stick with the pattern that's been used so far.
>> i realize it offends your sense of syntactic sensibility, but it's
>> just not worth treating that one attribute so differently from the
>> rest of them.
>>
>
> Why are you so hung up over the fact that the *implementation* of this
> is an attribute? You're totally confusing interface and implementation.
>
Perhaps I should clarify this:
The whole reason to abstract this as a macro *at all* is to take it away
from the specific implementation in gcc. Thus, implementing an inferior
interface just because gcc happens to do it that way is actively
counterproductive.
-hpa
prev parent reply other threads:[~2007-05-26 23:29 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
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 [this message]
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=4658C2C1.7060607@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox