Re: gcc/mfidoa again, or binutils?

On Tue, 2 Nov 2010, I wrote: > > $ m68k-linux-gnu-as x.s -mcpu32 > $ > > Fido is supposed to be compatible with CPU32. With no FPU, the > unimplemented F-line instruction exception is available (says the > Motorola CPU32 Reference Manual on page 6-9). The Fido1100 User Guide agrees: http://w

Re: gcc/mfidoa again, or binutils?

Finn Thain dixit: >Grep found this in gas/m68k/all.exp: Oh, but just take some other floating point ops. I wrote a small .c calling a lot of things from and built with -D_GNU_SOURCE -O3 -S to get that, then just took one randomly for a test case. bye, //mirabilos -- I believe no one can invent

Re: gcc/mfidoa again, or binutils?

On Mon, 1 Nov 2010, Thorsten Glaser wrote: > Hi, > > I believe this may be a bug in our binutils: Also binutils 2.20.51.20101024. > > r...@ara2:~ # cat >x.s > .text > fmove.l %d1, %fpcr > r...@ara2:~ # as x.s > r...@ara2:~ # as x.s -mfidoa > x.s: Assembler messages: > x.s:2: E

gcc/mfidoa again, or binutils?

Hi, I believe this may be a bug in our binutils: r...@ara2:~ # cat >x.s .text fmove.l %d1, %fpcr r...@ara2:~ # as x.s r...@ara2:~ # as x.s -mfidoa x.s: Assembler messages: x.s:2: Error: invalid instruction for this architecture; needs 68020 [68k, 68ec020], 68030 [68ec030], 68040

Bug#602099: gcc-4.4: next round of m68k specific patches

Source: gcc-4.4 Version: 4.4.5-5 Severity: wishlist Tags: patch Hi, here’s the next round of m68k support. The patches have accumulated by discussion on the mailing list; they are not yet regression te- sted, but this is tracked by the submitters, and the binary packages compiled from this work f

Re: status report (almost done)

Ah well, two more things. Dixi quod… >I’m only two packages short of uploading to unstable (when possible) and The .dsc/.changes are not yet debsign’ed (this takes time, as I don’t have the key on the same machine), will do before uploading, just in case newer versions must be built too. >With

status report (almost done)

Hi *, I’m only two packages short of uploading to unstable (when possible) and unreleased (when necessary): util-linux (which, due to Finn’s gcc fixes, should work now – jpeg did) and eglibc (just rebuilding with the new gcc and re-synching against latest sid). After I upload, however, there are