Displaying 6 results from an estimated 6 matches for "parsedeclar".
Did you mean:
parsedeclare
2013 Jan 31
2
[LLVMdev] std::string suffices for Init* argument?
Hi Jakob,
How is `FieldName`, which is a std::string, being passed as the third
argument to SetValue on line 1848 of TGParser.cpp, which is declared
as being an Init*? The nearly identical (FIXME) codepath in
ParseDeclaration immediately puts the string into a StringInit, which
makes sense, but how on earth is the std::string being passed in? This
is really freaking me out.
-- Sean Silva
2016 Nov 20
3
uninitialized values in Attributes.cpp
...llvm::GlobalValue::LinkageTypes, llvm::Twine const&, llvm::Module*)
(Function.cpp:277)
==29299== by 0x1CD2B36: Create (Function.h:106)
==29299== by 0x1CD2B36:
llvm::LLParser::ParseFunctionHeader(llvm::Function*&, bool)
(LLParser.cpp:4766)
==29299== by 0x1CCE2C2: llvm::LLParser::ParseDeclare() (LLParser.cpp:444)
==29299== by 0x1CCC15A: llvm::LLParser::ParseTopLevelEntities()
(LLParser.cpp:276)
==29299== by 0x1CCBFBF: llvm::LLParser::Run() (LLParser.cpp:74)
==29299== by 0x1CC59D8:
llvm::parseAssemblyInto(llvm::MemoryBufferRef, llvm::Module&,
llvm::SMDiagnostic&, llv...
2016 Nov 20
3
uninitialized values in Attributes.cpp
...&, llvm::Module*)
>> (Function.cpp:277)
>> ==29299== by 0x1CD2B36: Create (Function.h:106)
>> ==29299== by 0x1CD2B36:
>> llvm::LLParser::ParseFunctionHeader(llvm::Function*&, bool)
>> (LLParser.cpp:4766)
>> ==29299== by 0x1CCE2C2: llvm::LLParser::ParseDeclare() (LLParser.cpp:444)
>> ==29299== by 0x1CCC15A: llvm::LLParser::ParseTopLevelEntities()
>> (LLParser.cpp:276)
>> ==29299== by 0x1CCBFBF: llvm::LLParser::Run() (LLParser.cpp:74)
>> ==29299== by 0x1CC59D8: llvm::parseAssemblyInto(llvm::MemoryBufferRef,
>> llvm:...
2016 Jun 02
6
-Wmisleading-indentation violations
Hi,
I was building LLVM with gcc 6.1.1 recently and it was spitting out
some warnings relating to misleading indention that caught my eye.
This wasn't a fresh build so I may have missed some. I've CC'ed the
authors of the potentially misleading lines so they can decide what do
about the warnings (if anything).
I'm wondering if clang-format is making some inappropriate choices
2013 Jan 31
0
[LLVMdev] std::string suffices for Init* argument?
On Jan 30, 2013, at 9:37 PM, Sean Silva <silvas at purdue.edu> wrote:
> How is `FieldName`, which is a std::string, being passed as the third
> argument to SetValue on line 1848 of TGParser.cpp, which is declared
> as being an Init*? The nearly identical (FIXME) codepath in
> ParseDeclaration immediately puts the string into a StringInit, which
> makes sense, but how on earth is the std::string being passed in? This
> is really freaking me out.
See TGParser.h:
bool SetValue(Record *TheRec, SMLoc Loc, Init *ValName,
const std::vector<unsigned> &Bi...
2016 Jul 20
2
[XRay] Build instrumented Clang, some analysis results
...or<clang::SourceLocation, std::allocator<clang::SourceLocation> >&, unsigned int, clang::SourceLocation&, clang::ParsedAttributes&, clang::BalancedDelimiterTracker&)
4. clang::Parser::ParseTopLevelDecl(clang::OpaquePtr<clang::DeclGroupRef>&)
5. clang::Parser::ParseDeclaration(unsigned int, clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&)
6. clang::Parser::ParseDeclarationStartingWithTemplate(unsigned int, clang::SourceLocation&, clang::AccessSpecifier, clang::AttributeList*)
7. clang::BackendConsumer::HandleTranslationUnit(clang::AST...