search for: legacy_alwaysinline

...unctions remaining after it's done. 3. alwaysinline functions must never reach backend and can be rejected before machine code generation (in SelectionDAG?). As this changes the semantics of alwaysinline attribute in the IR, we would need to reserve a new attribute ID, rename the current ID to legacy_alwaysinline or something similar and only enforce the above properties on the new attribute. There is a proposed Clang patch here: http://reviews.llvm.org/D12087 The patch only implements the Clang codegen part of the proposal and does not do any of the backend improvements.