Developers of compilers, debuggers and such are way more likely to introduce bugs with CISC architectures. Complexity doesn't end at the edge of the chip. It goes down the chain.
Debugging RISC object code is also easier, for the same reason.
RISC is a meaningless term today to describe design complexity. People see 'cmov' in x86 or the boot process or variable-length instructions or whatever, and think, "wow, how horribly complex this all is, it must be a huge design problem, and it's probably because of the instruction" -- but if they see some modern ARM machine do superscalar OoO execution in order to execute an instruction over multiple cycles and the compiler scheduled instructions taking that particular latency/throughput into account so it could generate optimal code for that uarch -- it's like, wow, this is all so simple, it must make everything so much easier. It doesn't, but it's worth asking what does the debate even mean at that point? All the actual complexity is elsewhere, and is (mostly) independent of the ISA.
Side note, but I have RISC-V hardware on my desk and one of the errata for this particular silicon is "the MMU may not catch and deliver all memory access violations correctly" -- meaning you just don't have memory protection sometimes, in some cases, on some days with some shirt colors! I'm pretty sure the ISA doesn't mandate that, and I'm also pretty sure it didn't come from the instruction decoder. Luckily, in this case, programmers have repeatedly proven they are extremely reliable at handling and estimating issues of memory safety (reliably bad at it).
Itanium is a counterexample to your argument.
>All the actual complexity is elsewhere, and is (mostly) independent of the ISA.
Which renders ISA complexity difficult to defend, particularly as RISC-V has demonstrated code density competitive with amd64.
Complexity is inherently bad, thus the use of complexity needs strong justification.
[1] http://itre.cis.upenn.edu/~myl/languagelog/archives/003775.h...
RISC-V is trying to make that a thing of the past.
Fewer bugs in your code, or fewer bugs to encounter in the platform?
I've found that my bugs are usually processor-independent, and that most of the bugs in SOCs are not with the CPU cores, but the support components around them (e.g., DMA engines and timer registers with bizarre behavior).
Well . . . and cache coherency issues. But everyone has cache coherency bugs. :-)