From: "J.A. Magallon" <jamagallon@able.es>
To: linux-kernel@vger.kernel.org
Subject: Re: Illegal use of reserved word in system.h
Date: Thu, 19 May 2005 23:10:29 +0000 [thread overview]
Message-ID: <1116544229l.2940l.2l@werewolf.able.es> (raw)
In-Reply-To: <20050519234126.A31656@flint.arm.linux.org.uk> (from rmk+lkml@arm.linux.org.uk on Fri May 20 00:41:26 2005)
On 05.20, Russell King wrote:
> On Thu, May 19, 2005 at 10:30:32PM +0000, J.A. Magallon wrote:
> > Stupid and portable C++ code follows:
> >...
> > # ifdef __linux__
> > strcpy(arch,"x86");
>
> These two appear to be self-contradictory, unless you define "portable"
> to mean "x86 only"... which would be hardly portable.
>
Yup, portable to what I needed to port it ;). Will be refined...
It was just a note about how to get info about ram, cpu, os and so on.
Probably soft (MySQL) that needs to know on what processors is being built
just needs to know on how many is being run to start a thread on each one,
or know about the ram to size its caches...
At build time, cpp -dM /dev/null:
linux-x86:
#define i386 1
#define __i386 1
#define __i386__ 1
#define __tune_pentium__ 1
#define __tune_i586__ 1
darwin-ppc:
#define __ppc__ 1
But the interesting part would be how to know at runtime on what
processor I'm running. Will have to look at x86info...
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandriva Linux release 2006.0 (Cooker) for i586
Linux 2.6.11-jam19 (gcc 4.0.0 (4.0.0-3mdk for Mandriva Linux release 2006.0))
next prev parent reply other threads:[~2005-05-19 23:13 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 19:07 Gilbert, John
2005-05-18 19:53 ` Adrian Bunk
2005-05-19 2:22 ` Kyle Moffett
2005-05-19 11:28 ` Adrian Bunk
2005-05-19 12:19 ` Richard B. Johnson
2005-05-19 12:27 ` Arjan van de Ven
2005-05-19 12:47 ` Maciej W. Rozycki
2005-05-19 13:01 ` Richard B. Johnson
2005-05-19 13:47 ` Steven Rostedt
2005-05-19 14:06 ` Andreas Schwab
2005-05-19 14:15 ` Steven Rostedt
2005-05-19 14:36 ` Richard B. Johnson
2005-05-19 15:19 ` Andreas Schwab
2005-05-19 15:56 ` Steven Rostedt
2005-05-19 16:03 ` Richard B. Johnson
2005-05-19 15:58 ` Richard B. Johnson
2005-05-19 16:22 ` Steven Rostedt
2005-05-19 17:06 ` Richard B. Johnson
2005-05-19 17:36 ` Steven Rostedt
2005-05-19 14:43 ` Maciej W. Rozycki
2005-05-19 14:59 ` Steven Rostedt
2005-05-20 12:23 ` Maciej W. Rozycki
2005-05-19 14:53 ` Arjan van de Ven
2005-05-19 14:58 ` Maciej W. Rozycki
2005-05-19 15:06 ` Arjan van de Ven
2005-05-19 13:56 ` Steven Rostedt
2005-05-19 17:30 ` Ben Greear
2005-05-19 17:36 ` Chris Friesen
2005-05-19 17:40 ` Ben Greear
2005-05-19 22:14 ` Andreas Schwab
2005-05-19 22:30 ` J.A. Magallon
2005-05-19 22:41 ` Russell King
2005-05-19 23:10 ` J.A. Magallon [this message]
2005-05-20 0:01 ` Jeff Woods
2005-05-20 9:27 ` Helge Hafting
2005-05-20 16:47 ` Lee Revell
2005-05-20 16:56 ` Ben Greear
2005-05-18 23:42 ` Andi Kleen
2005-05-18 23:59 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2005-05-20 17:30 Gilbert, John
2005-05-19 20:18 Gilbert, John
2005-05-19 1:51 Gilbert, John
2005-05-18 21:31 Gilbert, John
2005-05-19 17:37 ` Alan Cox
2005-05-20 11:49 ` Dave Airlie
2005-05-20 16:42 ` Alan Cox
2005-05-18 18:23 Gilbert, John
2005-05-18 19:02 ` Adrian Bunk
2005-05-18 19:32 ` Richard B. Johnson
2005-05-19 1:06 ` rdunlap
2005-05-18 0:51 Gilbert, John
2005-05-18 0:57 ` Lee Revell
2005-05-18 1:19 ` Chris Wedgwood
2005-05-18 2:51 ` Steven Rostedt
2005-05-18 4:12 ` Willy Tarreau
2005-05-18 10:06 ` Patrick McFarland
2005-05-18 10:49 ` Coywolf Qi Hunt
2005-05-18 11:12 ` Richard B. Johnson
2005-05-18 21:52 ` Matan Peled
2005-05-19 11:03 ` Richard B. Johnson
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=1116544229l.2940l.2l@werewolf.able.es \
--to=jamagallon@able.es \
--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®