search for: identifierinfo

Hi all， Clang use a hash table to store all its identifiers. The hash table definition is: typedef llvm::StringMap<IdentifierInfo*, llvm::BumpPtrAllocator> HashTableTy; HashTableTy HashTable; Can anyone explain the mechnism of handling the name string key collision for me? Is there a IdentifierInfo objects chain or list for variable or function with the same name? Thanks very much! Yabin -- The question is how do you...

...and same info used to create decl spec > with FunctionDecl::Create () . > > Question is , > > How do ,someone instantiate the DeclarationName instance using > StringRef ,because in the current trunk code snap ,we see that > the DeclarationName can be constructed using the IdentifierInfo or > Objc Selector or CXXOperatorId etc as argument in the constructor . > > The code i.e > void appendExtern(StringRef Sr) > { > char *ExternChar = const_cast<char *> (Sr.data()); > *Ptr =reinterpret_cast<void *>(ExternChar); > this->ExternName = Declar...

...onstructing the DeclarationNameInfo and same info used to create decl spec with FunctionDecl::Create () . Question is , How do ,someone instantiate the DeclarationName instance using StringRef ,because in the current trunk code snap ,we see that the DeclarationName can be constructed using the IdentifierInfo or Objc Selector or CXXOperatorId etc as argument in the constructor . The code i.e void appendExtern(StringRef Sr) { char *ExternChar = const_cast<char *> (Sr.data()); *Ptr =reinterpret_cast<void *>(ExternChar); this->ExternName = DeclarationName::getFromOpaquePtr(Ptr); }...

...y hand, because, see caveats below): 1. main 2. clang::Parser::ParseNamespace(unsigned int, clang::SourceLocation&, clang::SourceLocation) 3. clang::Parser::ParseInnerNamespace(std::vector<clang::SourceLocation, std::allocator<clang::SourceLocation> >&, std::vector<clang::IdentifierInfo*, std::allocator<clang::IdentifierInfo*> >&, std::vector<clang::SourceLocation, std::allocator<clang::SourceLocation> >&, unsigned int, clang::SourceLocation&, clang::ParsedAttributes&, clang::BalancedDelimiterTracker&) 4. clang::Parser::ParseTopLevelDecl(c...

...l const*>, llvm::DenseMapInfo<long long> >::grow(unsigned int) + 3326 22 clang 0x0000000100054fb0 std::_Deque_base<std::string, std::allocator<std::string> >::_M_initialize_map(unsigned long) + 2864 23 clang 0x000000010003611b llvm::DenseMap<clang::IdentifierInfo const*, unsigned int, llvm::DenseMapInfo<clang::IdentifierInfo const*>, llvm::DenseMapInfo<unsigned int> >::grow(unsigned int) + 10491 24 clang 0x0000000100016cfb std::_Rb_tree<std::string, std::string, std::_Identity<std::string>, std::less<std::string>, s...

> > I'm not sure we would want to store the MCInst(s) in the AST. After we're > done with semantic checking and we've created the IR representation (with > inputs, outputs, clobbers, constraints, etc.), I don't think there's a > reason for the MCInst(s) to persist. > I was assuming that MCInst would already provide a lot of the needed information, like

Hi All, We have populated info in the Clang Sema i.e class Sema (include/clang/Sema/Sema.h) and like to propagate the same to Clang Codegen . Currently we are propagating through ASTContext ,where we have duplicating fields info and operation in the Sema and ASTContext . Any better way of doing the same ? Thank you ~Umesh

On Aug 6, 2012, at 1:03 PM, João Matos wrote: > 1. How is clang going to discover the input operands, output operands, > constraints, and clobbered registers? > > The approach you described sounds good to me. Reusing all the work done in the LLVM MC layer seems the right approach. Glad you agree. We really shouldn't be replicating information in the frontend; this very error

.../src/lib/clang/libclangfrontend/../../../contrib/llvm/tools/clang/lib/Frontend/PrintPreprocessedOutput.cpp -o PrintPreprocessedOutput.o /src/lib/clang/libclangfrontend/../../../contrib/llvm/tools/clang/lib/Frontend/PrintPreprocessedOutput.cpp: In function 'void PrintMacroDefinition(const clang::IdentifierInfo&, const clang::MacroInfo&, clang::Preprocessor&, llvm::raw_ostream&)': /src/lib/clang/libclangfrontend/../../../contrib/llvm/tools/clang/lib/Frontend/PrintPreprocessedOutput.cpp:36: internal compiler error: in var_ann, at tree-flow-inline.h:127 Please submit a full bug report, w...