rust/compiler/rustc_codegen_llvm/src, branch 1.72.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.72.02023-07-06T08:10:42+00:00Auto merge of #113377 - BoxyUwU:move_ty_ctors_to_ty, r=compiler-errors2023-07-06T08:10:42+00:00borsbors@rust-lang.org2023-07-06T08:10:42+00:00urn:sha1:4dd1719b3406d80f539d2f49e9842f3563908632
Move `TyCtxt::mk_x` to `Ty::new_x` where applicable
Part of rust-lang/compiler-team#616
turns out there's a lot of places we construct `Ty` this is a ridiculously huge PR :S
r? `@oli-obk`
Rollup merge of #113334 - fmease:revert-lexing-c-str-lits, r=compiler-errors2023-07-06T01:20:33+00:00fee1-deadent3rm4n@gmail.com2023-07-06T01:20:33+00:00urn:sha1:1830b80c2daf5b03d45ec69289e15b25cee97c7f
Revert the lexing of `c"…"` string literals
Fixes \[after beta-backport\] #113235.
Further progress is tracked in #113333.
This PR *manually* reverts parts of #108801 (since a git-revert would've been too coarse-grained & messy)
and git-reverts #111647.
CC `@fee1-dead` (#108801) `@klensy` (#111647)
r? `@compiler-errors`
`@rustbot` label F-c_str_literals beta-nominated
Rollup merge of #112791 - WaffleLapkin:wag_the_llvm, r=cuviper2023-07-06T01:20:31+00:00fee1-deadent3rm4n@gmail.com2023-07-06T01:20:31+00:00urn:sha1:e461502e06b171c05d4730b4d1a2846a1e5847fa
llvm ffi: Expose `CallInst->setTailCallKind`
This is needed for the explicit tail calls experiment.
Move `TyCtxt::mk_x` to `Ty::new_x` where applicable2023-07-05T19:27:07+00:00Boxysupbscripter@gmail.com2023-07-05T19:13:26+00:00urn:sha1:12138b8e5e840b7446a0893e3cb02a9c05095930Revert "use new c literals instead of cstr! macro"2023-07-05T11:11:27+00:00León Orell Valerian Liehrme@fmease.dev2023-07-04T17:53:44+00:00urn:sha1:3788b7ab32a6398e7563557f7b32f741f43704a3
This reverts commit a17561ffc90c900cb7d0e96b00c6381244764ef7.
Move `coverageinfo::ffi` and `coverageinfo::map` out of SSA2023-07-05T10:40:40+00:00ZalatharZalathar@users.noreply.github.com2023-07-05T08:04:58+00:00urn:sha1:cb570d6bc1251f32a07d8ce173dc735be78a325fRemove trait `CoverageInfoMethods`, since non-LLVM backends don't need it2023-07-05T10:40:40+00:00ZalatharZalathar@users.noreply.github.com2023-07-05T07:56:10+00:00urn:sha1:9c430d38cf10ec3fab459be00e87057e5cce55b0
These methods are only ever called from within `rustc_codegen_llvm`, so they
can just be declared there as well.
Narrow trait `CoverageInfoBuilderMethods` down to just one method2023-07-05T10:40:39+00:00ZalatharZalathar@users.noreply.github.com2023-07-05T07:39:40+00:00urn:sha1:4169d0f756dde8b3e692610bddb3c948c5cd53ea
This effectively inlines most of `FunctionCx::codegen_coverage` into the LLVM
implementation of `CoverageInfoBuilderMethods`.
Auto merge of #113040 - Kobzol:llvm-remark-streamer, r=tmiasko2023-07-02T12:48:44+00:00borsbors@rust-lang.org2023-07-02T12:48:44+00:00urn:sha1:131a03664ef90d6443dfb567ac19e5466baa937f
Add `-Zremark-dir` unstable flag to write LLVM optimization remarks to YAML
This PR adds an option for `rustc` to emit LLVM optimization remarks to a set of YAML files, which can then be digested by existing tools, like https://github.com/OfekShilon/optview2. When `-Cremark-dir` is passed, and remarks are enabled (`-Cremark=all`), the remarks will be now written to the specified directory, **instead** of being printed to standard error output. The files are named based on the CGU from which they are being generated.
Currently, the remarks are written using the LLVM streaming machinery, directly in the diagnostics handler. It seemed easier than going back to Rust and then form there back to C++ to use the streamer from the diagnostics handler. But there are many ways to implement this, of course, so I'm open to suggestions :)
I included some comments with questions into the code. Also, I'm not sure how to test this.
r? `@tmiasko`
Add `rustc` option to output LLVM optimization remarks to YAML files2023-07-02T11:41:36+00:00Jakub Beránekberykubik@gmail.com2023-06-25T21:39:02+00:00urn:sha1:62728c7aaff0441b12057de8f1be620feb96652c