search for: yamltraits

...verloaded `cast(const llvm::Value*&)' is ambiguous llvm/include/llvm/IR/InstrTypes.h:827: error: call of overloaded `dyn_cast(llvm::Type*&)' is ambiguous llvm/include/llvm/Support/Casting.h:249: error: call of overloaded `cast(llvm::Value*&)' is ambiguous llvm/lib/Support/YAMLTraits.cpp:88: error: call of overloaded `dyn_cast(llvm::yaml::Input::HNode*&)' is ambiguous llvm/lib/Support/YAMLTraits.cpp:99: error: call of overloaded `dyn_cast(llvm::yaml::Input::HNode*&)' is ambiguous llvm/lib/Support/YAMLTraits.cpp:125: error: call of overloaded `dyn_cast(llvm::ya...

Hi All, I am trying to compile latest llvm code using xlc 12.1 on AIX and got the following error. I am trying to debug the issue. Has anybody seen the issue on linux/gcc or is it just xlc specific ? [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/YAMLTraits.cpp.o "/llvm/version2/llvm/include/llvm/Support/YAMLTraits.h", line 264.20: 1540-0118 (S) A class name is expected in the base specifier. 1540-0700 (I) The previous message was produced while processing "struct llvm::yaml::has_FlowTraits<const class llvm::StringRef,1>::Derived&...

....64le # RUN: yaml2obj -D BITS=64 -D ENCODE=MSB %s -o %t.64be See https://reviews.llvm.org/D73828 for examples how -D simplifies tests. Do people think it may be useful in other YAML tools? If yes, I'll move the yaml2obj implementation (https://reviews.llvm.org/D73821 ) to include/llvm/Support/YAMLTraits.h llvm::yaml::Input so that other YAML tools can use the feature. Do people prefer a different syntax? I think [[PATTERN]] is nice because it is what FileCheck -DFILE=... uses: # CHECK: ... [[FILE]] FileCheck only preprocesses patterns in CHECK lines. D73821 preprocesses both comment li...

....64le # RUN: yaml2obj -D BITS=64 -D ENCODE=MSB %s -o %t.64be See https://reviews.llvm.org/D73828 for examples how -D simplifies tests. Do people think it may be useful in other YAML tools? If yes, I'll move the yaml2obj implementation (https://reviews.llvm.org/D73821 ) to include/llvm/Support/YAMLTraits.h llvm::yaml::Input so that other YAML tools can use the feature. Do people prefer a different syntax? I think [[PATTERN]] is nice because it is what FileCheck -DFILE=... uses: # CHECK: ... [[FILE]] FileCheck only preprocesses patterns in CHECK lines. D73821 preprocesses both comment li...

2017-05-26 17:47 GMT-07:00 Zachary Turner via llvm-dev < llvm-dev at lists.llvm.org>: > Changing a header file somewhere and having to spend 10 minutes waiting > for a build leads to a lot of wasted developer time. > > The real culprit here is tablegen. Can we split support and ADT into two > - the parts that tablegen depends on and the parts that it doesn't? >

..., "int_test": 4 } int_test: -627100365 Done Note the strings are both incorrect - it can't seem to identify the proper end of each string. And it ends up lost looking at the integer. The test code is: #include <iostream> #include <fstream> #include "llvm/Support/YAMLTraits.h" using namespace std; using llvm::yaml::Input; using llvm::yaml::MappingTraits; //===------------------------- ---------------------------------------------===// // Test MappingTraits //===----------------------------------------------------------------------===// struct FooBar { bool...

...Using r172358 as an example (a moderately large commit chosen otherwise at random), the current commit message subject is: [llvm-commits] [llvm] r172358 - in /llvm/trunk: include/llvm/ADT/StringRef.h include/llvm/Analysis/DOTGraphTraitsPass.h include/llvm/Object/RelocVisitor.h include/llvm/Support/YAMLTraits.h lib/Analysis/ValueTracking.cpp lib/MC/ELFObjectWriter.cpp lib/MC/WinCOFFObjectWriter.cpp lib/Support/APFloat.cpp lib/Support/DynamicLibrary.cpp lib/Target/R600/AMDGPUSubtarget.h lib/Target/R600/AMDILDevice.h lib/Target/R600/AMDILPeepholeOptimizer.cpp lib/Transforms/IPO/DeadArgumentElimination.cpp...

