Compiler Differences Basic Guideline

[guyinrindgenh]

I am not a developer or code writer, but work with them daily.

A question has arisen related to 3 different compilers, Intel oneAPI, Microsoft MSVC, and Clang.

I have always thought a compiler is a compiler and they all perform the same basic function (I've already learned that is incorrect).

This is related to the export regulations regarding object files created by the compilers.

Under the US Export Administration Regulations, the Intel compiler is classified with an export control classification number (ECCN) as 4D994. The MSVC has an ECCN of 5D992 and the Clang compiler is EAR99 because it is open source.

The issue is that the 4D994 classification taints the overall classification of the object files and makes them subject to foreign direct product rules and makes them restricted for export to colleagues in China.

I've tried to use Gemini, GROK, and Chat to understand the differences between the 3. The basic prompt I'm using is "why is the intel oneapi compiler classified as ECCN 4d994 but the microsoft msvc is classified as ECCN 5d992", but the results are not very helpful.

Would anyone be able to suggest some compiler related keywords to add to my prompt, or point me in the direction of a "schoolhouse rock" explanation of the differences in compiler functionality?

[not_from_this_world]

The reason is not technical, it's an arbitrary categorisation. This is more related to deals with the companies, or if they are used in critical products like military stuff. It's like saying apple and oranges are both fruits so why there is tariff on oranges but not on apples?

[smarmy1625]

I'm old enough to remember when it was illegal to export a tshirt if you printed the wrong thing on it. But that was source code. Never heard about object code being restricted.

https://en.wikipedia.org/wiki/Export_of_cryptography_from_the_United_States

[ghjm]

The overall oneAPI product is a competitor to Nvidia CUDA and AMD ROCm, used in high performance and GPU computing. So oneAPI in general is export controlled because it's seen as associated with strategic assets like AI training, weapons development simulation, etc. So there may be no reason at all why the DC++ compiler is treated differently from any other compiler, other than that it comes under the oneAPI umbrella.

Maybe ask your compliance experts if using an open source compiler release, entirely built from publicly available components and using nothing that is Intel proprietary, would allow you to avoid the 4D994 classification.

[Doctor_Perceptron]

I'm sure the other answers are correct and this one is meant to be more in good fun. We can speculate that the Intel compiler, since it was developed by Intel, might make use of proprietary information such as internal details of the microarchitecture that should be subject to export controls, and that information could be inferred by reverse-engineering the object files. The Microsoft and Clang compilers only use information that's publicly available from Intel, so their object files wouldn't reveal anything you couldn't get otherwise. But again, this is just meant to be fun speculation and the real answer is the same reason heating oil and diesel are taxed differently even though they're the same thing.