similar to: [LLVMdev] new warning

/Volumes/mrs5/net/llvm/llvm/lib/CodeGen/PreAllocSplitting.cpp: In member function ‘bool<unnamed>::PreAllocSplitting::SplitRegLiveInterval (llvm::LiveInterval*)’: /Volumes/mrs5/net/llvm/llvm/lib/CodeGen/PreAllocSplitting.cpp:546: warning: ‘SS’ may be used uninitialized in this function

Hi, There are some warnings in the LLVM and clang code bases: ---------------------------- llvm[0]: Compiling RegAllocGreedy.cpp for Release+Asserts build /Users/filcab/dev/stuff/llvm/llvm/include/llvm/ADT/SmallVector.h: In member function ‘void<unnamed>::RAGreedy::calcLiveBlockInfo(llvm::LiveInterval&)’: /Users/filcab/dev/stuff/llvm/llvm/include/llvm/ADT/SmallVector.h:325: warning:

/Volumes/mrs5/net/llvm/llvm/lib/Transforms/Scalar/ InstructionCombining.cpp: In member function ‘llvm::Instruction*<unnamed>::InstCombiner::visitAnd (llvm::BinaryOperator&)’: /Volumes/mrs5/net/llvm/llvm/lib/Transforms/Scalar/ InstructionCombining.cpp:3597: warning: ‘RHSCC’ may be used uninitialized in this function /Volumes/mrs5/net/llvm/llvm/lib/Transforms/Scalar/

On Feb 27, 2009, at 7:20 AM, Roman Levenstein wrote: > Hi, > > I'm working on the implementation of Extended Linear Scan register > allocator as described by Sarkar & Bodik. > One of the interesting features of their algorithm is the possibility > to allocate different physical registers to different live-ranges of > the same LiveInterval. Of course, it may require

Hi, I'm working on the implementation of Extended Linear Scan register allocator as described by Sarkar & Bodik. One of the interesting features of their algorithm is the possibility to allocate different physical registers to different live-ranges of the same LiveInterval. Of course, it may require some glue code to be inserted in cases, where different physical regs were assigned to

Hi Evan, Thanks a lot for your reply! 2009/2/27 Evan Cheng <evan.cheng at apple.com>: > > On Feb 27, 2009, at 7:20 AM, Roman Levenstein wrote: > >> Hi, >> >> I'm working on the implementation of Extended Linear Scan register >> allocator as described by Sarkar & Bodik. >> One of the interesting features of their algorithm is the possibility

new warnings, I think lib/CodeGen/SelectionDAG/DAGCombiner.cpp: In member function ‘llvm::SDValue<unnamed>::DAGCombiner::FindBetterChain(llvm::SDNode*, llvm::SDValue)’: lib/CodeGen/SelectionDAG/DAGCombiner.cpp:6006: warning: ‘SrcValueOffset’ may be used uninitialized in this function lib/CodeGen/SelectionDAG/DAGCombiner.cpp:6006: note: ‘SrcValueOffset’ was declared here

They looked real enough to me: /Volumes/mrs5/net/llvm/llvm/lib/Target/CellSPU/SPUISelDAGToDAG.cpp: In function ‘bool<unnamed>::isFPS16Immediate(llvm::ConstantFPSDNode*, short int&)’: /Volumes/mrs5/net/llvm/llvm/lib/Target/CellSPU/SPUISelDAGToDAG.cpp: 148: warning: dereferencing type-punned pointer will break strict- aliasing rules

On Dec 20, 2007, at 3:56 PM, Mike Stump wrote: > They looked real enough to me: Fixed, thanks. -Chris > > > /Volumes/mrs5/net/llvm/llvm/lib/Target/CellSPU/SPUISelDAGToDAG.cpp: In > function ‘bool<unnamed>::isFPS16Immediate(llvm::ConstantFPSDNode*, > short int&)’: > /Volumes/mrs5/net/llvm/llvm/lib/Target/CellSPU/SPUISelDAGToDAG.cpp: > 148: warning:

