public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Philippe De Muyter <phdm@macqel.be>
To: Greg Ungerer <gerg@snapgear.com>
Cc: uClinux development list <uclinux-dev@uclinux.org>,
	linux-m68k@vger.kernel.org, Greg Ungerer <gerg@uclinux.org>
Subject: Re: [uClinux-dev] [PATCH v2 1/6] m68k: merge mmu and non-mmu versions of muldi3
Date: Wed, 20 Apr 2011 12:38:02 +0200	[thread overview]
Message-ID: <20110420103802.GA26891@frolo.macqel> (raw)
In-Reply-To: <4DAEB2E1.6050404@snapgear.com>

Hi Greg,

On Wed, Apr 20, 2011 at 08:18:09PM +1000, Greg Ungerer wrote:
>>
>> The 68340 has it also. (And I have an old linux port for this processor)
>
> That is just a SoC that contains a 68020 though, so __mc68020__ would
> be defined for that.

No, this is a cpu32 core, which is a subset of a 68020, so gcc does not
define __mc68020__, or at least should not (there are old bug reports
about that).

>
>
>> I surmise the 68360 has it also.
>
> I believe that is a SoC with a 68040 cpu core, so I would expect that
> __mc68040__ would be correct for that.

This is a cpu32+ core.

Same here.

Not that it is that important now :)

Philippe

  parent reply	other threads:[~2011-04-20 10:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20  5:54 [PATCH v2 0/6] m68knommu: merge and clean up of arch/m68k/lib files gerg
2011-04-20  5:54 ` gerg
2011-04-20  5:54   ` [PATCH v2 1/6] m68k: merge mmu and non-mmu versions of muldi3 gerg
2011-04-20  5:54     ` [PATCH v2 2/6] m68k: merge mmu and non-mmu versions of lib/Makefile gerg
2011-04-20  5:54       ` [PATCH v2 3/6] m68k: remove duplicate memmove() implementation gerg
2011-04-20  5:54         ` [PATCH v2 4/6] m68k: remove duplicate memset() implementation gerg
2011-04-20  5:54           ` [PATCH v2 5/6] m68k: remove duplicate memcpy() implementation gerg
2011-04-20  5:54             ` [PATCH v2 6/6] m68k: let Makefile sort out compiling mmu and non-mmu lib/checksum.c gerg
2011-04-20  8:06     ` [PATCH v2 1/6] m68k: merge mmu and non-mmu versions of muldi3 Sam Ravnborg
2011-04-20  8:55       ` [uClinux-dev] " Geert Uytterhoeven
2011-04-20  9:12         ` Philippe De Muyter
2011-04-20  9:31           ` [uClinux-dev] " Greg Ungerer
2011-04-20  9:55             ` Philippe De Muyter
2011-04-20 10:18               ` Greg Ungerer
2011-04-20 10:38                 ` Andreas Schwab
2011-04-20 10:38                 ` Philippe De Muyter [this message]
2011-04-20 11:01                   ` Greg Ungerer
2011-04-20 11:23                     ` Philippe De Muyter
2011-04-20  8:57       ` Philippe De Muyter
2011-04-20  9:08       ` Greg Ungerer
2011-04-20  6:04   ` [PATCH v2 0/6] m68knommu: merge and clean up of arch/m68k/lib files Greg Ungerer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110420103802.GA26891@frolo.macqel \
    --to=phdm@macqel.be \
    --cc=gerg@snapgear.com \
    --cc=gerg@uclinux.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=uclinux-dev@uclinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox