mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2024-08-17 05:29:24 +00:00
Prepare the file to become IPO.h
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@3029 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
parent
378fb1df55
commit
03917ccb0c
@ -1,29 +1,21 @@
|
||||
//===- llvm/Transforms/CleanupGCCOutput.h - Cleanup GCC Output ---*- C++ -*--=//
|
||||
//===- llvm/Transforms/IPO.h - Interprocedural Optimiations -----*- C++ -*-===//
|
||||
//
|
||||
// These passes are used to cleanup the output of GCC. GCC's output is
|
||||
// unneccessarily gross for a couple of reasons. This pass does the following
|
||||
// things to try to clean it up:
|
||||
//
|
||||
// * Eliminate names for GCC types that we know can't be needed by the user.
|
||||
// * Eliminate names for types that are unused in the entire translation unit
|
||||
// * Fix various problems that we might have in PHI nodes and casts
|
||||
// * Link uses of 'void %foo(...)' to 'void %foo(sometypes)'
|
||||
//
|
||||
// Note: This code produces dead declarations, it is a good idea to run DCE
|
||||
// after this pass.
|
||||
//
|
||||
//===----------------------------------------------------------------------===//
|
||||
|
||||
#ifndef LLVM_TRANSFORMS_CLEANUPGCCOUTPUT_H
|
||||
#define LLVM_TRANSFORMS_CLEANUPGCCOUTPUT_H
|
||||
#ifndef LLVM_TRANSFORMS_IPO_H
|
||||
#define LLVM_TRANSFORMS_IPO_H
|
||||
|
||||
class Pass;
|
||||
|
||||
// CleanupGCCOutputPass - Perform all of the function body transformations.
|
||||
//===----------------------------------------------------------------------===//
|
||||
// createDeadTypeEliminationPass - Return a new pass that eliminates symbol
|
||||
// table entries for types that are never used.
|
||||
//
|
||||
Pass *createCleanupGCCOutputPass();
|
||||
Pass *createDeadTypeEliminationPass();
|
||||
|
||||
|
||||
//===----------------------------------------------------------------------===//
|
||||
// FunctionResolvingPass - Go over the functions that are in the module and
|
||||
// look for functions that have the same name. More often than not, there will
|
||||
// be things like:
|
||||
|
Loading…
Reference in New Issue
Block a user