rust/compiler/rustc_codegen_llvm/src/debuginfo, branch 1.84.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.84.02024-11-19T13:19:09+00:00When the required discriminator value exceeds LLVM's limits, drop the debug info for the function instead of panicking.2024-11-19T13:19:09+00:00Kyle Hueykhuey@kylehuey.com2024-11-19T02:48:10+00:00urn:sha1:f5b023bd9cf43803a6d39b101c54a98cb7e7da7c
The maximum discriminator value LLVM can currently encode is 2^12. If macro use
results in more than 2^12 calls to the same function attributed to the same
callsite, and those calls are MIR-inlined, we will require more than the maximum
discriminator value to completely represent the debug information. Once we reach
that point drop the debug info instead.
Honor collapse_debuginfo when dealing with MIR-inlined functions inside macros.2024-11-19T13:18:56+00:00Kyle Hueykhuey@kylehuey.com2024-11-19T02:16:22+00:00urn:sha1:1e4ebb0ccdffe4a8ddb15cb8e95bef3b905f045b
The test relies on the fact that inlining more than 2^12 calls at the same
callsite will trigger a panic (and after the following commit, a warning) due to
LLVM limitations but with collapse_debuginfo the callsites should not be the
same.
use `TypingEnv` when no `infcx` is available2024-11-18T09:38:56+00:00lcnrrust@lcnr.de2024-11-15T12:53:31+00:00urn:sha1:9cba14b95bb07a5b31ed1aac2bf4eadd248232da
the behavior of the type system not only depends on the current
assumptions, but also the currentnphase of the compiler. This is
mostly necessary as we need to decide whether and how to reveal
opaque types. We track this via the `TypingMode`.
Rollup merge of #132702 - 1c3t3a:issue-132615, r=rcvalle2024-11-12T22:26:41+00:00Matthias Krügermatthias.krueger@famsik.de2024-11-12T22:26:41+00:00urn:sha1:bd79fe7a94b8191ef580db7789fc55291eb825f1
CFI: Append debug location to CFI blocks
Currently we're not appending debug locations to the inserted CFI blocks. This shows up in #132615 and #100783. This change fixes that by passing down the debug location to the CFI type-test generation and appending it to the blocks.
Credits also belong to `@jakos-sec` who worked with me on this.
CFI: Append debug location to CFI blocks2024-11-11T09:17:43+00:00Bastian Kerstingbkersting@google.com2024-11-08T08:51:19+00:00urn:sha1:c2102259a04dd9ede1e7faf01daa0dfcb948c214Add discriminators to DILocations when multiple functions are inlined into a single point.2024-11-09T16:01:31+00:00Kyle Hueykhuey@kylehuey.com2024-11-04T19:38:14+00:00urn:sha1:1dc106121b62562ead6e7d612fa136dc4b35cd5d
LLVM does not expect to ever see multiple dbg_declares for the same variable at the same
location with different values. proc-macros make it possible for arbitrary code,
including multiple calls that get inlined, to happen at any given location in the source
code. Add discriminators when that happens so these locations are different to LLVM.
This may interfere with the AddDiscriminators pass in LLVM, which is added by the
unstable flag -Zdebug-info-for-profiling.
Fixes #131944
compiler: Directly use rustc_abi in codegen2024-11-03T20:30:32+00:00Jubilee Youngworkingjubilee@gmail.com2024-11-03T02:32:52+00:00urn:sha1:b895bf4fdce434f394dbe0f4c57d4d0952cd13d7Remove support for `-Zprofile` (gcov-style coverage instrumentation)2024-10-30T22:09:25+00:00ZalatharZalathar@users.noreply.github.com2024-10-17T09:11:20+00:00urn:sha1:ce3e14a448e090abf494a91b87f124258c542d4cConsistently use safe wrapper function `set_section`2024-10-30T00:38:20+00:00ZalatharZalathar@users.noreply.github.com2024-10-29T23:02:46+00:00urn:sha1:65ff2a6ad71de45c848a622d86b6c74092e1b734Clean up FFI calls for setting module flags2024-10-29T10:40:34+00:00ZalatharZalathar@users.noreply.github.com2024-10-29T02:38:17+00:00urn:sha1:8d2ed4f0f3f79c402d2ebe585e0904baf4f8d634
- Don't rely on enum values defined by LLVM's C++ API
- Use safe wrapper functions instead of direct `unsafe` calls
- Consistently pass pointer/length strings instead of C strings