Add new toolchain and driver options for the M68k target
Some very minor nits - the 68060 omission is the biggest one (apple might not have used it but commodore did!)
(sorting) put this before mips?
Why no 68060 ?
(style) remove unnecessary braces?
(clang-tidy) end namespace tools
(sorting) move before msp430 ?
(sorting) move down to before mips ?
Unless you are planning to add 100 or more target variations I'd prefer to see these explicitly defined instead of a foreach. If I'm grepping for a specific CPU variation in the code base it's nice to get that information easily.
No need for this else here.
and also the unnecessary elses.
Update: I've just put the sub-target (skeleton) for M68060. So now you can specific M68060 :-)
@RKSimon Just added 060's support :-)
I don't think so...first, const char *const means "a pointer points to const char, and you can't modify this pointer", which make sense in this context. Second, all the surrounding code here are using const char *const.
I think you misunderstood my comment. Having CHECK-A, CHECK-B, CHECK-C etc is fine. My issue was with the MX00/MX10/MX20 suffix that makes no sense to me; it's M68000/M68010/etc, X normally stands for a variable, but the 0 is always constant. M00/M10/etc, M000/M010/etc and M68000/M68010/M68020 would seem like more sensible names (also without the M would be fine), but MX00 looks like it's trying to match M000/M100/M200/etc, which is not the case.
Yeah, I just don't think it's particularly intuitive, especially when the backend was originally intended to be called M680x0, the use of an X to stand in for different things in very similar situations is confusing.