search for: gettypealignment

...got the following errors: llvm[4]: Compiling Heuristic.cpp for Debug build (PIC) Heuristic.cpp: In function 'bool Wants8ByteAlignment(const llvm::Type*, unsigned int, const llvm::TargetData&)': Heuristic.cpp:77: error: 'const class llvm::TargetData' has no member named 'getTypeAlignment' There seem to be 3 methods in TargetData that are close to getTypeAlignment(): getTypeAlignmentABI (), getTypeAlignmentPref (), getTypeAlignmentShift (). Does anyone working on llvm-poolalloc know what method should be used. Thanks, Ryan

...> > llvm[4]: Compiling Heuristic.cpp for Debug build (PIC) > Heuristic.cpp: In function 'bool Wants8ByteAlignment(const llvm::Type*, > unsigned int, const llvm::TargetData&)': > Heuristic.cpp:77: error: 'const class llvm::TargetData' has no member > named 'getTypeAlignment' The getTypeAlignment method was renamed to getTypeAlignmentABI, it should be safe to make that substitution. -Chris > There seem to be 3 methods in TargetData that are close to > getTypeAlignment(): getTypeAlignmentABI (), getTypeAlignmentPref (), > getTypeAlignmentShift (). Does...

...g Heuristic.cpp for Debug build (PIC) >> Heuristic.cpp: In function 'bool Wants8ByteAlignment(const >> llvm::Type*, >> unsigned int, const llvm::TargetData&)': >> Heuristic.cpp:77: error: 'const class llvm::TargetData' has no member >> named 'getTypeAlignment' > > The getTypeAlignment method was renamed to getTypeAlignmentABI, it > should > be safe to make that substitution. > > -Chris > >> There seem to be 3 methods in TargetData that are close to >> getTypeAlignment(): getTypeAlignmentABI (), getTypeAlignmentPref...

...ristic.cpp for Debug build (PIC) >>> Heuristic.cpp: In function 'bool Wants8ByteAlignment(const llvm::Type*, >>> unsigned int, const llvm::TargetData&)': >>> Heuristic.cpp:77: error: 'const class llvm::TargetData' has no member >>> named 'getTypeAlignment' >> >> >> The getTypeAlignment method was renamed to getTypeAlignmentABI, it >> should >> be safe to make that substitution. >> >> -Chris >> >>> There seem to be 3 methods in TargetData that are close to >>> getTypeAlignment():...

...or Debug build (PIC) >>>>Heuristic.cpp: In function 'bool Wants8ByteAlignment(const llvm::Type*, >>>>unsigned int, const llvm::TargetData&)': >>>>Heuristic.cpp:77: error: 'const class llvm::TargetData' has no member >>>>named 'getTypeAlignment' >>> >>> >>>The getTypeAlignment method was renamed to getTypeAlignmentABI, it >>>should >>>be safe to make that substitution. >>> >>>-Chris >>> >>> >>>>There seem to be 3 methods in TargetData that a...

...rgetData' ../../2006-05-08-llvm-gcc-4/gcc/llvm-internal.h:56: error: forward declaration of `struct llvm::TargetData' ../../2006-05-08-llvm-gcc-4/gcc/llvm-backend.cpp: In function `void emit_global_to_llvm(tree_node*)': ../../2006-05-08-llvm-gcc-4/gcc/llvm-backend.cpp:387: error: `getTypeAlignment' undeclared (first use this function) ../../2006-05-08-llvm-gcc-4/gcc/llvm-backend.cpp:387: error: (Each undeclared identifier is reported only once for each function it appears in.) Adding: #include "llvm/Target/TargetData.h" Fixed this. Then I get: ../../2006-05-08-llv...

Hi All, There's a new snapshot of llvmgcc4 available here: http://nondot.org/sabre/2006-05-08-llvm-gcc-4.tar.gz This release includes the various portability fixes contributed on llvmdev, includes fixes to build with mainline CVS (and, thus, *requires* mainline CVS), and includes various other bug fixes. If you're interested, please try it out. Thanks, -Chris --