rust/compiler/rustc_codegen_llvm/src/debuginfo/metadata, branch try

Change `tag_field` to `FieldIdx` in `Variants::Multiple`

2025-06-04T06:42:21+00:00

It was already available as a generic parameter anyway, and it's not like we'll ever put a tag in the 5-billionth field.

AsyncDrop implementation using shim codegen of async_drop_in_place::{closure}, scoped async drop added.

2025-04-28T09:23:13+00:00

Rollup merge of #138599 - adwinwhite:recursive-overflow, r=wesleywiser

2025-04-18T03:17:53+00:00

avoid overflow when generating debuginfo for expanding recursive types Fixes #135093 Fixes #121538 Fixes #107362 Fixes #100618 Fixes #115994 The overflow happens because expanding recursive types keep creating new nested types when recurring into sub fields. I fixed that by returning an empty stub node when expanding recursion is detected.

Revert "Deduplicate template parameter creation"

2025-04-15T18:00:11+00:00

This reverts commit 6adc2c1fd6ecde7bf83c8b8fbc71f402ced87054.

Create a safe wrapper around `LLVMRustDIBuilderCreateMemberType`

2025-03-18T17:15:02+00:00

Avoid splitting up a layout

2025-03-18T17:01:09+00:00

Deduplicate template parameter creation

2025-03-17T16:32:21+00:00

Immediately create an `Option` instead of reallocating for it later

2025-03-17T16:17:48+00:00

fix(debuginfo): avoid overflow when handling expanding recursive type

2025-03-17T10:33:40+00:00

debuginfo: Set bitwidth appropriately in enum variant tags

2025-02-12T18:01:42+00:00

Previously, we unconditionally set the bitwidth to 128-bits, the largest an discrimnator would possibly be. Then, LLVM would cut down the constant by chopping off leading zeroes before emitting the DWARF. LLVM only supported 64-bit descriminators, so this would also have occasionally resulted in truncated data (or an assert) if more than 64-bits were used. LLVM added support for 128-bit enumerators in llvm/llvm-project#125578 That patchset also trusts the constant to describe how wide the variant tag is. As a result, we went from emitting tags that looked like: DW_AT_discr_value (0xfe) (`form1`) to emitting tags that looked like: DW_AT_discr_value (<0x10> fe ff ff ff 00 00 00 00 00 00 00 00 00 00 00 00 ) This makes the `DW_AT_discr_value` encode at the bitwidth of the tag, which: 1. Is probably closer to our intentions in terms of describing the data. 2. Doesn't invoke the 128-bit support which may not be supported by all debuggers / downstream tools. 3. Will result in smaller debug information.