2 ms·
Competition is a strong motivator to improve areas your implementation is bad at. E.g. with gcc/clang an often-mentioned example is error messages: They're not
by detaro 7y ago
Competition is a strong motivator to improve areas your implementation is bad at. E.g. with gcc/clang an often-mentioned example is error messages: They're not a benchmark you can optimize for, but turns out users really like helpful error messages and will start using a different compiler for them.
Actual standardization (as in, there is a document describing the what's supposed to happen) is helped by multiple implementations because their conflicts will help discover unclear parts. This in return helps new implementations get of the ground if there's a need to produce them. Some standards groups require multiple independent implementation of something to exist before it is allowed to be released as a standard.
Different implementations might be different enough that some changes are easier to make in one than the other. This makes it easier to test these changes, the other implementation(s) can then decide if the gains are worth their effort.
It provides an out if one project resists changes for human/political reasons.
I wouldn't be surprised if there's a few unusual architectures around that use Fortran but aren't handled by LLVM.