From 95fdc6a0f61a389e92a6b84250c2286b4808b626 Mon Sep 17 00:00:00 2001 From: Ulrich Drepper Date: Sun, 30 Jun 2002 04:04:20 +0000 Subject: [PATCH] Update. 2002-06-19 Steven Munroe * Examples/ex9.c (main): Use list of children and join them. (thread): Do not call exit. --- linuxthreads/ChangeLog | 5 +++ linuxthreads/Examples/ex9.c | 14 +++++-- localedata/ChangeLog | 3 ++ localedata/locales/mt_MT | 79 +++++++++++++++++++++++++++++++++++++ manual/argp.texi | 2 +- manual/arith.texi | 10 ++--- manual/charset.texi | 24 +++++------ manual/ctype.texi | 2 +- manual/filesys.texi | 4 +- manual/install.texi | 8 ++-- manual/locale.texi | 2 +- manual/memory.texi | 4 +- manual/resource.texi | 4 +- manual/startup.texi | 4 +- manual/stdio.texi | 8 ++-- manual/time.texi | 2 +- 16 files changed, 134 insertions(+), 41 deletions(-) diff --git a/linuxthreads/ChangeLog b/linuxthreads/ChangeLog index fa1c8b0f5d..9102cd044c 100644 --- a/linuxthreads/ChangeLog +++ b/linuxthreads/ChangeLog @@ -1,3 +1,8 @@ +2002-06-19 Steven Munroe + + * Examples/ex9.c (main): Use list of children and join them. + (thread): Do not call exit. + 2002-06-20 Ulrich Drepper * spinlock.c (wait_node_alloc): We cannot use compare-and-exchange. diff --git a/linuxthreads/Examples/ex9.c b/linuxthreads/Examples/ex9.c index dafb4065de..9b8aca3b94 100644 --- a/linuxthreads/Examples/ex9.c +++ b/linuxthreads/Examples/ex9.c @@ -32,7 +32,8 @@ static pthread_barrier_t barrier; int main (void) { - pthread_t th; + pthread_t th; + pthread_t thread_list[NUM_THREADS]; int i; if (pthread_barrier_init (&barrier, NULL, NUM_THREADS + 1) != 0) @@ -40,12 +41,17 @@ main (void) for (i = 0; i < NUM_THREADS; i++) { - if (pthread_create (&th, NULL, thread, NULL) != 0) + if (pthread_create (&thread_list[i], NULL, thread, NULL) != 0) error (EXIT_FAILURE, 0, "cannot create thread"); } (void) thread (NULL); - /* notreached */ + + for (i = 0; i < NUM_THREADS; i++) + { + pthread_join(thread_list[i], NULL); + } + return 0; } @@ -87,7 +93,7 @@ thread (void *arg) printf ("%04d: last serial thread %lu terminating process\n", ++linecount, (unsigned long) self); funlockfile (stdout); - exit (0); + return; } pthread_exit(NULL); diff --git a/localedata/ChangeLog b/localedata/ChangeLog index c6d86073e7..4f4451dae2 100644 --- a/localedata/ChangeLog +++ b/localedata/ChangeLog @@ -1,5 +1,8 @@ 2002-06-29 Ulrich Drepper + * locales/mt_MT: Add locale-specific collation info. + Patch by Ramon Casha [PR libc/3701]. + * locales/en_AU: Add am/pm support. Patch partly by maffew@cat.org.au [PR libc/3911]. diff --git a/localedata/locales/mt_MT b/localedata/locales/mt_MT index 6279471da7..47e59cf813 100644 --- a/localedata/locales/mt_MT +++ b/localedata/locales/mt_MT @@ -3,6 +3,9 @@ escape_char / % Maltese language locale for Malta. % Contributed by Kentaroh Noji and % Tetsuji Orita . +% +% collating order changes by Ramon Casha +% and Pablo Saratxaga -- 2002-05-08 LC_IDENTIFICATION title "Maltese language locale for Malta" @@ -37,9 +40,85 @@ END LC_CTYPE LC_COLLATE +% a b c c. d e f g. g gh/ h h/ i ie j k l m n o p q r s t u v w x y z. z + % Copy the template from ISO/IEC 14651 copy "iso14651_t1" +collating-symbol +collating-symbol +collating-symbol +collating-symbol + +collating-symbol +collating-element from "" +collating-element from "" +collating-element from "" +collating-element from "" + +collating-symbol +collating-element from "" +collating-element from "" +collating-element from "" +collating-element from "" + +collating-symbol +collating-symbol + +reorder-after + +reorder-after + + +reorder-after + +reorder-after + +reorder-after + +reorder-after + +reorder-after + +reorder-after + + +reorder-after + ;;;IGNORE +reorder-after + ;;;IGNORE + +reorder-after + ;;;IGNORE +reorder-after + ;;;IGNORE + +reorder-after + ;;;IGNORE + ;;;IGNORE +reorder-after + ;;;IGNORE + ;;;IGNORE + +reorder-after + ;;;IGNORE +reorder-after + ;;;IGNORE + +reorder-after + ;;;IGNORE + ;;;IGNORE +reorder-after + ;;;IGNORE + ;;;IGNORE + +reorder-after + ;;;IGNORE +reorder-after + ;;;IGNORE + +reorder-end + END LC_COLLATE LC_MONETARY diff --git a/manual/argp.texi b/manual/argp.texi index b7446970c3..090d49f7a5 100644 --- a/manual/argp.texi +++ b/manual/argp.texi @@ -467,7 +467,7 @@ Here's an example that uses both, for different args: @smallexample -... +@dots{} case ARGP_KEY_ARG: if (@var{state}->arg_num == 0) /* First argument */ diff --git a/manual/arith.texi b/manual/arith.texi index c40ba3c59e..0f2e6fe86d 100644 --- a/manual/arith.texi +++ b/manual/arith.texi @@ -755,9 +755,9 @@ is a simple example of the way to use @code{fetestexcept}: feclearexcept (FE_ALL_EXCEPT); f = compute (); raised = fetestexcept (FE_OVERFLOW | FE_INVALID); - if (raised & FE_OVERFLOW) @{ /* ... */ @} - if (raised & FE_INVALID) @{ /* ... */ @} - /* ... */ + if (raised & FE_OVERFLOW) @{ /* @dots{} */ @} + if (raised & FE_INVALID) @{ /* @dots{} */ @} + /* @dots{} */ @} @end smallexample @@ -2396,8 +2396,8 @@ or to the largest representable value if the floating-point format doesn't support infinities. You can prepend a @code{"+"} or @code{"-"} to specify the sign. Case is ignored when scanning these strings. -The strings @code{"nan"} and @code{"nan(@var{chars...})"} are converted -to NaN. Again, case is ignored. If @var{chars...} are provided, they +The strings @code{"nan"} and @code{"nan(@var{chars@dots{}})"} are converted +to NaN. Again, case is ignored. If @var{chars@dots{}} are provided, they are used in some unspecified fashion to select a particular representation of NaN (there can be several). diff --git a/manual/charset.texi b/manual/charset.texi index 4fb58d1cac..2ebde7d275 100644 --- a/manual/charset.texi +++ b/manual/charset.texi @@ -177,9 +177,9 @@ code like @smallexample @{ int c; - ... + @dots{} while ((c = getc (fp)) < 0) - ... + @dots{} @} @end smallexample @@ -190,9 +190,9 @@ are used: @smallexample @{ wint_t c; - ... + @dots{} while ((c = wgetc (fp)) != WEOF) - ... + @dots{} @} @end smallexample @@ -437,7 +437,7 @@ problem: while (! feof (fp)) @{ fread (&buf[len], 1, MB_CUR_MAX - len, fp); - /* @r{... process} buf */ + /* @r{@dots{} process} buf */ len -= used; @} @} @@ -491,7 +491,7 @@ clearing the whole variable with code such as follows: mbstate_t state; memset (&state, '\0', sizeof (state)); /* @r{from now on @var{state} can be used.} */ - ... + @dots{} @} @end smallexample @@ -523,7 +523,7 @@ Code using @code{mbsinit} often looks similar to this: mbstate_t state; memset (&state, '\0', sizeof (state)); /* @r{Use @var{state}.} */ - ... + @dots{} if (! mbsinit (&state)) @{ /* @r{Emit code to return to initial state.} */ @@ -531,7 +531,7 @@ Code using @code{mbsinit} often looks similar to this: const wchar_t *srcp = empty; wcsrtombs (outbuf, &srcp, outbuflen, &state); @} - ... + @dots{} @} @end smallexample @@ -911,7 +911,7 @@ this solution is unsuitable, there is a very slow but more accurate solution. @smallexample - ... + @dots{} if (len < MB_CUR_LEN) @{ mbstate_t temp_state; @@ -925,7 +925,7 @@ solution. return NULL; @} @} - ... + @dots{} @end smallexample Here we perform the conversion that might overflow the buffer so that @@ -2395,7 +2395,7 @@ The @code{int __internal_use} element is mostly used together with if (!data->__internal_use && data->__invocation_counter == 0) /* @r{Emit prolog.} */ - ... + @dots{} @end smallexample This element must never be modified. @@ -2708,7 +2708,7 @@ gconv (struct __gconv_step *step, struct __gconv_step_data *data, @{ struct __gconv_step *next_step = step + 1; struct __gconv_step_data *next_data = data + 1; - ... + @dots{} @end smallexample The @code{next_step} pointer references the next step information and diff --git a/manual/ctype.texi b/manual/ctype.texi index 593f7f3a0b..1117363a4b 100644 --- a/manual/ctype.texi +++ b/manual/ctype.texi @@ -625,7 +625,7 @@ is_in_class (int c, const char *class) return isalpha (c); if (strcmp (class, "cntrl") == 0) return iscntrl (c); - ... + @dots{} return 0; @} @end smallexample diff --git a/manual/filesys.texi b/manual/filesys.texi index a74f32d9fe..0f127467a4 100644 --- a/manual/filesys.texi +++ b/manual/filesys.texi @@ -453,7 +453,7 @@ Code to call @code{readdir_r} could look like this: @} u; if (readdir_r (dir, &u.d, &res) == 0) - ... + @dots{} @end smallexample @end deftypefun @@ -1501,7 +1501,7 @@ modify the attributes of a file. and what their values mean. * Reading Attributes:: How to read the attributes of a file. * Testing File Type:: Distinguishing ordinary files, - directories, links... + directories, links@dots{} * File Owner:: How ownership for new files is determined, and how to change it. * Permission Bits:: How information about a file's access diff --git a/manual/install.texi b/manual/install.texi index afadcdbc10..a8f003d81a 100644 --- a/manual/install.texi +++ b/manual/install.texi @@ -45,7 +45,7 @@ GNU Make, and possibly others. @xref{Tools for Compilation}, below. GNU libc can be compiled in the source directory, but we strongly advise building it in a separate build directory. For example, if you have unpacked -the glibc sources in @file{/src/gnu/glibc-2.2.0}, create a directory +the glibc sources in @file{/src/gnu/glibc-2.3}, create a directory @file{/src/gnu/glibc-build} to put the object files in. This allows removing the whole build directory in case an error occurs, which is the safest way to get a fresh start and should always be done. @@ -54,7 +54,7 @@ From your object directory, run the shell script @file{configure} located at the top level of the source tree. In the scenario above, you'd type @smallexample -$ ../glibc-2.2.0/configure @var{args...} +$ ../glibc-2.3/configure @var{args@dots{}} @end smallexample Please note that even if you're building in a separate build directory, @@ -64,9 +64,9 @@ directory, especially some files in the manual subdirectory. @noindent @code{configure} takes many options, but you can get away with knowing only two: @samp{--prefix} and @samp{--enable-add-ons}. The -@code{--prefix} option tells @code{configure} where you want glibc +@code{--prefix} option tells @code{configure} where you want glibc installed. This defaults to @file{/usr/local}. The -@samp{--enable-add-ons} option tells @code{configure} to use all the +@samp{--enable-add-ons} option tells @code{configure} to use all the add-on bundles it finds in the source directory. Since important functionality is provided in add-ons, you should always specify this option. diff --git a/manual/locale.texi b/manual/locale.texi index f477ac8e30..e3e0563a36 100644 --- a/manual/locale.texi +++ b/manual/locale.texi @@ -1201,7 +1201,7 @@ least also in the IBM AIX library. This function would normally be used like this: @smallexample - ... + @dots{} /* @r{Use a safe default.} */ _Bool doit = false; diff --git a/manual/memory.texi b/manual/memory.texi index e64dc8d9dc..c840e70829 100644 --- a/manual/memory.texi +++ b/manual/memory.texi @@ -751,7 +751,7 @@ End with a line saying just "end". >call mcheck(0) >continue >end -(gdb) ... +(gdb) @dots{} @end smallexample This will however only work if no initialization function of any object @@ -1003,7 +1003,7 @@ my_free_hook (void *ptr, const void *caller) main () @{ - ... + @dots{} @} @end smallexample diff --git a/manual/resource.texi b/manual/resource.texi index 3beb939006..9d2e17bed4 100644 --- a/manual/resource.texi +++ b/manual/resource.texi @@ -546,7 +546,7 @@ any one time is equal to the number of CPUs, you can easily extrapolate the information. The functions described in this section are all defined by the POSIX.1 -and POSIX.1b standards (the @code{sched...} functions are POSIX.1b). +and POSIX.1b standards (the @code{sched@dots{}} functions are POSIX.1b). However, POSIX does not define any semantics for the values that these functions get and set. In this chapter, the semantics are based on the Linux kernel's implementation of the POSIX standard. As you will see, @@ -656,7 +656,7 @@ the high priority process group. All the priority in the world won't stop an interrupt handler from running and delivering a signal to the process if you hit Control-C. -Some systems use absolute priority as a means of allocating a fixed +Some systems use absolute priority as a means of allocating a fixed percentage of CPU time to a process. To do this, a super high priority privileged process constantly monitors the process' CPU usage and raises its absolute priority when the process isn't getting its entitled share diff --git a/manual/startup.texi b/manual/startup.texi index 35ddbc4904..5ccb78b958 100644 --- a/manual/startup.texi +++ b/manual/startup.texi @@ -657,7 +657,7 @@ Example: #include #include -... +@dots{} int rc; @@ -677,7 +677,7 @@ following preferable code: #include #include -... +@dots{} int rc; diff --git a/manual/stdio.texi b/manual/stdio.texi index 05ecab042e..39fd4fb123 100644 --- a/manual/stdio.texi +++ b/manual/stdio.texi @@ -497,7 +497,7 @@ sometimes not possible): @smallexample FILE *fp; @{ - ... + @dots{} flockfile (fp); fputs ("This is test number ", fp); fprintf (fp, "%d\n", test); @@ -2450,7 +2450,7 @@ For example: @smallexample #define myprintf(a, b, c, d, e, rest...) \ - printf (mytemplate , ## rest...) + printf (mytemplate , ## rest) @end smallexample @noindent @@ -5295,7 +5295,7 @@ the following in the environment before calling the @code{fmtmsg} function the first time: @smallexample -MSGVERB=@var{keyword}[:@var{keyword}[:...]] +MSGVERB=@var{keyword}[:@var{keyword}[:@dots{}]] @end smallexample Valid @var{keyword}s are @code{label}, @code{severity}, @code{text}, @@ -5314,7 +5314,7 @@ described above are available. Any other numeric value would make If the user puts @code{SEV_LEVEL} with a format like @smallexample -SEV_LEVEL=[@var{description}[:@var{description}[:...]]] +SEV_LEVEL=[@var{description}[:@var{description}[:@dots{}]]] @end smallexample @noindent diff --git a/manual/time.texi b/manual/time.texi index 9744982a04..645c876287 100644 --- a/manual/time.texi +++ b/manual/time.texi @@ -1435,7 +1435,7 @@ character, not the number of bytes. Also the format string @var{template} is a wide character string. Since all characters needed to specify the format string are in the basic character set it is portably possible to write format strings in the C -source code using the @code{L"..."} notation. The parameter +source code using the @code{L"@dots{}"} notation. The parameter @var{brokentime} has the same meaning as in the @code{strftime} call. The @code{wcsftime} function supports the same flags, modifiers, and