From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: What are .s files in arch/i386/boot
Date: 7 Jun 2003 14:27:34 -0700 [thread overview]
Message-ID: <bbtlc6$qtd$1@cesium.transmeta.com> (raw)
In-Reply-To: 6un0gty981.fsf@zork.zork.net
Followup to: <6un0gty981.fsf@zork.zork.net>
By author: Sean Neakums <sneakums@zork.net>
In newsgroup: linux.dev.kernel
>
> James Stevenson <james@stev.org> writes:
>
> >> > > 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.
>
> If there were ever C files to begin with. It's not unheard-of for
> people to write assembler code from scratch.
>
The ones in the Linux kernel were all written from scratch.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
next prev parent reply other threads:[~2003-06-07 21:14 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 [this message]
2003-06-08 20:04 ` Jos Hulzink
2003-06-08 21:41 ` Shawn
2003-06-09 1:38 ` Horst von Brand
-- 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='bbtlc6$qtd$1@cesium.transmeta.com' \
--to=hpa@zytor.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