Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

compiler: apply more accurate effects to return_type_tfunc #55338

Merged
merged 3 commits into from
Aug 10, 2024
Merged

compiler: apply more accurate effects to return_type_tfunc #55338

merged 3 commits into from
Aug 10, 2024

Commits on Aug 9, 2024

  1. compiler: apply more accurate effects to return_type_tfunc 

    In extreme cases, the compiler could mark this function for
concrete-eval, even though that is illegal unless the compiler has first
deleted this instruction. Otherwise the attempt to concrete-eval will
re-run the function repeatedly until it hits a StackOverflow.

Workaround to fix #55147
    @vtjnash @aviatesk
    vtjnash authored and aviatesk committed Aug 9, 2024
    Configuration menu
    Copy the full SHA
    775f53b View commit details
    Browse the repository at this point in the history

  2. setup new no_return_type_call effect and allow post-opt to refine it

    @aviatesk
    aviatesk committed Aug 9, 2024
    Configuration menu
    Copy the full SHA
    a7ee4fd View commit details
    Browse the repository at this point in the history

  3. simplify the effect bit name

    @aviatesk
    aviatesk committed Aug 9, 2024
    Configuration menu
    Copy the full SHA
    82b781c View commit details
    Browse the repository at this point in the history