From: Randy Dunlap <randy.dunlap@oracle.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: akpm <akpm@osdl.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] math-emu/setcc: avoid gcc extension
Date: Sun, 7 Jan 2007 10:45:55 -0800 [thread overview]
Message-ID: <20070107104555.015aa79f.randy.dunlap@oracle.com> (raw)
In-Reply-To: <33e707f92df6b89a1c22f337f230cf32@kernel.crashing.org>
On Sun, 7 Jan 2007 14:27:32 +0100 Segher Boessenkool wrote:
> closing brace on the "while" line, please.
---
From: Randy Dunlap <randy.dunlap@oracle.com>
setcc() in math-emu is written as a gcc extension statement expression
macro that returns a value. However, it's not used that way and it's
not needed like that, so just make it a do-while non-extension macro
so that we don't use an extension when it's not needed.
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
arch/i386/math-emu/status_w.h | 5 +++--
---
arch/i386/math-emu/status_w.h | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--- linux-2620-rc2.orig/arch/i386/math-emu/status_w.h
+++ linux-2620-rc2/arch/i386/math-emu/status_w.h
@@ -48,9 +48,10 @@
#define status_word() \
((partial_status & ~SW_Top & 0xffff) | ((top << SW_Top_Shift) & SW_Top))
-#define setcc(cc) ({ \
+#define setcc(cc) do { \
partial_status &= ~(SW_C0|SW_C1|SW_C2|SW_C3); \
- partial_status |= (cc) & (SW_C0|SW_C1|SW_C2|SW_C3); })
+ partial_status |= (cc) & (SW_C0|SW_C1|SW_C2|SW_C3); \
+ } while (0)
#ifdef PECULIAR_486
/* Default, this conveys no information, but an 80486 does it. */
next prev parent reply other threads:[~2007-01-07 18:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-07 6:19 [PATCH] math-emu/setcc: avoid gcc extension Randy Dunlap
2007-01-07 13:27 ` Segher Boessenkool
2007-01-07 18:45 ` Randy Dunlap [this message]
2007-01-07 19:12 ` Segher Boessenkool
2007-01-07 19:19 ` Randy Dunlap
2007-01-07 19:22 ` Robert P. J. Day
2007-01-07 19:29 ` Segher Boessenkool
2007-01-07 19:30 ` Randy Dunlap
2007-01-07 19:58 ` Christoph Hellwig
2007-01-07 21:07 ` Randy Dunlap
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=20070107104555.015aa79f.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=segher@kernel.crashing.org \
/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.