Skip to content

Tracking LLVM workarounds #100077

Open
Open
@workingjubilee

Description

@workingjubilee

This is a metabug for tracking the compiler's workarounds of LLVM's behavior that have resulted in the compiler implementing what one might refer to as "ugly hacks" to fix the behavior in question on our side. Logically, when the behavior is resolved and appropriate tests if any have been added, the issue can be closed, from Rust's perspective. Worse, leaving "fixed but not ideally" issues open makes it harder to sift through and prioritize problems. However, also logically, we also want to obtain various code improvements in the future, and not tracking them in some way makes it harder for us to find them again. Thus the purpose of this metabug is to allow observing these as a collective.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-LLVMArea: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.WG-llvmWorking group: LLVM backend code generationmetabugIssues about issues themselves ("bugs about bugs")

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions