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 11:19:00 -0800 [thread overview]
Message-ID: <20070107111900.9d434162.randy.dunlap@oracle.com> (raw)
In-Reply-To: <974f8eb0d5984af6726a130082453916@kernel.crashing.org>
On Sun, 7 Jan 2007 20:12:42 +0100 Segher Boessenkool wrote:
> There's an extra tab in that last line. Could you also
> please fix the indenting (use a tab, not spaces) -- I know
> it was there originally, but since there are only a few
> lines in that file like that... :-)
how's this one?
---
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 | 7 ++++---
1 file changed, 4 insertions(+), 3 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) ({ \
- partial_status &= ~(SW_C0|SW_C1|SW_C2|SW_C3); \
- partial_status |= (cc) & (SW_C0|SW_C1|SW_C2|SW_C3); })
+#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); \
+} while (0)
#ifdef PECULIAR_486
/* Default, this conveys no information, but an 80486 does it. */
next prev parent reply other threads:[~2007-01-07 19:19 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
2007-01-07 19:12 ` Segher Boessenkool
2007-01-07 19:19 ` Randy Dunlap [this message]
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=20070107111900.9d434162.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox