C source files with ``.i`` extension about sv-benchmarks HOT 6 CLOSED

We use .i for the pre-processed files (results of cpp -P)
and .c for the original files.
Sometimes (where you see only a .c file), pre-processing is not necessary.

On 15-10-11 12:00 PM, Dan Liew wrote:

Why are there C source files with an |.i| extension rather than |.c|?

Currently the Makefile build system won't build the |.i| files. It *technically could be taught to but it really over complicates matters (I have to worry about name clashes when generating the |.o| and |.d| files).

—
Reply to this email directly or view it on GitHub #41.

from sv-benchmarks.

@dbeyer Guess I will have to add support for this then

from sv-benchmarks.

Wait does that mean inside a directory if there are two files foo.c and foo.i that I should only build foo.i or should I build both? Building both would be really problematic because I would no longer be able to do

$ make foo.o

because the build system wouldn't know which one to build.

from sv-benchmarks.

If there are both files, typically only the .i file is relevant for SV-Comp, the source .c is present as documentation to show how the .i file was generated.

I think that it would probably be best to not care too much about which files are present in each directory, but use the .set files and the files listed therein (only the files from the .set files are relevant for SV-Comp).

from sv-benchmarks.

If there are both files, typically only the .i file is relevant for SV-Comp, the source .c is present as documentation to show how the .i file was generated.

Okay then I'll try to teach the build system to build .i files and pick those in preference to an identically named (modulo the suffix) .c file.

I think that it would probably be best to not care too much about which files are present in each directory, but use the .set files and the files listed therein (only the files from the .set files are relevant for SV-Comp).

Ah I did not know about this when I designed the build system. I made the assumption when designing it that most source files in the repository would be relevant or in a directory that I knew should not be traversed.

I might be able to incorporate them into the build process somehow...

from sv-benchmarks.

Support of *.i file implemented in 3e15c15

from sv-benchmarks.