Skip to content

Make codegen treat inline fns the same as regular fns in non-opt builds #54089

Open
Open
Make codegen treat inline fns the same as regular fns in non-opt builds#54089
Labels
A-codegenArea: Code generationA-incr-compArea: Incremental compilationC-optimizationCategory: An issue highlighting optimization opportunities or PRs implementing suchI-compiletimeIssue: Problems and improvements with respect to compile times.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.WG-compiler-performanceWorking group: Compiler PerformanceWG-llvmWorking group: LLVM backend code generation
@michaelwoerister

Description

@michaelwoerister
michaelwoerister
opened on Sep 9, 2018

See #53963 (comment) and following. There's no need to create private duplicates of #[inline] functions in debug builds, since we don't even run an inlining pass there.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-codegenArea: Code generationA-incr-compArea: Incremental compilationC-optimizationCategory: An issue highlighting optimization opportunities or PRs implementing suchI-compiletimeIssue: Problems and improvements with respect to compile times.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.WG-compiler-performanceWorking group: Compiler PerformanceWG-llvmWorking group: LLVM backend code generation

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions