-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Rollup of 9 pull requests #74242
Rollup of 9 pull requests #74242
Commits on Jun 25, 2020
-
Modify type names on MSVC to make tuples .natvis compatible.
- Mangles (T0, T1) as tuple<T0, T1>, possibly unblocking rust-lang#70052 "Update hashbrown to 0.8.0" - Prettifies Rust tuples similar to VS2017's std::tuple - Improves debuginfo test coverage
Configuration menu - View commit details
-
Copy full SHA for f8eb81b - Browse repository at this point
Copy the full SHA f8eb81bView commit details -
debuginfo: Define int/float types in terms of MSVC-recognized types.
PDB debug information doesn't appear to be emitted for basic types. By defining u32 as a typedef for unsigned __int32 when targeting MSVC, we allow CDB and other debuggers to recognize "u32" as a type/expression. This in turn unblocks rust-lang#70052 "Update hashbrown to 0.8.0" by allowing $T1 ..= $T3 to resolve, which would otherwise fail to resolve when builtin types fail to parse.
Configuration menu - View commit details
-
Copy full SHA for 24a728a - Browse repository at this point
Copy the full SHA 24a728aView commit details
Commits on Jul 8, 2020
-
Fix cross-compilation of LLVM to aarch64 Windows targets
When cross-compiling, the LLVM build system recurses to build tools that need to run on the host system. However, since we pass cmake defines to set the compiler and target, LLVM still compiles these tools for the target system, rather than the host. The tools then fail to execute during the LLVM build. This change sets defines for the tools that need to run on the host (llvm-nm, llvm-tablegen, and llvm-config), so that the LLVM build does not attempt to build them, and instead relies on the tools already built. If compiling with clang-cl, this change also adds the `--target` option to specify the target triple. MSVC compilers do not require this, since there is a separate compiler binary for cross-compilation.
Configuration menu - View commit details
-
Copy full SHA for 59f979f - Browse repository at this point
Copy the full SHA 59f979fView commit details -
linker: illumos ld does not support --eh-frame-hdr
As of rust-lang#73564, the --eh-frame-hdr flag is unconditionally passed to linkers on many platforms. The illumos link editor does not currently support this flag. The linker machinery in the Rust toolchain currently seems to use the (potentially cross-compiled) target to choose linker flags, rather than looking at what might be running on the build system. Disabling the flag for all illumos/Solaris targets seems like the best we can do for now without more serious surgery.
Configuration menu - View commit details
-
Copy full SHA for 7fb421b - Browse repository at this point
Copy the full SHA 7fb421bView commit details
Commits on Jul 9, 2020
-
Configuration menu - View commit details
-
Copy full SHA for 520fb92 - Browse repository at this point
Copy the full SHA 520fb92View commit details -
Configuration menu - View commit details
-
Copy full SHA for 6864546 - Browse repository at this point
Copy the full SHA 6864546View commit details -
Configuration menu - View commit details
-
Copy full SHA for a9b6476 - Browse repository at this point
Copy the full SHA a9b6476View commit details -
Enforce the static symbol order.
By making the proc macro abort if any symbols are out of order. The commit also changes the proc macro collect multiple errors (of order or duplicated symbols) and prints them at the end, which is useful if you have multiple errors.
Configuration menu - View commit details
-
Copy full SHA for de3f2d1 - Browse repository at this point
Copy the full SHA de3f2d1View commit details
Commits on Jul 10, 2020
-
Rename
sym::item_context
assym::ItemContext
.Because it represents the symbol `ItemContext`, and `sym` identifiers are supposed to match the actual symbol whenever possible.
Configuration menu - View commit details
-
Copy full SHA for 714b6ec - Browse repository at this point
Copy the full SHA 714b6ecView commit details -
Minor refactor for rustc_resolve diagnostics match
Use `matches!` instead of old `if let`
Configuration menu - View commit details
-
Copy full SHA for 1fb0ed0 - Browse repository at this point
Copy the full SHA 1fb0ed0View commit details
Commits on Jul 11, 2020
-
Configuration menu - View commit details
-
Copy full SHA for dd872be - Browse repository at this point
Copy the full SHA dd872beView commit details -
Configuration menu - View commit details
-
Copy full SHA for b929f72 - Browse repository at this point
Copy the full SHA b929f72View commit details -
Configuration menu - View commit details
-
Copy full SHA for f5de23b - Browse repository at this point
Copy the full SHA f5de23bView commit details -
Rollup merge of rust-lang#72920 - oli-obk:const_transmute, r=RalfJung
Stabilize `transmute` in constants and statics but not const fn cc rust-lang#53605 (leaving issue open so we can add `transmute` to `const fn` later) Previous attempt: rust-lang#64011 r? @RalfJung cc @rust-lang/wg-const-eval
Configuration menu - View commit details
-
Copy full SHA for 62c3d99 - Browse repository at this point
Copy the full SHA 62c3d99View commit details -
Rollup merge of rust-lang#73715 - MaulingMonkey:pr-natvis-tuples, r=A…
…manieu debuginfo: Mangle tuples to be natvis friendly, typedef basic types These changes are meant to unblock rust-lang#70052 "Update hashbrown to 0.8.0" by allowing the use of `tuple<u64, u64>` as a .natvis expression in MSVC style debuggers (MSVC, WinDbg, CDB, etc.) * f8eb81b does the actual mangling of `(u64, u64)` -> `tuple<u64, 64>` * 24a728a allows `u64` to resolve (fixing `$T1` / `$T2` when used to visualize `HashMap<u64, u64, ...>`)
Configuration menu - View commit details
-
Copy full SHA for 670a8fb - Browse repository at this point
Copy the full SHA 670a8fbView commit details -
Rollup merge of rust-lang#74116 - arlosi:aarch64build, r=pietroalbini
Fix cross compilation of LLVM to aarch64 Windows targets When cross-compiling, the LLVM build system recurses to build tools that need to run on the host system. However, since we pass cmake defines to set the compiler and target, LLVM still compiles these tools for the target system, rather than the host. The tools then fail to execute during the LLVM build. This change sets defines for the tools that need to run on the host (llvm-nm, llvm-tablegen, and llvm-config), so that the LLVM build does not attempt to build them, and instead relies on the tools already built. If compiling with clang-cl, adds the `--target` option to specify the target triple. MSVC compilers do not require this, since there is a separate compiler binary for each cross-compilation target. Related issue: rust-lang#72881 Requires LLVM change: rust-lang/llvm-project#67
Configuration menu - View commit details
-
Copy full SHA for 95314f2 - Browse repository at this point
Copy the full SHA 95314f2View commit details -
Rollup merge of rust-lang#74167 - jclulow:illumos-linker-eh-frame-hdr…
…-fix, r=petrochenkov linker: illumos ld does not support --eh-frame-hdr As of rust-lang#73564, the --eh-frame-hdr flag is unconditionally passed to linkers on many platforms. The illumos link editor does not currently support this flag. The linker machinery in the Rust toolchain currently seems to use the (potentially cross-compiled) target to choose linker flags, rather than looking at what might be running on the build system. Disabling the flag for all illumos/Solaris targets seems like the best we can do for now without more serious surgery.
Configuration menu - View commit details
-
Copy full SHA for f9389bc - Browse repository at this point
Copy the full SHA f9389bcView commit details -
Rollup merge of rust-lang#74168 - JohnTitor:help-for-in-band-lifetime…
…s, r=petrochenkov Add a help to use `in_band_lifetimes` in nightly Fixes rust-lang#73775
Configuration menu - View commit details
-
Copy full SHA for 212ce2f - Browse repository at this point
Copy the full SHA 212ce2fView commit details -
Rollup merge of rust-lang#74197 - estebank:self-sugg, r=petrochenkov
Reword incorrect `self` token suggestion
Configuration menu - View commit details
-
Copy full SHA for 5ef9245 - Browse repository at this point
Copy the full SHA 5ef9245View commit details -
Rollup merge of rust-lang#74203 - nnethercote:enforce-static-symbol-o…
…rder, r=petrochenkov Enforce the static symbol order. By making the proc macro abort if any symbols are out of order. The commit also changes the proc macro collect multiple errors (of order or duplicated symbols) and prints them at the end, which is useful if you have multiple errors. r? @petrochenkov
Configuration menu - View commit details
-
Copy full SHA for f5ee28f - Browse repository at this point
Copy the full SHA f5ee28fView commit details -
Rollup merge of rust-lang#74213 - pickfire:patch-1, r=jonas-schievink
Minor refactor for rustc_resolve diagnostics match Use `matches!` instead of old `if let`
Configuration menu - View commit details
-
Copy full SHA for d1f886d - Browse repository at this point
Copy the full SHA d1f886dView commit details -
Rollup merge of rust-lang#74240 - da-x:fix-74081, r=Manishearth
Fix rust-lang#74081 and add the test case from rust-lang#74236
Configuration menu - View commit details
-
Copy full SHA for cc1ecf3 - Browse repository at this point
Copy the full SHA cc1ecf3View commit details