This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: m68k: "instruction/operands mismatch" -- Statement 'moveb a3,d1' ignored
- To: toon at moene dot indiv dot nluug dot nl
- Subject: Re: m68k: "instruction/operands mismatch" -- Statement 'moveb a3,d1' ignored
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Tue, 30 Nov 1999 23:40:55 -0700
- cc: gcc at gcc dot gnu dot org
- Reply-To: law at cygnus dot com
In message <199911211543.HAA28745@cygnus.com>you write:
> GCC snapshot CVS'd 19991121133UTC:
>
> "instruction/operands mismatch" -- Statement 'moveb a3,d1' ignored
> touch stamp-str
> stage1/xgcc -Bstage1/ -B/usr/snp/m68k-next-nextstep3/bin/ -c -DIN_GCC -
> W -Wall -O2 -g -O2 -W -Wall -I. -I.. -I../../../egcs/gcc/f -I../../../e
> gcs/gcc/f/.. -I../../../egcs/gcc/f/../config -I../../../egcs/gcc/f/../../in
> clude ../../../egcs/gcc/f/expr.c
> /usr/tmp/ccBvOixk.s:11750:"instruction/operands mismatch" -- Statement 'mov
> eb a3,d1' ignored
I didn't even get that far :( Mine core dumped running genrecog in the
stage2 build. But I was working from the Nov 15 sources. I'm updating the
sources to see if this particular problem has already been fixed. Once
I can get that working, I'll see if I can reproduce your problem.
> Seems to be something amiss in the m68k.md - not to mention the number of w
> arnings I get:
>
> /genrecog ../../egcs/gcc/config/m68k/m68k.md > tmp-recog.c
> ./../egcs/gcc/config/m68k/m68k.md:898: warning: destination operand 0 allow
> s non-lvalue
Not really. They're relatively minor issues that genrecog was recently
enhanced to detect and warn about. For truly serious problems genrecog
will spit out an error.
jeff