bcm5719-llvm/llvm/test/ObjectYAML/MachO, branch meklort-10.0.1

[ObjectYAML] - Redefine LLVM_YAML_IS_SEQUENCE_VECTOR(llvm::yaml::Hex*) as LLVM_YAML_IS_FLOW_SEQUENCE_VECTOR.

2019-10-30T15:12:48+00:00

I am using it in https://reviews.llvm.org/D69399. This change changes how obj2yaml dumps arrays of `llvm::yaml::Hex8/llvm::yaml::Hex16/llvm::yaml::Hex32` from: ``` PayloadBytes: - 0x01 - 0x02 ... ``` To ``` PayloadBytes: [ 0x01, 0x02, ... ] ``` The latter way is shorter and looks better for arrays. Differential revision: https://reviews.llvm.org/D69558

[ObjectYAML] Fix lifetime issue in dumpDebugLines

2019-08-29T02:36:48+00:00

Subscribers: llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D66901 llvm-svn: 370289

[yaml2obj/obj2yaml][MachO] Fix a test failure in big endian hosts

2019-08-20T09:58:31+00:00

These section contents are dummy data (0xdeadbeef) and it's endianess does not matter. - http://lab.llvm.org:8011/builders/clang-ppc64be-linux/builds/37265 llvm-svn: 369360

[yaml2obj/obj2yaml][MachO] Allow setting custom section data

2019-08-20T08:49:07+00:00

Reviewers: alexshap, jhenderson, rupprecht Reviewed By: alexshap, jhenderson Subscribers: abrachet, hiraditya, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D65799 llvm-svn: 369348

[yaml2obj][MachO] Don't fill dummy data for virtual sections

2019-06-17T02:07:20+00:00

Summary: Currently, MachOWriter::writeSectionData writes dummy data (0xdeadbeef) to fill section data areas in the file even if the section is a virtual one. Since virtual sections don't occupy any space in the file, writing dummy data could results the "OS.tell() - fileStart <= Sec.offset" assertion failure. This patch fixes the bug by simply not writing any dummy data for virtual sections. Reviewers: beanz, jhenderson, rupprecht, alexshap Reviewed By: alexshap Subscribers: compnerd, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D62991 llvm-svn: 363525

Make YAML quote forward slashes.

2018-10-12T16:31:20+00:00

If you have the string /usr/bin, prior to this patch it would not be quoted by our YAML serializer. But a string like C:\src would be, due to the presence of a backslash. This makes the quoting rules of basically every single file path different depending on the path syntax (posix vs. Windows). While technically not required by the YAML specification to quote forward slashes, when the behavior of paths is inconsistent it makes it difficult to portably write FileCheck lines that will work with either kind of path. Differential Revision: https://reviews.llvm.org/D53169 llvm-svn: 344359

Revert "Make YAML quote forward slashes."

2018-10-12T16:31:08+00:00

This reverts commit b86c16ad8c97dadc1f529da72a5bb74e9eaed344. This is being reverted because I forgot to write a useful commit message, so I'm going to resubmit it with an actual commit message. llvm-svn: 344358

Make YAML quote forward slashes.

2018-10-12T16:24:09+00:00

llvm-svn: 344357

Align all scalar numbers to LLVM_YAML_IS_FLOW_SEQUENCE_VECTOR

2017-04-04T06:02:32+00:00

Otherwise, yamlize in YAMLTraits.h might be wrongly defined. This makes some AMDGPU tests fail when LLVM_LINK_LLVM_DYLIB is set. Differential Revision: https://reviews.llvm.org/D30508 llvm-svn: 299415

[ObjectYAML] Fix issue with DWARF2 AddrSize 8

2017-03-07T21:34:35+00:00

In my refactoring I introduced a bug where we were using the reference size instead of the offset size for DW_FORM_strp and similar forms. This patch resolves the error and adds a test case testing all the DWARF forms for DWARF2 AddrSize 8. There is similar coverage already in the DWARFDebugInfoTest sources that covers the parser. Once I migrate the DWARFGenerator APIs to be built on the YAML tools they will be fully covered under the same tests. llvm-svn: 297230