Reason for clang behavior?

Posted Oct 10, 2024 7:44 UTC (Thu) by taladar (subscriber, #68407)
Parent article: Improving bindgen for the kernel

> Clang actually only supports using one precompiled header per source file, and silently ignores any others passed.

Is there a good reason for that or did someone just decide that it wouldn't matter to ignore others because it would "only" impact performance? I would have expected a well written tool to give an error in this situation.