News for hackers. Stuff that matters.
Re:55 GiB/s FizzBuzz (2021) by haunter on Monday July 03, 2023 @02:45AM (#36569611)
> Save it as fizzbuzz.S (that's a capital S as the extension)

What’s the significane of “.S” vs “.s”?

Re:55 GiB/s FizzBuzz (2021) by harrisi on Monday July 03, 2023 @02:49AM (#36569627)
Capital S will run the pre processor first.

Edit:

From manpage:

    file.s
        Assembler code.
    file.S
    file.sx
        Assembler code that must be preprocessed.
Re:55 GiB/s FizzBuzz (2021) by wkz on Monday July 03, 2023 @02:50AM (#36569633)
IIRC, I believe that the difference traditionally was whether to pass the input through the preprocessor (.S), or not (.s).

Not sure if it makes a difference on modern toolchains.

Re:55 GiB/s FizzBuzz (2021) by zen_1 on Monday July 03, 2023 @02:58AM (#36569684)
The convention I'm used to uses .S to denote hand-written assembly files (usually tracked in git) vs .s for machine generated assembly which can be overwritten as needed.
Re:55 GiB/s FizzBuzz (2021) by easytiger on Monday July 03, 2023 @02:48AM (#36569621)
GCC et al won't overwrite a .S but if you ask it to gen ASM (e.g. gcc -S xyz.c) it will overwrite a .s