Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 29 Jun 2013 18:39:27 +0200
From: Jens Gustedt <>
Subject: Re: Use of size_t and ssize_t in mseek

Am Samstag, den 29.06.2013, 12:13 -0400 schrieb Rich Felker:
> With that said, I'm not opposed to adding Annex K, but I think we
> should look into how invasive it would be, i.e. whether most/all
> interfaces can just be wrappers for the non-bounds-checking versions
> or whether major internal changes would be required to some existing
> interfaces.

I implemented quite a lot of them for P99, so I don't think that there
would be major problems. Many of them are just some if/else clauses
that check the run time constraints.

There are some additional functionalities, though, so these would
demand extra coding and objects, especially the run time constraint
handling, but I think these are quite limited and wouldn't require
much effort.

Then some interfaces are clearly different such that they can't simply
be copied over, notably bsearch and qsort functions, since they
receive additional arguments to provide context to the object

IIRC, what I couldn't handle within P99 was checking of printf
arguments, but from within musl this should be relatively straight


:: INRIA Nancy Grand Est ::   ::
:: AlGorille ::::::::::::::: office Nancy : +33 383593090   ::
:: ICube :::::::::::::: office Strasbourg : +33 368854536   ::
:: ::::::::::::::::::::::::::: gsm France : +33 651400183   ::
:: :::::::::::::::::::: gsm international : +49 15737185122 ::

Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.