1. 31 8月, 2016 1 次提交
    • R
      restore _Noreturn to __assert_fail · e738b8cb
      Rich Felker 提交于
      this reverts commit 2c1f8fd5. without
      the _Noreturn attribute, the compiler cannot use asserts to perform
      reachability/range analysis. this leads to missed optimizations and
      spurious warnings.
      
      the original backtrace problem that prompted the removal of _Noreturn
      was not clearly documented at the time, but it seems to happen only
      when libc was built without -g, which also breaks many other
      backtracing cases.
      e738b8cb
  2. 12 2月, 2016 1 次提交
  3. 27 8月, 2014 1 次提交
  4. 05 1月, 2013 1 次提交
  5. 17 10月, 2012 1 次提交
  6. 08 9月, 2012 1 次提交
    • R
      default features: make musl usable without feature test macros · c1a9658b
      Rich Felker 提交于
      the old behavior of exposing nothing except plain ISO C can be
      obtained by defining __STRICT_ANSI__ or using a compiler option (such
      as -std=c99) that predefines it. the new default featureset is POSIX
      with XSI plus _BSD_SOURCE. any explicit feature test macros will
      inhibit the default.
      
      installation docs have also been updated to reflect this change.
      c1a9658b
  7. 07 9月, 2012 1 次提交
    • R
      further use of _Noreturn, for non-plain-C functions · 0c05bd3a
      Rich Felker 提交于
      note that POSIX does not specify these functions as _Noreturn, because
      POSIX is aligned with C99, not the new C11 standard. when POSIX is
      eventually updated to C11, it will almost surely give these functions
      the _Noreturn attribute. for now, the actual _Noreturn keyword is not
      used anyway when compiling with a c99 compiler, which is what POSIX
      requires; the GCC __attribute__ is used instead if it's available,
      however.
      
      in a few places, I've added infinite for loops at the end of _Noreturn
      functions to silence compiler warnings. presumably
      __buildin_unreachable could achieve the same thing, but it would only
      work on newer GCCs and would not be portable. the loops should have
      near-zero code size cost anyway.
      
      like the previous _Noreturn commit, this one is based on patches
      contributed by philomath.
      0c05bd3a
  8. 12 2月, 2011 1 次提交