Skip to content

check for various issues in generated assembly #20823

@drdozer

Description

@drdozer

When writing high performance code, it becomes vitally important to know if loop bounds checking has been optimized out, or if arithmetic underflow/overflow checks have been proven to not be possible, for example. The way I do this currently is to copy-paste bits of code into godbolt, or to manually scan .d files in target. Is it within scope of rust-analyzer to track this kind of information and present it so that it can be highlighted in the IDE? There is probably a nicer way to test for the panic handlers being dead-code eliminated within the rust compilation, than to look at the final assembly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-featureCategory: feature request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions