Since the compilation flags for clang to generate .bc file are a child set of what is used for gcc to generate .o file, some .bc file can fail to be generated. The failed ones can be seen in ./code/log/<linux-version>/irgen.log.
Since not all compilation flags supported by gcc are also supported by clang, it takes some time to locate the flag that can suppress that error, when you experience such an error, feel free to report it here e.g., the failing clang command line, I'll have a look and see how to suppress it.
Nevertheless, if it's just a few .c source code failed, it won't affect the following procedures very much, since the final merged .bc file is just a linking of all .bc files together.
Since the compilation flags for clang to generate
.bcfile are a child set of what is used for gcc to generate.ofile, some.bcfile can fail to be generated. The failed ones can be seen in ./code/log/<linux-version>/irgen.log.Since not all compilation flags supported by gcc are also supported by clang, it takes some time to locate the flag that can suppress that error, when you experience such an error, feel free to report it here e.g., the failing clang command line, I'll have a look and see how to suppress it.
Nevertheless, if it's just a few
.csource code failed, it won't affect the following procedures very much, since the final merged.bcfile is just a linking of all.bcfiles together.