...testing to > the backend pieces; after all, testability is a huge motivation for this > work. > > As a concrete example, a file solely containing '%' crashes the yaml > parser: > $ ~/llvm/Debug+Asserts/bin/yaml2obj -format=coff t.yaml > yaml2obj: ~/llvm/src/lib/Support/YAMLTraits.cpp:78: bool > llvm::yaml::Input::setCurrentDocument(): Assertion `Strm->failed() && "Root > is NULL iff parsing failed"' failed. > 0 yaml2obj 0x000000000048682e > 1 yaml2obj 0x0000000000486b43 > 2 yaml2obj 0x000000000048570e > 3 l...

...ader.h > Registry.h > ScopedPrinter.h > SMLoc.h > Solaris.h > SourceMgr.h > SpecialCaseList.h > TargetParser.h > TargetRegistry.h > TargetSelect.h > TarWriter.h > ToolOutputFile.h > TrigramIndex.h > TypeName.h > Valgrind.h > Wasm.h > YAMLParser.h > YAMLTraits.h > > > So, as a very crude first attempt, you call the first group of stuff > "Base", the second group "Support", and add a dependency from Support to > Base. This has nothing to do with tablegen, btw, and tablegen would still > probably depend on Support eve...

David Blaikie wrote: > On Fri, Nov 30, 2012 at 9:43 AM, Sebastian Pop <spop at codeaurora.org> wrote: > > Hi, > > > > Sebastian Pop wrote: > >> Chris Lattner wrote: > >> > I'm in favor of it. Of course, the truly awesomest thing would be something like: > >> > > >> > [cfe-commits] r167788 - [lib/Analysis] Fix bad CFG

2015-04-28 10:14 GMT-07:00 Quentin Colombet <qcolombet at apple.com>: > Hi Alex, > > Thanks for working on this. > > Personally I would rather not have to write YAML inputs but instead resort > on the what the machine dumps look like. That being said, I can live with > YAML :). > > More importantly, how do you plan to report syntax errors to the users? > Things

I would like to begin a discussion about updating LLVM's opt-report infrastructure. There are some things I'd like to be able to do with optimization reports that I don't think can be done, or at least aren't natural to do, with the current implementation. I understand that there is a lot of code in place already to produce optimization remarks, and one of my explicit goals is to

...ader.h > Registry.h > ScopedPrinter.h > SMLoc.h > Solaris.h > SourceMgr.h > SpecialCaseList.h > TargetParser.h > TargetRegistry.h > TargetSelect.h > TarWriter.h > ToolOutputFile.h > TrigramIndex.h > TypeName.h > Valgrind.h > Wasm.h > YAMLParser.h > YAMLTraits.h > YAML Parser as well. -- Mehdi > > > So, as a very crude first attempt, you call the first group of stuff > "Base", the second group "Support", and add a dependency from Support to > Base. This has nothing to do with tablegen, btw, and tablegen would...

....dir/ThreadPool.cpp.o CMakeFiles/LLVMSupport.dir/Timer.cpp.o CMakeFiles/LLVMSupport.dir/ToolOutputFile.cpp.o CMakeFiles/LLVMSupport.dir/Triple.cpp.o CMakeFiles/LLVMSupport.dir/Twine.cpp.o CMakeFiles/LLVMSupport.dir/Unicode.cpp.o CMakeFiles/LLVMSupport.dir/YAMLParser.cpp.o CMakeFiles/LLVMSupport.dir/YAMLTraits.cpp.o CMakeFiles/LLVMSupport.dir/raw_os_ostream.cpp.o CMakeFiles/LLVMSupport.dir/raw_ostream.cpp.o CMakeFiles/LLVMSupport.dir/regcomp.c.o CMakeFiles/LLVMSupport.dir/regerror.c.o CMakeFiles/LLVMSupport.dir/regexec.c.o CMakeFiles/LLVMSupport.dir/regfree.c.o CMakeFiles/LLVMSupport.dir/regstrlcpy.c.o C...

...canning dependencies of targetLLVMSupport [ 0%] Building CXX objectlib/Support/CMakeFiles/LLVMSupport.dir/AMDGPUMetadata.cpp.o In file included from /testlocation/llvm_lld/llvm-stable/lib/Support/AMDGPUMetadata.cpp:18: In file included from /testlocation/llvm_lld/llvm-stable/include/llvm/Support/YAMLTraits.h:23: In file included from /testlocation/llvm_lld/llvm-stable/include/llvm/Support/SourceMgr.h:25: In file included from /testlocation/llvm_lld/llvm-stable/include/llvm/Support/MemoryBuffer.h:23: In file included from /testlocation/llvm_lld/llvm-stable/include/llvm/Support/FileSystem.h:33: In...

On Fri, Nov 30, 2012 at 9:43 AM, Sebastian Pop <spop at codeaurora.org> wrote: > Hi, > > Sebastian Pop wrote: >> Chris Lattner wrote: >> > I'm in favor of it. Of course, the truly awesomest thing would be something like: >> > >> > [cfe-commits] r167788 - [lib/Analysis] Fix bad CFG construction bug when handling C++ 'try' statements.

...Using r172358 as an example (a moderately large commit chosen otherwise at random), the current commit message subject is: [llvm-commits] [llvm] r172358 - in /llvm/trunk: include/llvm/ADT/StringRef.h include/llvm/Analysis/DOTGraphTraitsPass.h include/llvm/Object/RelocVisitor.h include/llvm/Support/YAMLTraits.h lib/Analysis/ValueTracking.cpp lib/MC/ELFObjectWriter.cpp lib/MC/WinCOFFObjectWriter.cpp lib/Support/APFloat.cpp lib/Support/DynamicLibrary.cpp lib/Target/R600/AMDGPUSubtarget.h lib/Target/R600/AMDILDevice.h lib/Target/R600/AMDILPeepholeOptimizer.cpp lib/Transforms/IPO/DeadArgumentElimination.cpp...

...: Compiling Twine.cpp for Release+Asserts build llvm[1]: Compiling Unicode.cpp for Release+Asserts build llvm[1]: Compiling Valgrind.cpp for Release+Asserts build llvm[1]: Compiling Watchdog.cpp for Release+Asserts build llvm[1]: Compiling YAMLParser.cpp for Release+Asserts build llvm[1]: Compiling YAMLTraits.cpp for Release+Asserts build llvm[1]: Compiling circular_raw_ostream.cpp for Release+Asserts build llvm[1]: Compiling raw_os_ostream.cpp for Release+Asserts build llvm[1]: Compiling raw_ostream.cpp for Release+Asserts build llvm[1]: Compiling regcomp.c for Release+Asserts build llvm[1]: Compiling...