Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <4E4DC636.1010109@gmail.com>
Date: Fri, 19 Aug 2011 04:11:02 +0200
From: Luka Marčetić <paxcoder@...il.com>
To: musl@...ts.openwall.com
Subject: cluts daily reports 8/19

Hey.

I've contacted Rich via IRC to ask about pthread_eintr. Specifically, 
what pthread_* functions make syscalls. I asked because I was surprised 
to find out most of my tests were for noth. Turns out there are only 
about 4 for which I haven't written tests (about 2 written). But then 
Rich implied the task itself is low priority with his question about my 
will to finish the test. Rich, maybe you meant to imply that I should 
start doing tests before I complete the incomplete ones? I'd wish you'd 
tell me these things explicitly. Anyway, assuming that is what I should 
do, I moved on to the task of adopting autoconf/gnulib tests (btw. 
they're both GPL...).
Autoconf has about 4 trivial and/or obsolete tests for the whole of 
stdio. I think there's no merit in adopting those. Gnulib, on the other 
hand from what I've seen so far seems like it could be useful. Attached 
are potential files for adoption from gnulib/tests (see the grep). Other 
than that, there's also a certain 
gnulib/tests/unistdio/test-u8-printf1.h that seems to test wchar 
support. I'm not sure if it's utf-8 specific though. If you think this 
may be useful, I can whip up a few replacement functions and include 
that file too.
So basically, I'm waiting your ok to start adopting these things into 
cluts. In the meanwhile I may finish pthread_eintr and later start 
string.c again.
Thanks.
Luka

P.S. No real to-report today, hopefully there'll be one tomorrow.

View attachment "printf.txt" of type "text/plain" (482 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.