public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: finishing cancellation support
Date: Sun, 29 Jun 2003 18:24:00 -0000	[thread overview]
Message-ID: <3EFF2EDA.9080106@redhat.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm on the home stretch for the cancellation handling.  The secondary
cancellation points need to be handled and other functions not intended
to be cancellation points need to be modified appropriately.

The biggest problem (beside time) are the cancellation handlers.
Actually, it's not too much of a problem, not with the C cleanup
attribute handling.  This is why I'll bump the gcc requirement to gccs
with this cleanup handling.  It's nothing really new, any deployed glibc
already had to be compiled with such a gcc.  But it'll now be a
configure test.  gcc 3.3.1 has the code (and will probably released
soon).  The Red Hat backport to gcc 3.2 also has the changes.  So there
should be a compiler for everybody.

I'll be checking in code in small chunks.  The amount of work is too
large to do it in one scoop.  Hopefully everything remains usable.

The biggest problem is testing.  Especially with the exception based
cleanup.  I could really use some help.  While doing the work I'll
document which of the secondary cancellation points (see the second
table in 2.9.5.2 POSIX 2003) are actual cancellation points in NPTL.  If
I could get some help with writing test cases similar to the ones in
tst-cancel4.c in NPTL this would speed up things quite a bit.

- -- 
- --------------.                        ,-.            444 Castro Street
Ulrich Drepper \    ,-----------------'   \ Mountain View, CA 94041 USA
Red Hat         `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+/y7a2ijCOnn/RHQRApYnAKDGcbiUEErdhDMDAsXuILP/EqK4zgCfRy0E
NqwyTXxf8moXfwCo7LSeUno=
=F9lp
-----END PGP SIGNATURE-----

                 reply	other threads:[~2003-06-29 18:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3EFF2EDA.9080106@redhat.com \
    --to=drepper@redhat.com \
    --cc=libc-hacker@sources.redhat.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).