Displaying 7 results from an estimated 7 matches for "mappingtrait".
2013 Mar 11
0
[LLVMdev] YAML IO problems
...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 boolTest;
llvm::StringRef directory;
llvm::StringRef suffix;
int32_t intTest;
}...
2020 Nov 19
3
[PATCH 0/2] [clang-format] Add new configurations
From: Anastasiia Lukianenko <anastasiia_lukianenko at epam.com>
We are trying to use the clang-format approach as a base for Xen [1]
style formatting.
During the state of testing clang-format with different configurations,
we found that some points regarding the Xen coding style are not
configurable. Therefore, we decided to add them to be able to make a
choice in different cases.
Regards,
2012 Oct 30
2
[LLVMdev] Status of YAML IO?
...e: bar2
# CHECK-NOT: name: baz
# CHECK: ...
My thinking is that we can extend this to support embedded COFF/ELF/MachO in yaml by using new kind values. For example:
---
kind: object-coff
header:
# stuff
sections:
# stuff
symbols:
# stuff
...
The MappingTrait<const ld::File*> will look at the kind value and switch off it. We just need an external function (per file format) which can be called with the same mapping() parameters which will do the io.map*() calls and have traits for platform specific types, which turns the yaml into an in-memory b...
2012 Oct 30
0
[LLVMdev] Status of YAML IO?
...gt; My thinking is that we can extend this to support embedded
> COFF/ELF/MachO in yaml by using new kind values. For example:
>
> ---
> kind: object-coff
> header:
> # stuff
> sections:
> # stuff
> symbols:
> # stuff
> ...
>
> The MappingTrait<const ld::File*> will look at the kind value and
> switch off it. We just need an external function (per file format)
> which can be called with the same mapping() parameters which will do
> the io.map*() calls and have traits for platform specific types,
> which turns the...
2012 Oct 25
0
[LLVMdev] Status of YAML IO?
> To better understand how a client would use YAML I/O. I've completely rewritten the ReaderYAML and WriterYAML in lld to use YAML I/O. The source code is now about half the size. But more importantly, the error checking is much, much better and any time an attribute (e.g. of an Atom) is changed or added, there is just one place to update the yaml code instead of two places (the reader
2012 Oct 25
3
[LLVMdev] Status of YAML IO?
On Oct 22, 2012, at 5:07 PM, Nick Kledzik wrote:
> On Oct 22, 2012, at 4:40 PM, Sean Silva wrote:
>> Hey Nick, what's the status on YAML IO? The other thread seems to have died.
>
> I'm waiting on Michael Spencer's feedback.
To better understand how a client would use YAML I/O. I've completely rewritten the ReaderYAML and WriterYAML in lld to use YAML I/O. The
2012 Oct 30
2
[LLVMdev] Status of YAML IO?
...upport embedded COFF/ELF/MachO in yaml by using new kind values. For example:
>>
>> ---
>> kind: object-coff
>> header:
>> # stuff
>> sections:
>> # stuff
>> symbols:
>> # stuff
>> ...
>>
>> The MappingTrait<const ld::File*> will look at the kind value and switch off it. We just need an external function (per file format) which can be called with the same mapping() parameters which will do the io.map*() calls and have traits for platform specific types, which turns the yaml into an in-memory b...