On 11/17/19 9:57 AM, Andreas Schwab wrote: > On Nov 17 2019, Mikael Pettersson wrote: > >> /tmp/ccJA1qws.s:4828: Error: operands mismatch -- statement `seq %a1' ignored >> /tmp/ccJA1qws.s:7344: Error: operands mismatch -- statement `seq %a1' ignored > > That should fix it: > > diff --git a/gcc/config/m68k/m68k.md b/gcc/config/m68k/m68k.md > index 0cf063aaf84..3efcaad33a4 100644 > --- a/gcc/config/m68k/m68k.md > +++ b/gcc/config/m68k/m68k.md > @@ -698,7 +698,7 @@ > }) > > (define_insn "cstore_bftst<mode>_insn" > - [(set (match_operand:QI 0 "register_operand") > + [(set (match_operand:QI 0 "register_operand" "=d") > (match_operator:QI 1 "ordered_comparison_operator" > [(zero_extract:SI (match_operand:BTST 2 "<btst_predicate>" > "<btst_constraint>") > (match_operand:SI 3 "const_int_operand" "n") OK.
Bernd, presumably you can add this minor bugfix on top of your kit when you install it? Jeff ps. And to answer a question of Bernd's from a prior message. I'm not bootstrapping on real m68k hardware. I'm using qemu user space emulation + a native m68k chroot environment. I've also used Aranym in the past with good success. I prefer the former because it's the same core technology as other targets *and* since I'm just using user mode emulation I can exploit whatever SMP resources are on the host. jeff
