Skip to content
Snippets Groups Projects
  1. Feb 02, 2019
  2. Jan 30, 2019
  3. Jan 21, 2019
  4. Dec 10, 2018
  5. Dec 07, 2018
  6. Nov 26, 2018
  7. Nov 24, 2018
  8. Nov 20, 2018
  9. Oct 30, 2018
  10. Aug 01, 2018
  11. Jul 29, 2018
  12. Jul 18, 2018
  13. Jul 17, 2018
  14. Jul 12, 2018
  15. Jun 01, 2018
  16. Apr 10, 2018
    • Mike Hommey's avatar
      Add PTHREAD_*_MUTEX_INITIALIZER_NP for glibc · d9013273
      Mike Hommey authored
      `pthread_mutex_t` varies across architectures, in several ways:
      - endianness alters the ordering of bytes, since the contents of the
        struct are larger than 8-bit.
      - its length varies.
      - the location of the mutex kind (`PTHREAD_MUTEX_RECURSIVE`,
        `PTHREAD_MUTEX_ERRORCHECK` or `PTHREAD_MUTEX_ADAPTIVE_NP`) varies
        between 32-bit and 64-bit: On 32-bit architectures, it is preceded by
        three int/unsigned int, while on 64-bit architectures, it is preceded
        by four of them.
      
      These initializers are only available from <pthread.h> when _GNU_SOURCE
      is defined.
      
      Relax the cfg_if check in ci/style.rs to allow #[cfg(target_endian)]
      tests.
      d9013273
  17. Mar 18, 2018
    • Francis Gagné's avatar
      Rename the dox configuration option to cross_platform_docs · 18341fd2
      Francis Gagné authored
      The libc crate is used as a dependency of the Rust compiler. Its build
      system passes `--cfg dox` to all crates when generating their
      documentation. libc's documentation is generated when the build system
      is asked to generate the compiler documentation because `cargo doc`
      automatically documents all dependencies.
      
      When the dox configuration option is enabled, libc disables its
      dependency on the core crate and provides the necessary definitions
      itself. The dox configuration option is meant for generating
      documentation for a multitude of targets even if the core crate for that
      target is not installed. However, when documenting the compiler, it's
      not necessary to do that; we can just use core or std as usual.
      
      This change is motivated by the changes made to the compiler in
      rust-lang/rust#48171. With these changes, it's necessary to provide
      implementations of the Clone and Copy traits for some primitive types in
      the library that defines these traits (previously, these implementations
      were provided by the compiler). Normally, these traits (and thus the
      implementations) are provided by core, so any crate that uses
      `#![no_core]` must now provide its own copy of the implementations.
      
      Because libc doesn't provide its own copy of the implementations yet,
      and because the compiler's build system passes `--cfg dox` to libc,
      generating the documentation for the compiler fails when generating
      documentation for libc. By renaming the configuration option, libc will
      use core or std and will thus have the necessary definitions for the
      documentation to be generated successfully.
      18341fd2
  18. Mar 15, 2018
  19. Feb 27, 2018
  20. Jan 18, 2018
  21. Nov 25, 2017
    • Alex Crichton's avatar
      Fix wasm tests · 69784400
      Alex Crichton authored
      Looks like `cargo test` is now trying to test too many files due to
      rust-lang/cargo#4750 so add a clause to the wrapper to ignore the bogus ones for
      now
      69784400
    • Alex Crichton's avatar
      Fix the FreeBSD target · 4d7fa243
      Alex Crichton authored
      It wasn't expecting a `*.d` file to exist, now it does.
      4d7fa243
  22. Nov 13, 2017
  23. Oct 31, 2017
  24. Oct 27, 2017
  25. Oct 24, 2017
  26. Oct 18, 2017
Loading