LLVM  14.0.0git
ForceFunctionAttrs.h
Go to the documentation of this file.
1 //===-- ForceFunctionAttrs.h - Force function attrs for debugging ---------===//
2 //
3 // Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
4 // See https://llvm.org/LICENSE.txt for license information.
5 // SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
6 //
7 //===----------------------------------------------------------------------===//
8 /// \file
9 /// Super simple passes to force specific function attrs from the commandline
10 /// into the IR for debugging purposes.
11 //===----------------------------------------------------------------------===//
12 
13 #ifndef LLVM_TRANSFORMS_IPO_FORCEFUNCTIONATTRS_H
14 #define LLVM_TRANSFORMS_IPO_FORCEFUNCTIONATTRS_H
15 
16 #include "llvm/IR/PassManager.h"
17 
18 namespace llvm {
19 
20 /// Pass which forces specific function attributes into the IR, primarily as
21 /// a debugging tool.
22 struct ForceFunctionAttrsPass : PassInfoMixin<ForceFunctionAttrsPass> {
24 };
25 
26 /// Create a legacy pass manager instance of a pass to force function attrs.
28 
29 }
30 
31 #endif // LLVM_TRANSFORMS_IPO_FORCEFUNCTIONATTRS_H
llvm::PreservedAnalyses
A set of analyses that are preserved following a run of a transformation pass.
Definition: PassManager.h:155
llvm
This file implements support for optimizing divisions by a constant.
Definition: AllocatorList.h:23
M
We currently emits eax Perhaps this is what we really should generate is Is imull three or four cycles eax eax The current instruction priority is based on pattern complexity The former is more complex because it folds a load so the latter will not be emitted Perhaps we should use AddedComplexity to give LEA32r a higher priority We should always try to match LEA first since the LEA matching code does some estimate to determine whether the match is profitable if we care more about code then imull is better It s two bytes shorter than movl leal On a Pentium M
Definition: README.txt:252
llvm::PassInfoMixin
A CRTP mix-in to automatically provide informational APIs needed for passes.
Definition: PassManager.h:374
llvm::createForceFunctionAttrsLegacyPass
Pass * createForceFunctionAttrsLegacyPass()
Create a legacy pass manager instance of a pass to force function attrs.
llvm::ForceFunctionAttrsPass
Pass which forces specific function attributes into the IR, primarily as a debugging tool.
Definition: ForceFunctionAttrs.h:22
llvm::Module
A Module instance is used to store all the information related to an LLVM module.
Definition: Module.h:67
llvm::ForceFunctionAttrsPass::run
PreservedAnalyses run(Module &M, ModuleAnalysisManager &)
Definition: ForceFunctionAttrs.cpp:72
PassManager.h
llvm::Pass
Pass interface - Implemented by all 'passes'.
Definition: Pass.h:91
llvm::AnalysisManager
A container for analyses that lazily runs them and caches their results.
Definition: InstructionSimplify.h:44