search for: yamlio

...onality to llvm/Support to help in parsing yaml documents. That parser greatly helps at the syntax level, but you still need to hand write a lot of semantic checking and then convert the various node types in to something usable. I've developed a layer on top of YAMLParser.h I'm calling YAMLIO.h (yaml I/O) which unifies parsing and writing yaml documents and handles most semantic checking, and is very easy to use! Basically, you define your yaml document schema as a mix of C++ structs and vectors, and YAMLIO does the rest. Lets look at a quick example first. Suppose this is your yaml...

...have a dedicated JSON library in the LLVM tree, I'd like to add one. The pressing need is for clangd, but we have other tools that read/write JSON too. I'm proposing we write a new one, rather than importing a third-party library (licensing/integration reasons), on or extending YamlParser/YamlIO (usability/flexibility). I lean towards a design that parses a full DOM at once, and provides literal-like syntax for composing documents. I've written a document laying out the reasons for taking this path, and my proposal for a design (with links to a prototype) https://docs.google.com/docum...

...bject-test.elf-i386 [ 1543s] FileCheck error: '-' is empty. [ 1543s] -- [ 1543s] [ 1543s] ******************** [ 1552s] Testing: 0 .. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90.. [ 1552s] FAIL: LLVM-Unit :: Support//home/abuild/rpmbuild/BUILD/llvm-3.3/stage2/unittests/Support/SupportTests/YAMLIO.TestReadKindAndFlagsSequence (8538 of 8585) [ 1552s] ******************** TEST 'LLVM-Unit :: Support//home/abuild/rpmbuild/BUILD/llvm-3.3/stage2/unittests/Support/SupportTests/YAMLIO.TestReadKindAndFlagsSequence' FAILED ******************** [ 1552s] Note: Google Test filter = YAMLIO.TestRea...

...aml2obj 0x0000000000404879 > Stack dump: > 0. Program arguments: ~/llvm/Debug+Asserts/bin/yaml2obj -format=coff > t.yaml > > Hopefully a fuzzer that is fuzzing a yaml input would not waste its time with syntactically invalid or unusual YAML. Also, you're thinking of YAMLIO which is a layer on top of the YAML parser (YAMLParser.{h,cpp}). It might make sense to not use YAMLIO (it is good for some types of data, not for all) but still use the YAML parser. -- Sean Silva > On Tue, Apr 28, 2015 at 2:00 PM, Alex L <arphaman at gmail.com> wrote: > >> &gt...

...gt; Do you have any other ideas or some ideas as to why you'd prefer one > direction rather than the other? Bin Zeng worked on a project as an intern last summer to serialize machine functions to yaml. At the time, we were unable to commit it to trunk because we were waiting for Nick's yamlio work to get committed. I've still got his patches and plan to commit them whenever I get a chance. I was also considering having another intern pick up that project where it left off. The approach is perhaps similar to what Dan is proposing, just flipped around. In one scheme, the top-level...

...ibrary in the LLVM tree, I'd like to add > one. The pressing need is for clangd, but we have other tools that > read/write JSON too. > > I'm proposing we write a new one, rather than importing a third-party > library (licensing/integration reasons), on or extending YamlParser/YamlIO > (usability/flexibility). I lean towards a design that parses a full DOM at > once, and provides literal-like syntax for composing documents. > > I've written a document laying out the reasons for taking this path, and > my proposal for a design (with links to a prototype) >...

Hi, On Wed, Apr 2, 2014 at 1:03 AM, Michael Spencer <bigcheesegs at gmail.com> wrote: > On Mon, Mar 31, 2014 at 10:54 AM, Simon Atanasyan <simon at atanasyan.com> wrote: >> As far as I understand now it is impossible to generate ELF object >> file with relocation sections using yaml2obj tool. I plan to support >> ELF relocations in the yaml2obj. Does anybody work

I'm trying to parse a simple JSON file, and am having problems with using YAMLIO. FWIW, I see the unit test YAMLIOTest.cpp is disabled with a #if 0. Anyway, the JSON file yaml.json contains: { "bool_test": true, "directory": ".", "suffix": "_test", "int_test": 4 } The test program when run shows: YAML:5:15: e...

On Wed, Jun 26, 2013 at 3:59 PM, Nadav Rotem <nrotem at apple.com> wrote: > > On Jun 26, 2013, at 3:51 PM, Chandler Carruth <chandlerc at google.com> wrote: > > Can you suggest an alternative solution? Can you describe why you don't > think metadata is the right container? This alone isn't really helpful at > moving us toward something that there has been

> On Sep 8, 2014, at 10:14 AM, Joerg Sonnenberger <joerg at britannica.bec.de> wrote: > > On Fri, Sep 05, 2014 at 09:23:34PM -0500, Richard Pennington wrote: >> Right now it only handles replacing a "-target foo" option >> with the options defined in the file foo in the resource/config >> directory, but I think it has potential for doing quite a bit

On Thu, Jun 27, 2013 at 10:49 AM, Jakob Stoklund Olesen <stoklund at 2pi.dk>wrote: > > On Jun 27, 2013, at 10:12 AM, Chandler Carruth <chandlerc at google.com> > wrote: > > > > > On Thu, Jun 27, 2013 at 9:50 AM, Jakob Stoklund Olesen <stoklund at 2pi.dk> > wrote: > > On Jun 26, 2013, at 4:18 PM, Eric Christopher <echristo at gmail.com> >

> > > I think that the two alternatives that are obvious are for the MF to contain > the IR, or for the IR to contain the MF. Alternatively, they can live in > parallel and the MF may reference the IR. I am not sure what is the right > approach here, but my gut feeling is that metadata is not necessarily the > right container for MF. Off the cuff I'd think that IR

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

Some background: A while back while working on code to read / write PDB files, I came up with Yet Another Stream Abstraction. Note that LLVM already has a few. Off the top of my head, theres: 1) `MemoryBuffer` and its associated class hierarchy 2) `raw_ostream` and it's associated classes. 3) `DataExtractor` which is used for reading from a StringRef. There's probably more, and