Re: [PATCH] arch/sh: provide unified syscall trap compatible with all SH models

2015-08-25 Thread Rich Felker
On Tue, Aug 25, 2015 at 09:18:44AM +0200, Geert Uytterhoeven wrote: > Hi Rich, > > On Tue, Aug 25, 2015 at 5:03 AM, Rich Felker wrote: > > From: Rich Felker > > > > Historically SH-2 Linux (and originally uClinux) used a syscall > > calling convention incompatible with the established SH-3/4

Re: [PATCH] arch/sh: provide unified syscall trap compatible with all SH models

2015-08-25 Thread Geert Uytterhoeven
Hi Rich, On Tue, Aug 25, 2015 at 5:03 AM, Rich Felker wrote: > From: Rich Felker > > Historically SH-2 Linux (and originally uClinux) used a syscall > calling convention incompatible with the established SH-3/4 Linux ABI. > This choice was made because the trap range used by the existing ABI, >

Re: [PATCH] arch/sh: provide unified syscall trap compatible with all SH models

2015-08-25 Thread Geert Uytterhoeven
Hi Rich, On Tue, Aug 25, 2015 at 5:03 AM, Rich Felker dal...@libc.org wrote: From: Rich Felker dal...@libc.org Historically SH-2 Linux (and originally uClinux) used a syscall calling convention incompatible with the established SH-3/4 Linux ABI. This choice was made because the trap range

Re: [PATCH] arch/sh: provide unified syscall trap compatible with all SH models

2015-08-25 Thread Rich Felker
On Tue, Aug 25, 2015 at 09:18:44AM +0200, Geert Uytterhoeven wrote: Hi Rich, On Tue, Aug 25, 2015 at 5:03 AM, Rich Felker dal...@libc.org wrote: From: Rich Felker dal...@libc.org Historically SH-2 Linux (and originally uClinux) used a syscall calling convention incompatible with the

[PATCH] arch/sh: provide unified syscall trap compatible with all SH models

2015-08-24 Thread Rich Felker
From: Rich Felker Historically SH-2 Linux (and originally uClinux) used a syscall calling convention incompatible with the established SH-3/4 Linux ABI. This choice was made because the trap range used by the existing ABI, 0x10-0x17, overlaps with the hardware exception/interrupt trap range

[PATCH] arch/sh: provide unified syscall trap compatible with all SH models

2015-08-24 Thread Rich Felker
From: Rich Felker dal...@libc.org Historically SH-2 Linux (and originally uClinux) used a syscall calling convention incompatible with the established SH-3/4 Linux ABI. This choice was made because the trap range used by the existing ABI, 0x10-0x17, overlaps with the hardware exception/interrupt