cvs commit: src/sys/sys signal.h

Daniel Eischen deischen at
Wed Dec 7 19:21:41 PST 2005

On Thu, 8 Dec 2005, David Xu wrote:

> Daniel Eischen wrote:
> >>So will there be some sort of compatibility shims?  I bet that there
> >>will still be a lot of 4.x binaries being run on 7.0 systems in the
> >>future, just like 2.2.8 binaries were being run for years after 3.x and
> >>4.x came out.
> >>
> >>
> >
> >Yeah, and we can implement the shims in versioned libraries ;-)
> >
> At least, util now, there is no binary compatible problem. but I would like
> we will implement SIGEV_THREAD before 7.0, this is why I requested you
> to implement it ASAP because you claimed you will do it, so I just
> sit back. Current only libthr implemented SIGEV_THERAD for timer, I can
> implement it for mqueue, but aio syscall interface sucks, need more time
> for it.

I was going to do it in libc so it doesn't have to be done by each
thread library.

But there are still aio_* syscalls that haven't been changed to have
compat syscalls.  You did aio_read, aio_write, and lio_listion, but
not aio_error, aio_return, aio_suspend, aio_cancel, and aio_waitcomplete.
I think these really need compat syscalls due to the different layout of
struct sigevent (because it affects layout of struct aiocb).

I don't think Library-level shims aren't going to help in the case of
statically built binaries.


More information about the cvs-src mailing list