mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Luka Marčetić" <paxcoder@gmail.com>
To: musl@lists.openwall.com
Subject: cluts daily reports 8/19
Date: Fri, 19 Aug 2011 04:11:02 +0200	[thread overview]
Message-ID: <4E4DC636.1010109@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1453 bytes --]

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.

[-- Attachment #2: printf.txt --]
[-- Type: text/plain, Size: 482 bytes --]

ls | grep printf | grep .c | grep posix
test-dprintf-posix2.c
test-dprintf-posix.c
test-fprintf-posix2.c
test-fprintf-posix3.c
test-fprintf-posix.c
test-printf-posix2.c
test-printf-posix.c
test-snprintf-posix.c
test-sprintf-posix.c
test-vasnprintf-posix2.c
test-vasnprintf-posix3.c
test-vasnprintf-posix.c
test-vasprintf-posix.c
test-vdprintf-posix.c
test-vfprintf-posix.c
test-vprintf-posix.c
test-vsnprintf-posix.c
test-vsprintf-posix.c
test-xfprintf-posix.c
test-xprintf-posix.c

             reply	other threads:[~2011-08-19  2:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19  2:11 Luka Marčetić [this message]
2011-08-19  2:15 ` Luka Marčetić
2011-08-19  2:41 ` Rich Felker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E4DC636.1010109@gmail.com \
    --to=paxcoder@gmail.com \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).