-
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 4 pull requests #95987
Rollup of 4 pull requests #95987
Conversation
When a `macro_rules! foo { ... }` invocation is compiled the name used is `foo`, not `macro_rules!`. This is different to all other macro invocations, and confused me when I was inserted debugging println statements for macro evaluation. This commit changes it to `macro_rules` (or just `macro`), which is what I expected. There are no externally visible changes.
The `Lrc` isn't necessary, neither is the `SmallVec`. Performance is changed negligibly, but the new code is simpler.
Co-authored-by: Guillaume Gomez <guillaume1.gomez@gmail.com>
… r=GuillaumeGomez rustdoc doctest: include signal number in exit status Related to rust-lang#95601
…aks, r=petrochenkov `parse_tt`: a few more tweaks r? `@petrochenkov`
…r=Mark-Simulacrum [bootstrap] Grab the right FileCheck binary for dist when cross-compiling. Fixes rust-lang#95862 We were using the target dir for all the other LLVM tools (`llvm-config`, `llvm-ar`, etc) but the build target dir for `FileCheck`. This meant for targets which are cross-compiled, we were copying the wrong binary.
…triplett Don't test -Cdefault-linker-libraries=yes when cross compiling. See rust-lang#95727 (comment) and the five comments below that. Unblocks rust-lang#95727.
@bors r+ rollup=never p=4 |
📌 Commit 550a510 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (52ca603): comparison url. Summary:
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Footnotes |
Visiting for weekly performance triage.
@rustbot label: +perf-regression-triaged |
Successful merges:
parse_tt
: a few more tweaks #95794 (parse_tt
: a few more tweaks)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup