Permalink
Browse files

Fix typos

  • Loading branch information...
jwilk authored and somasis committed Jan 15, 2018
1 parent ba753ec commit 56c03c68a3d107626595c1f6e7ed41aa059b2a85
Showing with 4 additions and 4 deletions.
  1. +1 −1 bugs-found-by-musl.md
  2. +1 −1 design-concepts.md
  3. +2 −2 faq.md
View
@@ -290,7 +290,7 @@
- isoc: underflow omission in annex f with FLT\_EVAL\_METHOD!=0 ([comp.lang.c discussion](https://groups.google.com/forum/#!topic/comp.std.c/oosKDrY28E8))
- glibc: fegetenv/fesetenv does not save/restore sse exception flags on i386
- gcc: peephole optimization on i386 (i64 &= -1ULL<<32; turns into "andl \$-1,4(%esp); movl \$0,(%esp)")
- gcc: optimization for fmod loop: superflous fldl/fstpl in loop
- gcc: optimization for fmod loop: superfluous fldl/fstpl in loop
- glibc, gnulib: invalid ld80 on i386 printf'd incorrectly, gnulib tests this case, but not correctly
- glibc: -lxnet fails (posix requirement)
- glibc vs linux: on microblaze struct elf\_prpsinfo does not match the in-kernel definition.
View
@@ -61,7 +61,7 @@ implementation.
Adapted from <http://www.openwall.com/lists/musl/2011/04/18/1>
The current thread cancellation design in musl is the second in a series of
designs to rememdy two critical flaws in the classic way cancellation is
designs to remedy two critical flaws in the classic way cancellation is
implemented by glibc and other libraries:
1. Cancellation can act after the syscall has returned successfully from
View
4 faq.md
@@ -204,8 +204,8 @@ error message suggests to do. See
To fix it, either update the in-tree gnulib (no idea how to do that), or use a
hack: each one of the gnulib function is triggered by a configure test, the
condition being either "libc doesnt have this function" or "this libc function
doesnt behave like GNUlib dictators want it to be". All of those configure
condition being either "libc doesn't have this function" or "this libc function
doesn't behave like GNUlib dictators want it to be". All of those configure
checks use a cache variable like "`gl_cv_func_isnanl_works=yes`" [bigger list].
So, you can prevent their code getting compiled in when you start configure with

0 comments on commit 56c03c6

Please sign in to comment.