Straight from the GCC 4.5.0 Mint Patch (latest rev) from Vincent: +MULTILIB_OPTIONS = m68020-60/mcpu=5475 mshort + +MULTILIB_DIRNAMES = m68020-60 m5475 mshort + +MULTILIB_MATCHES = \ + m68020-60=m68881 \ + m68020-60=m68020 \ + m68020-60=m68020-40 \ + m68020-60=mc68020 \ + m68020-60=m68030 \ + m68020-60=m68040 \ + m68020-60=m68060 \ + m68020-60=mcpu?68020 \ + m68020-60=mcpu?68030 \ + m68020-60=mcpu?68040 \ + m68020-60=mcpu?68060 \ + m68020-60=march?68020 \ + m68020-60=march?68030 \ + m68020-60=march?68040 \ + m68020-60=march?68060 \ + mcpu?5475=mcfv4e \ + mcpu?5475=mcpu?5470 \ + mcpu?5475=mcpu?5471 \ + mcpu?5475=mcpu?5472 \ + mcpu?5475=mcpu?5473 \ + mcpu?5475=mcpu?5474 \ + mcpu?5475=mcpu?547x \ + mcpu?5475=mcpu?5480 \ + mcpu?5475=mcpu?5481 \ + mcpu?5475=mcpu?5482 \ + mcpu?5475=mcpu?5483 \ + mcpu?5475=mcpu?5484 \ + mcpu?5475=mcpu?5485 \ + mcpu?5475=mcpu?548x --- -m68020 with use the -m68020-60 option. So, you either build: 68000 code Code compatible with 68020-60 with FPU Code compatible with v4e Coldfire CPUs No other targets are supported.To support straight -m68020, someone would need to specifically build libc and friends supporting it, and maintain it, besides adding support to GCC.
That is the way things are right now. On Sat, 19 Jun 2010, Paul Wratt wrote:
On Fri, Jun 18, 2010 at 5:13 AM, m0n0 <ole@monochrom.net> wrote:Hello, I passed -m68020 to gcc invocation, but gcc takes libs from m68020-60 - why is that? Would be nice if someone can explain it in one sentence :) As far as I understood the -m68020 is using the fpu, while 68020-60 doesn't. Greets, Oleso Ole is right in assuming: "" the -m68020 is using the fpu, while 68020-60 doesn't. "" Thats a question, and I presumue (if yes) it applies to ALL other non 68000 targets? I just checked Wiki, it says 040 was the first with onboard FPU... can someone clarify this. (what gcc is using with a specific target) Paul