cvs commit: src/sys/boot/i386/boot0 Makefile boot0.s
boot0_512.s boot0sio.s
Ruslan Ermilov
ru at FreeBSD.org
Wed Apr 28 00:29:10 PDT 2004
On Tue, Apr 27, 2004 at 02:37:10PM -0700, Julian Elischer wrote:
> On Tue, 27 Apr 2004, Poul-Henning Kamp wrote:
[...]
> > If we have such a convention: yes. I wasn't aware of it.
> >
> It has been the convention since before I made the first bootblocks.
> The Makefiles know how to produce a .s from a .S using the C
> preprocessor.
> (or did I get this the other way around :-)
>
It's not a "convention" per se. Instead, it gives the correct
hint to the compiler. From gcc.info:
: `FILE.s'
: Assembler code.
:
: `FILE.S'
: Assembler code which must be preprocessed.
:
: `-x c'
: `-x c++'
: `-x objective-c'
: `-x assembler-with-cpp'
: Specify the source language: C, C++, Objective-C, or assembly.
: This has nothing to do with standards conformance or extensions;
: it merely selects which base syntax to expect. If you give none
: of these options, cpp will deduce the language from the extension
: of the source file: `.c', `.cc', `.m', or `.S'. Some other common
: extensions for C++ and assembly are also recognized. If cpp does
: not recognize the extension, it will treat the file as C; this is
: the most generic mode.
Cheers,
--
Ruslan Ermilov
ru at FreeBSD.org
FreeBSD committer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/cvs-src/attachments/20040428/76cb81ff/attachment.bin
More information about the cvs-src
mailing list