This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Gsoc 2014 project proposal
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Andrea Francesco Iuorio <andreafrancesco dot iuorio at gmail dot com>, libc-alpha at sourceware dot org
- Date: Thu, 27 Feb 2014 01:15:29 -0500
- Subject: Re: Gsoc 2014 project proposal
- Authentication-results: sourceware.org; auth=none
- References: <CAMaJsKjobBfmxjBRB2WP6MMLiAAD=QTV3bhO=hogeZHxmmotPg at mail dot gmail dot com> <Pine dot LNX dot 4 dot 64 dot 1402261759390 dot 11728 at digraph dot polyomino dot org dot uk> <CAMaJsKg-4WTvX+XPYXMYXHZvRvUotyYeq7O69Xye4WBE7Zw6Wg at mail dot gmail dot com>
On 02/26/2014 02:34 PM, Andrea Francesco Iuorio wrote:
> I didn' t think about it. It perfectly make sense since pthread ( and
> its internal types ) is an userspace library and so the user can
> define their own pthread functions. I' ll change my implementation
> plan to include some time to study what pthread function i' ll need
> for the project while i' m reading the C11 reference. At the moment i
> don' t know what pthread ( and functions in general ) i should need to
> create aliasies but that means that, during the first period, i should
> make a precise plan of what functions i should change in glibc ( and
> than change them )
I suggest *against* a precise plan. My strong suggestion is that you
approach this tactically e.g. one function at a time. This way should
you need to stop at any point the result is something that can be
continued easily and the partial work is not lost.
Adding the first function is the most work because it requires the
new headers, and refactoring to get the types right.
Cheers,
Carlos.