[PATCH] Prevent repetitive warnings for unrecognized processors and features (2nd attempt)

Renato Golin renato.golin at linaro.org
Tue Feb 4 05:09:15 PST 2014


On 4 February 2014 12:21, Artyom Skrobov <Artyom.Skrobov at arm.com> wrote:

> A proper fix for the driver would be to replace the whole cascade of
> StringSwitch'es with something tablegen-driven, and ideally based on the
> same tablegen files that drive the target selection in the backend. This is
> a long-known FIXME, but it's unlikely to be finished in the short-term.
>

Unfortunately, a "proper fix" was already proposed by many people, and
there was enough controversy on that topic for a generation. Furthermore,
there are those that don't agree that the driver needs a big change, but
rather a small fix, mainly to the architecture definition (CPUs, features,
triples, OSs, etc).

AFAICR, the solutions were:

1. tablegen. PRO: more expressive. CON: static, needs recompilation for
small changes
2. hand-written: PRO: flexible. little changes. CON: will become a mess,
again.
3. config files. PRO: dynamic and provider/user driven. CON: different than
anyone else is doing, and can become a monster

The least controversial is 2, so any change in that direction will probably
be reviewed quickly. The others, well, good luck. I personally think a mix
of hand-written and config files would be the easiest to convince everyone.

cheers,
--renato
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20140204/1b154949/attachment.html>


More information about the llvm-commits mailing list