squiid/rust
1
0
Fork 0
Code Issues Pull requests Projects Activity
rust/.gitmodules

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

44 lines
1.5 KiB
Text
Raw Normal View History

Use rust-installer for installation This is just a refactoring of the current installer so that Rust and Cargo use the same codebase. cc #16456
2014-11-21 23:45:45 +01:00
[submodule "src/rust-installer"]
Update to the oxidized rust-installer
2017-05-09 00:01:13 +02:00
path = src/tools/rust-installer
Correct .gitmodules Use proper URLs as given by Github. So far we relied on redirect by Github which is not guaranteed to work.
2015-12-25 19:51:04 +01:00
url = https://github.com/rust-lang/rust-installer.git
import nomicon submodule
2017-03-03 02:15:41 +01:00
[submodule "src/doc/nomicon"]
path = src/doc/nomicon
update submodules to rust-lang These are the repositories I've moved from rust-lang-nursery to rust-lang, so we should update the submodules too.
2019-10-30 14:37:05 +01:00
url = https://github.com/rust-lang/nomicon.git
Add Cargo as a submodule
2017-02-15 23:55:26 +01:00
[submodule "src/tools/cargo"]
Update stage0 bootstrap compiler We've got a freshly minted beta compiler, let's update to use that on nightly! This has a few other changes associated with it as well * A bump to the rustc version number (to 1.19.0) * Movement of the `cargo` and `rls` submodules to their "proper" location in `src/tools/{cargo,rls}`. Now that Cargo workspaces support the `exclude` option this can work. * Updates of the `cargo` and `rls` submodules to their master branches. * Tweak to the `src/stage0.txt` format to be more amenable for Cargo version numbers. On the beta channel Cargo will bootstrap from a different version than rustc (e.g. the version numbers are different), so we need different configuration for this. * Addition of `dev` as a readable key in the `src/stage0.txt` format. If present then stage0 compilers are downloaded from `dev-static.rust-lang.org` instead of `static.rust-lang.org`. This is added to accomodate our updated release process with Travis and AppVeyor.
2017-04-20 23:32:54 +02:00
path = src/tools/cargo
Unify all stage2 tools into a workspace This avoids double compiled Cargo. Hopefully this would speed up (extended) compilation for ~10m. Notes: when updating Cargo submodule, the replacement version may also need to be updated.
2017-04-30 01:11:58 +02:00
url = https://github.com/rust-lang/cargo.git
Always name git submodules by their paths.
2017-12-28 18:20:19 +01:00
[submodule "src/doc/reference"]
import reference submodule
2017-03-03 00:47:06 +01:00
path = src/doc/reference
update submodules to rust-lang These are the repositories I've moved from rust-lang-nursery to rust-lang, so we should update the submodules too.
2019-10-30 14:37:05 +01:00
url = https://github.com/rust-lang/reference.git
Always name git submodules by their paths.
2017-12-28 18:20:19 +01:00
[submodule "src/doc/book"]
Import submodule for the book. It's all in the external repository now.
2017-03-07 20:43:27 +01:00
path = src/doc/book
.gitmodules: use the official Git URL w/o redirect
2017-04-06 15:48:56 +02:00
url = https://github.com/rust-lang/book.git
Update stage0 bootstrap compiler We've got a freshly minted beta compiler, let's update to use that on nightly! This has a few other changes associated with it as well * A bump to the rustc version number (to 1.19.0) * Movement of the `cargo` and `rls` submodules to their "proper" location in `src/tools/{cargo,rls}`. Now that Cargo workspaces support the `exclude` option this can work. * Updates of the `cargo` and `rls` submodules to their master branches. * Tweak to the `src/stage0.txt` format to be more amenable for Cargo version numbers. On the beta channel Cargo will bootstrap from a different version than rustc (e.g. the version numbers are different), so we need different configuration for this. * Addition of `dev` as a readable key in the `src/stage0.txt` format. If present then stage0 compilers are downloaded from `dev-static.rust-lang.org` instead of `static.rust-lang.org`. This is added to accomodate our updated release process with Travis and AppVeyor.
2017-04-20 23:32:54 +02:00
[submodule "src/tools/rls"]
path = src/tools/rls
Update submodules to rust-lang
2020-01-25 09:58:10 +01:00
url = https://github.com/rust-lang/rls.git
Get the miri test suite to run inside the rustc dev environment
2017-08-28 16:54:50 +02:00
[submodule "src/tools/miri"]
path = src/tools/miri
update Cargo.lock and miri URL
2019-02-17 12:39:40 +01:00
url = https://github.com/rust-lang/miri.git
Adding RBE as a submodule #46194
2017-12-02 03:29:12 +01:00
[submodule "src/doc/rust-by-example"]
path = src/doc/rust-by-example
Add .git extension to submodule paths missing it Fixes a problem where submodules could not be cloned under some git configurations. Specifically, when url.git@github.com:.insteadOf = https://github.com/ is set.
2018-09-05 09:45:55 +02:00
url = https://github.com/rust-lang/rust-by-example.git
mv std libs to library/
2020-06-12 04:31:49 +02:00
[submodule "library/stdarch"]
path = library/stdarch
Update the stdarch submodule
2019-07-15 13:53:44 +02:00
url = https://github.com/rust-lang/stdarch.git
Move rustc-guide submodule to rustc-dev-guide
2020-03-10 21:22:25 +01:00
[submodule "src/doc/rustc-dev-guide"]
path = src/doc/rustc-dev-guide
url = https://github.com/rust-lang/rustc-dev-guide.git
Add the edition guide to doc.rust-lang.org
2018-11-30 15:36:49 +01:00
[submodule "src/doc/edition-guide"]
path = src/doc/edition-guide
update submodules to rust-lang These are the repositories I've moved from rust-lang-nursery to rust-lang, so we should update the submodules too.
2019-10-30 14:37:05 +01:00
url = https://github.com/rust-lang/edition-guide.git
Rebase to the llvm-project monorepo The new git submodule src/llvm-project is a monorepo replacing src/llvm and src/tools/{clang,lld,lldb}. This also serves as a rebase for these projects to the new 8.x branch from trunk. The src/llvm-emscripten fork is unchanged for now.
2019-01-16 18:59:03 +01:00
[submodule "src/llvm-project"]
path = src/llvm-project
url = https://github.com/rust-lang/llvm-project.git
Update LLVM submodule
2022-07-19 09:40:24 +02:00
branch = rustc/15.0-2022-08-09
Add embedded book
2019-01-19 04:52:39 +01:00
[submodule "src/doc/embedded-book"]
path = src/doc/embedded-book
update Cargo.lock and miri URL
2019-02-17 12:39:40 +01:00
url = https://github.com/rust-embedded/book.git
std: Switch from libbacktrace to gimli This commit is a proof-of-concept for switching the standard library's backtrace symbolication mechanism on most platforms from libbacktrace to gimli. The standard library's support for `RUST_BACKTRACE=1` requires in-process parsing of object files and DWARF debug information to interpret it and print the filename/line number of stack frames as part of a backtrace. Historically this support in the standard library has come from a library called "libbacktrace". The libbacktrace library seems to have been extracted from gcc at some point and is written in C. We've had a lot of issues with libbacktrace over time, unfortunately, though. The library does not appear to be actively maintained since we've had patches sit for months-to-years without comments. We have discovered a good number of soundness issues with the library itself, both when parsing valid DWARF as well as invalid DWARF. This is enough of an issue that the libs team has previously decided that we cannot feed untrusted inputs to libbacktrace. This also doesn't take into account the portability of libbacktrace which has been difficult to manage and maintain over time. While possible there are lots of exceptions and it's the main C dependency of the standard library right now. For years it's been the desire to switch over to a Rust-based solution for symbolicating backtraces. It's been assumed that we'll be using the Gimli family of crates for this purpose, which are targeted at safely and efficiently parsing DWARF debug information. I've been working recently to shore up the Gimli support in the `backtrace` crate. As of a few weeks ago the `backtrace` crate, by default, uses Gimli when loaded from crates.io. This transition has gone well enough that I figured it was time to start talking seriously about this change to the standard library. This commit is a preview of what's probably the best way to integrate the `backtrace` crate into the standard library with the Gimli feature turned on. While today it's used as a crates.io dependency, this commit switches the `backtrace` crate to a submodule of this repository which will need to be updated manually. This is not done lightly, but is thought to be the best solution. The primary reason for this is that the `backtrace` crate needs to do some pretty nontrivial filesystem interactions to locate debug information. Working without `std::fs` is not an option, and while it might be possible to do some sort of trait-based solution when prototyped it was found to be too unergonomic. Using a submodule allows the `backtrace` crate to build as a submodule of the `std` crate itself, enabling it to use `std::fs` and such. Otherwise this adds new dependencies to the standard library. This step requires extra attention because this means that these crates are now going to be included with all Rust programs by default. It's important to note, however, that we're already shipping libbacktrace with all Rust programs by default and it has a bunch of C code implementing all of this internally anyway, so we're basically already switching already-shipping functionality to Rust from C. * `object` - this crate is used to parse object file headers and contents. Very low-level support is used from this crate and almost all of it is disabled. Largely we're just using struct definitions as well as convenience methods internally to read bytes and such. * `addr2line` - this is the main meat of the implementation for symbolication. This crate depends on `gimli` for DWARF parsing and then provides interfaces needed by the `backtrace` crate to turn an address into a filename / line number. This crate is actually pretty small (fits in a single file almost!) and mirrors most of what `dwarf.c` does for libbacktrace. * `miniz_oxide` - the libbacktrace crate transparently handles compressed debug information which is compressed with zlib. This crate is used to decompress compressed debug sections. * `gimli` - not actually used directly, but a dependency of `addr2line`. * `adler32`- not used directly either, but a dependency of `miniz_oxide`. The goal of this change is to improve the safety of backtrace symbolication in the standard library, especially in the face of possibly malformed DWARF debug information. Even to this day we're still seeing segfaults in libbacktrace which could possibly become security vulnerabilities. This change should almost entirely eliminate this possibility whilc also paving the way forward to adding more features like split debug information. Some references for those interested are: * Original addition of libbacktrace - #12602 * OOM with libbacktrace - #24231 * Backtrace failure due to use of uninitialized value - #28447 * Possibility to feed untrusted data to libbacktrace - #21889 * Soundness fix for libbacktrace - #33729 * Crash in libbacktrace - #39468 * Support for macOS, never merged - ianlancetaylor/libbacktrace#2 * Performance issues with libbacktrace - #29293, #37477 * Update procedure is quite complicated due to how many patches we need to carry - #50955 * Libbacktrace doesn't work on MinGW with dynamic libs - #71060 * Segfault in libbacktrace on macOS - #71397 Switching to Rust will not make us immune to all of these issues. The crashes are expected to go away, but correctness and performance may still have bugs arise. The gimli and `backtrace` crates, however, are actively maintained unlike libbacktrace, so this should enable us to at least efficiently apply fixes as situations come up.
2020-05-13 23:22:37 +02:00
[submodule "library/backtrace"]
path = library/backtrace
url = https://github.com/rust-lang/backtrace-rs.git
Reference in a new issue Copy permalink