public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: Herbert Poetzl <herbert@13thfloor.at>
Cc: linux-kernel@vger.kernel.org, Jim Wilson <wilson@specifixinc.com>,
	Judith Lebzelter <judith@osdl.org>, cliff white <cliffw@osdl.org>,
	"Timothy D. Witham" <wookie@osdl.org>
Subject: Re: Kernel Cross Compiling [update]
Date: Sat, 21 Feb 2004 22:02:29 -0800	[thread overview]
Message-ID: <403845F5.5030101@kegel.com> (raw)
In-Reply-To: <20040222035350.GB31813@MAIL.13thfloor.at>

Herbert Poetzl wrote:
>    the GCC testsuite contains 2854 files in the relevant 
>    subdirs consistency.vlad, gcc.c-torture, gcc.dg, and
>    gcc.misc-tests.
>     
>    after removing the non relevant tests (file matching 
>    egrep '#include|float|double') 1799 C files remain.
>      
>    the result of the tests and comparison[4] shows that
>    both compilers produce the same code, except for one
>    little difference[5], which I'm unable to explain ...  
 > [5]  http://vserver.13thfloor.at/Stuff/Cross/Comparison/TEST-alpha.diff
 > ...

>    my conclusion so far is that my approach should be
>    sufficient for Kernel Cross Compiling.

Perhaps, but it's harder to repeat than using my crosstool script;
you said you had to munge a bunch of header files, but with
crosstool no special munging is required.  AFAIR you haven't
posted your header-munging procedure.

It's vaguely possible that your header munging was wrong, which
caused that one diff on alpha.

Say, could you compare compiling the kernel with the two
toolchains, and see if there are any differences?
- Dan

-- 
US citizens: if you're considering voting for Bush, look at these first:
http://www.misleader.org/
http://www.cbc.ca/news/background/arar/
http://www.house.gov/reform/min/politicsandscience/

  reply	other threads:[~2004-02-22  6:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-22  3:53 Kernel Cross Compiling [update] Herbert Poetzl
2004-02-22  6:02 ` Dan Kegel [this message]
2004-02-22 15:42   ` Herbert Poetzl
2004-02-22  8:43 ` Geert Uytterhoeven
2004-02-22  9:07 ` Russell King
2004-02-22 15:09   ` Herbert Poetzl
2004-02-22 12:45 ` Dr. David Alan Gilbert
2004-02-22 15:22   ` Herbert Poetzl
2004-02-22 15:52 ` Paul Mundt
2004-02-22 17:07   ` Herbert Poetzl
2004-02-22 17:23     ` Paul Mundt
2004-02-23 13:28       ` Richard Curnow
2004-02-23 14:41         ` Herbert Poetzl
2004-02-26 13:02           ` Richard Curnow
2004-02-23 19:42 ` Jim Wilson
2004-02-23 20:32   ` Herbert Poetzl
2004-02-24  1:49     ` Dan Kegel
2004-02-24  8:53       ` Herbert Poetzl
  -- strict thread matches above, loose matches on Subject: below --
2004-02-22 16:36 Arnd Bergmann

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=403845F5.5030101@kegel.com \
    --to=dank@kegel.com \
    --cc=cliffw@osdl.org \
    --cc=herbert@13thfloor.at \
    --cc=judith@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wilson@specifixinc.com \
    --cc=wookie@osdl.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