[uClinux-dev] Re: [PATCH v3 5/6] m68k: remove duplicate memcpy() implementation

2011-06-02 Thread Geert Uytterhoeven
On Thu, Jun 2, 2011 at 07:18, Greg Ungerer g...@snapgear.com wrote: On 26/05/11 16:38, Geert Uytterhoeven wrote: I was more thinking along the lines of !CONFIG_M68000  !CONFIG_M68010  !CONFIG_whatever Coldfire that doesn't support it. Or in this case (and probably most cases) we could just

[uClinux-dev] Re: [PATCH v3 5/6] m68k: remove duplicate memcpy() implementation

2011-06-02 Thread Greg Ungerer
Hi Geert, On 02/06/11 17:43, Geert Uytterhoeven wrote: On Thu, Jun 2, 2011 at 07:18, Greg Ungererg...@snapgear.com wrote: On 26/05/11 16:38, Geert Uytterhoeven wrote: I was more thinking along the lines of !CONFIG_M68000 á!CONFIG_M68010 á!CONFIG_whatever Coldfire that doesn't support

[uClinux-dev] Re: [PATCH v3 5/6] m68k: remove duplicate memcpy() implementation

2011-06-01 Thread Greg Ungerer
Hi Geert, On 26/05/11 16:38, Geert Uytterhoeven wrote: On Thu, May 26, 2011 at 08:23, Greg Ungererg...@snapgear.com wrote: On 24/05/11 18:06, Andreas Schwab wrote: Geert Uytterhoevenge...@linux-m68k.org áwrites: What exactly do you mean by does not support anything less? It seems it

[uClinux-dev] Re: [PATCH v3 5/6] m68k: remove duplicate memcpy() implementation

2011-05-26 Thread Greg Ungerer
Hi Andreas, Geert, On 24/05/11 18:06, Andreas Schwab wrote: Geert Uytterhoevenge...@linux-m68k.org writes: What exactly do you mean by does not support anything less? It seems it does restrict instruction generation to 68000 if you ask for it. The point is that Linux/m68k requires 68020+,

[uClinux-dev] Re: [PATCH v3 5/6] m68k: remove duplicate memcpy() implementation

2011-05-26 Thread Geert Uytterhoeven
On Thu, May 26, 2011 at 08:23, Greg Ungerer g...@snapgear.com wrote: On 24/05/11 18:06, Andreas Schwab wrote: Geert Uytterhoevenge...@linux-m68k.org  writes: What exactly do you mean by does not support anything less? It seems it does restrict instruction generation to 68000 if you ask for

RE: [uClinux-dev] Re: [PATCH v3 5/6] m68k: remove duplicate memcpy() implementation

2011-05-26 Thread Gavin Lambert
Quoth Greg Ungerer: On 24/05/11 18:06, Andreas Schwab wrote: Geert Uytterhoevenge...@linux-m68k.org writes: What exactly do you mean by does not support anything less? It seems it does restrict instruction generation to 68000 if you ask for it. The point is that Linux/m68k

Re: [uClinux-dev] Re: [PATCH v3 5/6] m68k: remove duplicate memcpy() implementation

2011-05-26 Thread Greg Ungerer
Hi Gavin, On 26/05/11 17:28, Gavin Lambert wrote: Quoth Greg Ungerer: On 24/05/11 18:06, Andreas Schwab wrote: Geert Uytterhoevenge...@linux-m68k.org writes: What exactly do you mean by does not support anything less? It seems it does restrict instruction generation to 68000 if you ask

[uClinux-dev] Re: [PATCH v3 5/6] m68k: remove duplicate memcpy() implementation

2011-05-24 Thread Geert Uytterhoeven
On Mon, May 23, 2011 at 21:54, Andreas Schwab sch...@linux-m68k.org wrote: Geert Uytterhoeven ge...@linux-m68k.org writes: FWIW, my m68k-linux-gnu-gcc (4.1.2 20061115 (prerelease)) always defines __mc68000__ and __mc68020__, even when specifying -m68000 on the command line. m68k-linux has

[uClinux-dev] Re: [PATCH v3 5/6] m68k: remove duplicate memcpy() implementation

2011-05-23 Thread Greg Ungerer
On 24/05/11 05:54, Andreas Schwab wrote: Geert Uytterhoevenge...@linux-m68k.org writes: FWIW, my m68k-linux-gnu-gcc (4.1.2 20061115 (prerelease)) always defines __mc68000__ and __mc68020__, even when specifying -m68000 on the command line. m68k-linux has always defined __mc68020__