LLVM? More likely LoLVM

LLVM has some ENTERPRISE QUALITY.

It has function createMCSubtargetInfo in Target class that creates subtarget for processor and its features. Unless you pass "help" string to it instead of CPU model.

In this case this function prints everything to stderr and calls exit(1), shutting down your whole application.

You write GUI program that has no stderr? Well, sucks to be you.
You can't get list of processors or features otherwise. Only by passing "help" and quiting application.
Thanks goodness LLVM has a nice license.

>>7
The Unix approach worked well for the predominantly text oriented tasks for that the system was created to handle. There are enough compromises in the original Unix systems to demonstrate that its creators knew byte I/O wasn't the best approach for everything (there are a lot more syscalls in AT&T Unix than just read and write, after all).

The religious supposition that byte streams are the best way to handle absolutely everything are a later development. Plan 9 helped popularize this but again I would point out that even that system doesn't use read and write for everything (its designers were smart people, not ideologues).

Having this behavior in a shared library like Clang is just old fashioned bad design. There are no functions in unistd.h that normally operate on data but kill your whole program if a magic argument is given, because that is a plainly stupid thing to do.

IHBT.