1. 15 May, 2019 1 commit
  2. 20 Apr, 2019 1 commit
  3. 19 Apr, 2019 6 commits
  4. 14 Apr, 2019 3 commits
  5. 13 Apr, 2019 1 commit
  6. 12 Apr, 2019 5 commits
  7. 10 Apr, 2019 2 commits
  8. 07 Apr, 2019 2 commits
    • Jeremy Soller's avatar
      Get rid of duplicate code · 50a5e5cc
      Jeremy Soller authored
      50a5e5cc
    • Jeremy Soller's avatar
      Add Redox scheme prefix · 4d71257e
      Jeremy Soller authored
      Fixes for Redox Path handling
      
      Update to new system calls and enviromental variables
      
      Remove unused type parameter
      
      Don't forget to close executable file
      
      Interpret shebangs on redox
      
      This is no longer handled on the kernel side
      
      Fix for missing setenv/unsetenv
      
      Use mangled names for compiler builtins to avoid conflicts with relibc
      
      Another attempt to fix build issues
      
      WIP aarch64-unknown-redox support
      
      Untested.
      
      Introduce a target family for Redox
      
      The Redox base target spec located within the rustc source did not
      specify a 'target_family' attribute. However, the x86_64 specific target
      spec located within the redox source did.
      
      Now AArch64 could have done something similar but unfortunately can't
      since there are rust compiler mods needed to support Redox on AArch64
      which imply that any AArch64 target spec file in the Redox source shall
      be ignored in favour of the target spec within the rustc source.
      
      The target_family attribute is eventually translated into an environment
      variable called CARGO_CFG_TARGET_FAMILY whose presence can be tested by
      software built with the compiler generated from the target spec.
      
      Some crates expect this variable to contain something failing which they
      crash. Eg onig_sys within rust-onig. Since the Redox base target spec in
      the rustc source doesn't specify target_family for AArch64, such crates
      don't build.
      
      The solution is to introduce target_family in the Redox base
      target spec within the rustc source so both x86_64 and AArch64 have it
      defined by default. It is set to "redox".
      
      "unix" would perhaps be more preferable but using that breaks the rustc
      build which starts making incorrect assumptions about the support libs
      that Redox has.
      4d71257e
  9. 06 Apr, 2019 6 commits
    • bors's avatar
      Auto merge of #59710 - alexcrichton:llvm-9-compat, r=sanxiyn · 8159f389
      bors authored
      rustc: Start implementing compat with LLVM 9
      
      This commit doesn't actually migrate to LLVM 9, but it brings our own
      C++ bindings in line with LLVM 9 and able to compile against tip of
      tree. The changes made were:
      
      * The `MainSubprogram` flag for debuginfo moved between flag types.
      * Iteration of archive members was tweaked slightly and we have to
        construct the two iterators before constructing the returned
        `RustArchiveIterator` value.
      * The `getOrInsertFunction` binding now returns a wrapper which we use
        `getCallee()` on to get the value we're interested in.
      8159f389
    • bors's avatar
      Auto merge of #59745 - cwhakes:master, r=sanxiyn · 209b0b41
      bors authored
      Change `copytest` parameter name from `y` to `sign`
      
      This should help clarify ambiguity with whether `a.copysign(b)` applies the sign of `a` to `b` or `b` to `a`.
      
      r? @Centril
      209b0b41
    • bors's avatar
      Auto merge of #59744 - cuviper:output-errors, r=sanxiyn · 2982dbf8
      bors authored
      Show better errors for LLVM IR output
      
      I was trying to output LLVM IR directly to the console:
      
          $ rustc hello.rs --emit=llvm-ir -o /dev/stdout
          LLVM ERROR: IO failure on output stream: Bad file descriptor
      
      Now `LLVMRustPrintModule` returns an error, and we print:
      
          error: failed to write LLVM IR to /dev/stdout.hello.7rcbfp3g-cgu.0.rcgu.ll: Permission denied
      
      ... which is more informative.
      2982dbf8
    • bors's avatar
      Auto merge of #59723 - Zoxc:rem-noforce, r=michaelwoerister · b025802a
      bors authored
      Remove no_force from coherent_trait
      
      r? @michaelwoerister
      b025802a
    • Will Hakes's avatar
      350e492b
    • Josh Stone's avatar
      Show better errors for LLVM IR output · aafe2c6d
      Josh Stone authored
      I was trying to output LLVM IR directly to the console:
      
          $ rustc hello.rs --emit=llvm-ir -o /dev/stdout
          LLVM ERROR: IO failure on output stream: Bad file descriptor
      
      Now `LLVMRustPrintModule` returns an error, and we print:
      
          error: failed to write LLVM IR to /dev/stdout.hello.7rcbfp3g-cgu.0.rcgu.ll: Permission denied
      
      ... which is more informative.
      aafe2c6d
  10. 05 Apr, 2019 13 commits