> On Jul 5, 2016, at 11:31 AM, Marc Collin <marc.collin7_AT_gmail.com> wrote:
>
> I did some tests with 8cc (because it's easier to build than scc for me).
> My results are that the binaries aren't identical.
> Here's a script so you can try to reproduce it.
>
> #!/bin/sh
> mkdir test_comp
> cd test_comp
> git clone https://github.com/rui314/8cc
> mv 8cc 1c
> cp -r 1c 2c
> cp -r 1c Ac
> cp -r 1c Bc
>
> # compile 8cc with gcc
> cd 1c
> make cc=gcc
>
> # compile 8cc with clang
> cd ../2c
> make cc=clang
>
> # compile 8cc with 8cc
> # using the binary that
> # was compiled with gcc
> cd ../Ac
> make cc=../1c/8cc
>
> # compile 8cc with 8cc
> # using the binary that
> # was compiled with clang
> cd ../Bc
> make cc=../2c/8cc
>
> cd ..
>
> # compare binaries
> md5sum Ac/8cc Bc/8cc
If you run them again, do the md5s match from the first run? That is, if you keep the same compiler to start with, is there already instability in the build process? If so, then comparing against a second compiler doesn't mean so much.
There are compiler-specific things that can affect the resulting binaries, but I doubt they would affect *suckage*, and that is really the question.
>
> On Tue, Jul 5, 2016 at 2:24 PM, Quentin Rameau <quinq_AT_fifth.space> wrote:
>>> So let's consider 3 situations.
>>> 1-- Compile scc with gcc. Use the output binary to compile scc. Get B1
>>> 2-- Compile scc with tcc. Use the output binary to compile scc. Get B2
>>> 3-- Compile scc with clang. Use the output binary to compile scc. Get
>>> B3
>>>
>>> Are you saying that if we compare the md5 of B1, B2 and B3 they will
>>> be identical?
>> Well, that could depend on how high are solar winds that day (apart
>> from that, they should be, yes).
>
Received on Tue Jul 05 2016 - 20:47:28 CEST