rust/compiler/rustc_codegen_llvm/src, branch 1.76.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.76.02024-01-12T10:27:00+00:00Revert "Auto merge of #113923 - DianQK:restore-no-builtins-lto, r=pnkfelix"2024-01-12T10:27:00+00:00DianQKdianqk@dianqk.net2024-01-12T10:27:00+00:00urn:sha1:251322ea3dedb68aa96c8e830d1dbddc07229912
This reverts commit 8c2b57721728233e074db69d93517614de338055, reversing
changes made to 9cf18e98f82d85fa41141391d54485b8747da46f.
Revert "Auto merge of #118568 - DianQK:no-builtins-symbols, r=pnkfelix"2024-01-12T10:26:42+00:00DianQKdianqk@dianqk.net2024-01-12T10:26:42+00:00urn:sha1:59ccbe306afe19197a1c8ec5553754ae7fbe2c8e
This reverts commit 503e129328080e924c0ddfca6abf4c2812580102, reversing
changes made to 0e7f91b75e7484a713e2f644212cfc1aa7478a28.
Fix fallout of making c_str_literals unstable again2024-01-02T22:57:56+00:00Wesley Wiserwesleywiser@microsoft.com2024-01-02T22:57:51+00:00urn:sha1:99aa435b701f6f679b36cbf7c794cfb701988b68Auto merge of #119069 - matthiaskrgr:rollup-xxk4m30, r=matthiaskrgr2023-12-18T08:03:22+00:00borsbors@rust-lang.org2023-12-18T08:03:22+00:00urn:sha1:e004adb5561b724ac18f5b24584648ca4e42b6ad
Rollup of 5 pull requests
Successful merges:
- #118852 (coverage: Skip instrumenting a function if no spans were extracted from MIR)
- #118905 ([AIX] Fix XCOFF metadata)
- #118967 (Add better ICE messages for some undescriptive panics)
- #119051 (Replace `FileAllocationInfo` with `FileEndOfFileInfo`)
- #119059 (Deny `~const` trait bounds in inherent impl headers)
r? `@ghost`
`@rustbot` modify labels: rollup
Rollup merge of #118852 - Zalathar:no-spans, r=cjgillot2023-12-18T07:08:22+00:00Matthias Krügermatthias.krueger@famsik.de2023-12-18T07:08:22+00:00urn:sha1:418ae3e9a066c33a28c02b7cde1748e022f5a32a
coverage: Skip instrumenting a function if no spans were extracted from MIR
The immediate symptoms of #118643 were fixed by #118666, but some users reported that their builds now encounter another coverage-related ICE:
```
error: internal compiler error: compiler/rustc_codegen_llvm/src/coverageinfo/mapgen.rs:98:17: A used function should have had coverage mapping data but did not: (...)
```
I was able to reproduce at least one cause of this error: if no relevant spans could be extracted from a function, but the function contains `CoverageKind::SpanMarker` statements, then codegen still thinks the function is instrumented and complains about the fact that it has no coverage spans.
This PR prevents that from happening in two ways:
- If we didn't extract any relevant spans from MIR, skip instrumenting the entire function and don't create a `FunctionCoverateInfo` for it.
- If coverage codegen sees a `CoverageKind::SpanMarker` statement, skip it early and avoid creating `func_coverage`.
---
Fixes #118850.
Rename many `DiagCtxt` and `EarlyDiagCtxt` locals.2023-12-18T05:06:22+00:00Nicholas Nethercoten.nethercote@gmail.com2023-12-18T00:15:13+00:00urn:sha1:f6aa418c9f616ae898d01082f8fe324927295d9cRename many `DiagCtxt` arguments.2023-12-18T05:06:22+00:00Nicholas Nethercoten.nethercote@gmail.com2023-12-17T23:15:45+00:00urn:sha1:f422dca3ae8b8a8c9a99b8e6ec0899e08dc072c3Rename `CodegenContext::create_diag_handler` as `CodegenContext::create_dcx`.2023-12-18T05:06:21+00:00Nicholas Nethercoten.nethercote@gmail.com2023-12-17T21:43:59+00:00urn:sha1:7c656bc05bdb39884bdc5e87b2ed870233289591Rename `Session::span_diagnostic` as `Session::dcx`.2023-12-18T05:06:21+00:00Nicholas Nethercoten.nethercote@gmail.com2023-12-17T19:21:26+00:00urn:sha1:09af8a667c0fa456bbe62fa462f4b0f42f2845ecRename `Handler` as `DiagCtxt`.2023-12-18T05:06:19+00:00Nicholas Nethercoten.nethercote@gmail.com2023-12-17T10:48:57+00:00urn:sha1:cde19c016e4608288a02f5bdec0b5330d474c26f