public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Horst von Brand <vonbrand@inf.utfsm.cl>
To: James Stevenson <james@stev.org>
Cc: Lars Unin <lars_unin@linuxmail.org>, linux-kernel@vger.kernel.org
Subject: Re: What are .s files in arch/i386/boot
Date: Sun, 08 Jun 2003 21:38:19 -0400	[thread overview]
Message-ID: <200306090138.h591cJS11030@pincoya.inf.utfsm.cl> (raw)
In-Reply-To: Your message of "Sat, 07 Jun 2003 21:05:42 +0100." <Pine.LNX.4.44.0306072102580.1776-100000@jlap.stev.org>

Lars Unin <lars_unin@linuxmail.org> said:
> James Stevenson <james@stev.org> said:
> > > > 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,

Those files are smallish routines that can't be sanely written in C, or (in
the case of the bootstrap stuff) are for running on the 8086 your latest
CPU thinks it is when booting. No support for that from gcc.

> > and the spec sheets the .c files were made from? 

If they where around once, they have been long plastered over by patches
that make them useless now.

> 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.

Probably never was. Only way out is as they say: "Use the source, Luke".

You'd better get a book on ia32 (caution, the intel sytax almost all are
written for is truly bletcherous, and does things just different enough
from the AT&T sytax gcc/the kernel uses to make your head spin when trying
to map back and forth). There was an HOWTO on assembly language programming
under Linux, haven't looked at it in a long time. 

> Why do all .c files have to be generated from a spec sheet ?

Now that is a good question... never used one in my life :-)
-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513

  parent reply	other threads:[~2003-06-09  1:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-07 18:54 What are .s files in arch/i386/boot Lars Unin
2003-06-07 20:05 ` James Stevenson
2003-06-07 19:32   ` Sean Neakums
2003-06-07 21:27     ` H. Peter Anvin
2003-06-08 20:04       ` Jos Hulzink
2003-06-08 21:41         ` Shawn
2003-06-09  1:38   ` Horst von Brand [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-09 15:37 Lars Unin
2003-06-09 15:30 Lars Unin
2003-06-09 21:06 ` Steve Brueggeman
2003-06-07 18:36 Lars Unin
2003-06-07 19:50 ` James Stevenson

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=200306090138.h591cJS11030@pincoya.inf.utfsm.cl \
    --to=vonbrand@inf.utfsm.cl \
    --cc=james@stev.org \
    --cc=lars_unin@linuxmail.org \
    --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