public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Lars Unin" <lars_unin@linuxmail.org>
To: james@stev.org, torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: What are .s files in arch/i386/boot [I think thats Linus, er.. hey Linus!]
Date: Sun, 08 Jun 2003 03:19:03 +0800	[thread overview]
Message-ID: <20030607191903.32603.qmail@linuxmail.org> (raw)


----- Original Message -----
From: James Stevenson <james@stev.org>
Date: Sat, 7 Jun 2003 21:05:42 +0100 (BST)
To: Lars Unin <lars_unin@linuxmail.org>
Subject: Re: What are .s files in arch/i386/boot

> 
> > > > What are .s files in arch/i386/boot, are they c sources of some sort?
> > > > Where can I find the specifications documents they were made from? 
> > > 
> > > There are not c files.
> > > They are assembler files
> > > 
> > > Try running gcc on a c file with the -S option
> > > it will generate the same then you can tweak the
> > > assembler produced to make it faster.
> > > 
> > Where can I find the .c files they were made from,
> > and the spec sheets the .c files were made from? 
> 
> You would have to find the original author of the person
> who tweaks the assembler in the .s file chances are the .c
> file is long gone though.
> 
> Why do all .c files have to be generated from a spec sheet ?
I think Linus is the author, and he would have got the information
from somewhere, we just have to ask him where he got it from...

Err... Linus? Are you there?
Linus?
-- 
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr

Powered by Outblaze

                 reply	other threads:[~2003-06-07 19:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030607191903.32603.qmail@linuxmail.org \
    --to=lars_unin@linuxmail.org \
    --cc=james@stev.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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