Hi,
On Fri, Nov 19, 2010 at 11:58 PM, Arnaud Lacombe <lacom...@gmail.com> wrote:
> [...]
> continuing to dig for other errors.
>
One nits; is there any reason to use `__xpg_strerror_r()' which is not
POSIX, versus 'strerror_r()' [0] ?
// FIXME: The name is only right for glibc.
func libc_strerror_r(int, *byte, Size_t) int __asm__ ("__xpg_strerror_r")
As RTEMS prototypes has already been mangled to make it return `int'
instead of the `char *', that would allow to merge all
`libgo/syscalls/errstr*.go'.
- Arnaud
[0]: http://www.opengroup.org/onlinepubs/9699919799/functions/strerror.html
