This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: GCC-4.0.2 on Cygwin


Kai Ruottu wrote:

Brian Rose wrote:

Brian Rose wrote:

/cygdrive/c/DOCUME~1/brose/LOCALS~1/TEMP/ccMW7YYh.s: Assembler messages:
/cygdrive/c/DOCUME~1/brose/LOCALS~1/TEMP/ccMW7YYh.s:31: Error: operands mismatch -- statement `fmovem.l %fpcr,%d1' ignored
/cygdrive/c/DOCUME~1/brose/LOCALS~1/TEMP/ccMW7YYh.s:42: Error: operands mismatch -- statement `fmovem.l %fpcr,%d1' ignored


 Please RTFM first! Is the opcode valid for m68040?  If so, there is
a bug in the assembler !  If it is not valid, your new gcc-4.x produces
bad code for m68040 !

Maybe yo should try another GCC or another binutils !


I have a process that works well for binutils-2.15 and gcc-3.4.2 that I use and is documented at http://brianrose.net/columns/CrossToolsWin32.html. I am just trying to update the tools to the current version.


I'm not actually working on anything now, but when I developed my process, I was working on the Coldfire target (specifically the MCF5249), and I used the --target=m68k-elf to build and run code without issue. Somehow, changing to binutils-2.16.1 or gcc-4.0.2 has introduced a problem into the GCC build.

My docs are at work and I am doing this as an interesting experiment at home. But I am just trying to resolve the errors in a process that once worked, and now does not. I guess the only constant is change.


--


Brian

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]