Hi all! I gave a shot at compiling core llvm with a Solaris 9 machine. The compiler is FSF gcc 3.4.6. I am building trunk in the release version. So far I did not run tests (no dejagnu installed). Here are my findings: 0) Configuring. I had to suppress the solaris tools by: env AR=/opt/gnu/bin/ar NM=/opt/gnu/bin/nm RANLIB=/opt/gnu/bin/ranlib STRIP=/opt/gnu/bin/strip ../llvm/configure

I tried on a different machine x86_64 ( vs x86 ) and I don't have these issues anymore (the tests are failing on the x86 machine because of a segmentation fault) Both builds were done using: g++ (GCC) 4.2.4 (Ubuntu 4.2.4-1ubuntu4) Something should be wrong with my environment... The only differences I noticed during the compilation are the following warnings (which appear several times, but

Building of llvm with gcc-4.5.2-1 gives these warnings: 1) Building FileManagerTest "llvm[4]: Compiling FileManagerTest.cpp for Debug+Asserts build C:/Programming/VersionControl/llvm/tools/clang/unittests/Basic/FileManagerTest.cpp: In member function 'virtual void<unnamed>::FileManagerTest_NoVirtualDirectoryExistsBeforeAVirtualFileIsAdded_Test::TestBody()':

Eric, could you tell me which version of gcc you are using (According to http://llvm.org/docs/GettingStarted.html, gcc 3.4.2 should be used but I don't know if this document is up to date regarding the required software versions) Anyway I also tried with gcc version 3.4.6 (Ubuntu 3.4.6-6ubuntu5) And now, I get a bunch of errors like this one: llvm-2.9/lib/Support/regcomp.c: In function `cset*

/Volumes/SandBox/clang/clang/clang/unittests/VMCore/MetadataTest.cpp: In member function 'virtual void<unnamed>::MDNodeTest_Everything_Test::TestBody()': /Volumes/SandBox/clang/clang/clang/unittests/VMCore/MetadataTest.cpp: 76: warning: dereferencing type-punned pointer will break strict- aliasing rules :-(

GCC is concerned that if we never go round the loop then fd will be uninitialized. By asserting that getaddrinfo set result != NULL we can avoid this. nbd.c: In function ‘nbd_open_handle’: nbd.c:974:5: error: ‘fd’ may be used uninitialized in this function [-Werror=maybe-uninitialized] 974 | close (fd); | ^~~~~~~~~~ nbd.c:954:7: note: ‘fd’ was declared here 954 | int fd;

Hello, I am a newbie to LLVM as well as compilers and I am hoping for some direction in finding an instance of where a Reaching Definition Analysis is being implemented within LLVM. I have referenced the sources files, initially hoping to find an explicit ReachingDefinitionAnalysis.cpp file ;-) but with no such luck. Other than that I have found the files SimpleRegisterCoalescing.cpp and the

2 new warnings in llvm: /Volumes/mrs5/net/llvm/llvm/lib/AsmParser/LLParser.cpp: In member function 'bool llvm::LLParser::ParseGlobal(const std::string&, const char*, unsigned int, bool, unsigned int)': /Volumes/mrs5/net/llvm/llvm/lib/AsmParser/LLParser.cpp:446: warning: 'IsConstant' may be used uninitialized in this function

On Thursday 17 January 2008 13:03, Evan Cheng wrote: > > So why does the live range extend throughout the entire basic block? > > > > %reg1055 doesn't appear anywhere else in the program so it shouldn't > > be > > live-in to the block. > > It could be a bug. Can you get me a test case? I'll see if I can whittle it down. It's a pretty huge

An embedded and charset-unspecified text was scrubbed... Name: gcc4-fs_ext3_acl.c URL: <http://listman.redhat.com/archives/ext3-users/attachments/20050620/80eb5460/attachment.c>

Hi Kameshwar, You're best off sending emails such as this to the LLVM developers mailing list (llvmdev at cs.uiuc.edu). You'll reach a much wider audience. The PBQPRegAlloc::buildInterferenceMatrix method constructs a PBQP cost matrix representing a single interference constraint, which doesn't sound like what you want. It is only used by the PBQP allocator (-regalloc=pbqp), whereas