Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rustc: Switch defaults from libgreen to libnative #12833

Merged
merged 3 commits into from Mar 22, 2014

Commits on Mar 21, 2014

  1. rustc: Switch defaults from libgreen to libnative

    The compiler will no longer inject libgreen as the default runtime for rust
    programs, this commit switches it over to libnative by default. Now that
    libnative has baked for some time, it is ready enough to start getting more
    serious usage as the default runtime for rustc generated binaries.
    
    We've found that there isn't really a correct decision in choosing a 1:1 or M:N
    runtime as a default for all applications, but it seems that a larger number of
    programs today would work more reasonable with a native default rather than a
    green default.
    
    With this commit come a number of bugfixes:
    
    * The main native task is now named "<main>"
    * The main native task has the stack bounds set up properly
    * #[no_uv] was renamed to #[no_start]
    * The core-run-destroy test was rewritten for both libnative and libgreen and
      one of the tests was modified to be more robust.
    * The process-detach test was locked to libgreen because it uses signal handling
    alexcrichton committed Mar 21, 2014
    Configuration menu
    Copy the full SHA
    ab1dd09 View commit details
    Browse the repository at this point in the history
  2. rand: Rewrite OsRng in Rust for windows

    This removes even more rust_builtin.c code, and allows us to more gracefully
    handle errors (not a process panic, but a task failure).
    alexcrichton committed Mar 21, 2014
    Configuration menu
    Copy the full SHA
    d2e99a0 View commit details
    Browse the repository at this point in the history
  3. rand: Fix a bug acquiring a context on windows

    The details can be found in the comment I wrote on the block in question, but
    the gist of it is that our usage of the TIB for a stack limit was causing
    CryptAcquireContext to fail, so we temporarily get around it by setting the
    stack limit to 0.
    alexcrichton committed Mar 21, 2014
    17 Configuration menu
    Copy the full SHA
    e7c4fb6 View commit details
    Browse the repository at this point in the history