mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kyle Moffett <mrmacman_g4@mac.com>
To: LKML Kernel <linux-kernel@vger.kernel.org>
Subject: Kernel ABI headers step #1: Gathering information
Date: Tue, 13 Sep 2005 02:11:28 -0400	[thread overview]
Message-ID: <6789B04A-198A-4C08-9F95-BFDBCD2C0660@mac.com> (raw)

As part of the kernel ABI headers project, I need to gather  
information on what
GCC provides on a variety of architectures and configurations.  I am  
looking for
people with a variety of architectures and distributions to run the  
script below
and (privately, please, no need to flood the list!) email me the  
output.  I'm
only interested in archs supported by linux, obviously :-D.  This  
should help me
to see if there are any global CPP features that can be relied upon  
across the
whole spectrum.  If you have any especially obtuse GCC/platform  
combination, I
would really appreciate it if you could do this, as otherwise I'm  
unlikely to
be able to locate all of said GCC combinations.  (The reason I get  
the kernel
version is so I'm able to tie GCC archs to kernel archs).  Once I've  
got a
decent database of per-arch features/macros/etc, I'll try to post it  
online
somewhere for all to access.  Thanks for all your help!

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



#! /bin/sh

echo "Linux kernel version:"
uname -a
echo
echo
echo "GCC version:"
gcc -v
echo
echo
echo "GCC predefined macros:"
echo | gcc -E - -dM | sort



             reply	other threads:[~2005-09-13  6:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13  6:11 Kyle Moffett [this message]
2005-09-13  6:40 ` Kyle Moffett

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=6789B04A-198A-4C08-9F95-BFDBCD2C0660@mac.com \
    --to=mrmacman_g4@mac.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®