Intel C++ Compiler Classic / oneAPI toolkits (Unicode source handling): Improper handling of Unicode bidirectional

Impact

Improper handling of Unicode bidirectional and homoglyph characters in source code means the compiler can build something materially different from what a reviewer reads. This is the Trojan Source class - a supply-chain problem for anyone compiling third-party or contributor-supplied kernels and operators into their inference stack.

Who can reach it

Anyone who can get source into your build - an internal contributor, a vendored dependency, or a model-op repo you compile from.

What to do

Upgrade the compiler to 2021.6 / oneAPI 2022.2 or later, and add a CI check that rejects bidirectional control characters in source. Build-toolchain change only - no node reboot, no firmware. Rebuild any artefact compiled with an affected compiler if provenance matters.

References