From: Kyle Moffett <mrmacman_g4@mac.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, bunk@stusta.de
Subject: Re: [RFC][MEGAPATCH] Change __ASSEMBLY__ to __ASSEMBLER__ (defined by GCC from 2.95 to current CVS)
Date: Sat, 10 Sep 2005 13:38:15 -0400 [thread overview]
Message-ID: <4FAE9F58-7153-4574-A2C3-A586C9C3CFF1@mac.com> (raw)
In-Reply-To: <20050910014543.1be53260.akpm@osdl.org>
On Sep 10, 2005, at 04:45:43, Andrew Morton wrote:
> This patch seems to have a rather low value-to-noise ratio. Why
> on earth do we want to do this?
When I started trying to split out the userspace<=>kernelspace ABI
headers, I
found a number of things (such as __ASSEMBLY__) that would not operate
properly in userspace. I did a bit of research and noticed that GCC
had a
macro __ASSEMBLER__ defined everywhere we wanted __ASSEMBLY__ to be
defined,
except probably more reliably (IE: We don't need to manually pass
flags to
gas). I figured that if I was going to change the linux-core headers, I
might as well change the rest. If you don't think this is
appropriate, I
would be interested to hear your opinion, although it might have
saved me a
bunch of work if you had brought up your issues before I split the thing
into chunks. :-D
Cheers,
Kyle Moffett
--
There are two ways of constructing a software design. One way is to
make it so
simple that there are obviously no deficiencies. And the other way is
to make
it so complicated that there are no obvious deficiencies. The first
method is
far more difficult.
-- C.A.R. Hoare
next prev parent reply other threads:[~2005-09-10 17:38 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 3:00 [RFC] Splitting out kernel<=>userspace ABI headers Kyle Moffett
2005-09-02 13:41 ` Erik Andersen
2005-09-02 20:51 ` Kyle Moffett
2005-09-02 23:58 ` Erik Andersen
2005-09-03 0:07 ` H. Peter Anvin
2005-09-03 0:30 ` Kyle Moffett
2005-09-03 0:34 ` H. Peter Anvin
2005-09-03 0:50 ` Kyle Moffett
2005-09-03 4:28 ` Erik Andersen
2005-09-03 5:22 ` H. Peter Anvin
2005-09-03 5:50 ` Erik Andersen
2005-09-03 5:53 ` H. Peter Anvin
2005-09-03 6:41 ` Erik Andersen
2005-09-03 15:01 ` H. Peter Anvin
2005-09-03 15:19 ` H. Peter Anvin
2005-09-03 16:55 ` Kyle Moffett
2005-09-05 16:35 ` H. Peter Anvin
2005-09-05 23:28 ` Kyle Moffett
2005-09-06 1:29 ` [RFC][MEGAPATCH] Change __ASSEMBLY__ to __ASSEMBLER__ (defined by GCC from 2.95 to current CVS) Kyle Moffett
2005-09-10 8:40 ` Kyle Moffett
2005-09-10 8:45 ` Andrew Morton
2005-09-10 17:38 ` Kyle Moffett [this message]
2005-09-10 22:04 ` Andrew Morton
2005-09-11 0:33 ` Kyle Moffett
2005-09-11 0:48 ` Andrew Morton
2005-09-11 3:15 ` Kyle Moffett
2005-09-12 8:09 ` Paul Jackson
2005-09-12 15:19 ` H. Peter Anvin
2005-09-12 15:47 ` Paul Jackson
2005-09-12 17:17 ` Sam Ravnborg
2005-09-12 21:14 ` Paul Jackson
2005-09-12 21:39 ` Kyle Moffett
2005-09-12 17:18 ` H. Peter Anvin
2005-09-12 17:51 ` Kyle Moffett
2005-09-12 21:04 ` Paul Jackson
2005-09-14 13:56 ` Bill Davidsen
2005-09-15 21:53 ` Jeremy Fitzhardinge
2005-09-03 5:55 ` [RFC] Splitting out kernel<=>userspace ABI headers Kyle Moffett
2005-09-03 5:57 ` H. Peter Anvin
2005-09-03 6:05 ` Kyle Moffett
2005-09-03 15:36 ` Denis Vlasenko
2005-09-03 16:33 ` Kyle Moffett
2005-09-03 16:51 ` Denis Vlasenko
2005-09-14 13:46 ` Bill Davidsen
2005-09-14 17:01 ` Sam Ravnborg
2005-09-14 17:01 ` H. Peter Anvin
2005-09-14 18:14 ` Kyle Moffett
2005-09-14 19:09 ` linux-os (Dick Johnson)
2005-09-14 19:20 ` H. Peter Anvin
2005-09-14 19:46 ` Kyle Moffett
2005-09-02 21:42 ` Jeff Dike
2005-09-02 21:55 ` H. Peter Anvin
2005-09-02 22:44 ` Kyle Moffett
2005-09-02 23:24 ` H. Peter Anvin
2005-09-02 23:41 ` Kyle Moffett
2005-09-02 23:53 ` 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=4FAE9F58-7153-4574-A2C3-A586C9C3CFF1@mac.com \
--to=mrmacman_g4@mac.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®