linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: billy rose <billyrose@cox-internet.com>
To: Mohamed Aslan <mkernel@linuxmail.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Rewrite Kernel
Date: Sat, 24 Apr 2004 10:10:56 -0500	[thread overview]
Message-ID: <408A8380.4010209@cox-internet.com> (raw)
In-Reply-To: <20040424132402.7EBB923AB1@ws5-3.us4.outblaze.com>

Have you ever written a complete program in assembler? I don't mean a 
small utility, I mean a full application. If you started today 
transcribing the kernel sources for 2.6.x, by the time you finished (not 
including debugging) the standard would no doubt be kernel 4.x or 
beyond. Your assembler version would be vastly outdated, lack features, 
and the methodology would be far behind what will be common at that 
time. - Just my opinion -

Mohamed Aslan wrote:
> No I Could Create Assembly Code Faster Than Gcc
> Gcc 2.95 was good but 3 isn't as 2,it's not my words linus recommended compiling kernel with 2.95
> don't forget something assemblying requires less time than compiling


=====
Billy

"There's some milk in the fridge that's about to go bad...
     And there it goes..." --Bobby



  reply	other threads:[~2004-04-24 15:11 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-24 13:24 Rewrite Kernel Mohamed Aslan
2004-04-24 15:10 ` billy rose [this message]
2004-04-24 15:45 ` David B. Stevens
  -- strict thread matches above, loose matches on Subject: below --
2004-04-07 13:05 Mohamed Aslan
2004-04-07 17:27 ` Robin Rosenberg
2004-04-07 12:54 Mohamed Aslan
2004-04-07 12:57 ` viro
2004-04-07 12:59 ` Wichert Akkerman
2004-04-07 13:08 ` John Bradford
2004-04-07 13:13 ` Sean Neakums
2004-04-07 13:46   ` Dumitru Ciobarcianu
2004-04-07 13:58   ` Richard B. Johnson
2004-04-07 14:36     ` Nick Piggin
2004-04-07 18:58     ` Valdis.Kletnieks
2004-04-07 13:22 ` Zwane Mwaikambo
2004-04-07 13:56 ` Richard B. Johnson
2004-04-07 14:02 ` Erik Mouw
2004-04-07 14:04 ` Trent Lloyd
2004-04-07 14:27 ` Redeeman
2004-04-07 14:55   ` John Bradford
2004-04-07 15:05     ` Lars Marowsky-Bree
2004-04-07 15:17       ` John Bradford
2004-04-07 15:20       ` Emmanuel Fleury
2004-04-07 15:21       ` John Bradford
2004-04-07 17:21       ` Redeeman
2004-04-07 18:47         ` Paulo Marques
2004-04-07 18:12       ` Aaron Smith
2004-04-07 19:58         ` Måns Rullgård
2004-04-07 23:03           ` David B. Stevens
2004-04-08 10:34             ` David Weinehall
2004-04-07 14:57 ` Rob Couto
2004-04-13 14:03   ` Eric W. Biederman
2004-04-07 16:00 ` Brian Pawlowski
2004-04-10 16:59 ` J. Ryan Earl
2004-04-10 17:21   ` Denis Vlasenko
2004-04-10 19:57     ` J. Ryan Earl
2004-04-11 16:58       ` Denis Vlasenko

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=408A8380.4010209@cox-internet.com \
    --to=billyrose@cox-internet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkernel@linuxmail.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;
as well as URLs for NNTP newsgroup(s).