<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm5719-llvm/llvm/test/ObjectYAML, branch meklort-10.0.1</title>
<subtitle>Project Ortega BCM5719 LLVM</subtitle>
<id>https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1</id>
<link rel='self' href='https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/'/>
<updated>2019-10-30T15:12:48+00:00</updated>
<entry>
<title>[ObjectYAML] - Redefine LLVM_YAML_IS_SEQUENCE_VECTOR(llvm::yaml::Hex*) as LLVM_YAML_IS_FLOW_SEQUENCE_VECTOR.</title>
<updated>2019-10-30T15:12:48+00:00</updated>
<author>
<name>Georgii Rymar</name>
<email>grimar@accesssoftek.com</email>
</author>
<published>2019-10-29T11:40:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=6e779e953e9d526e215e64bd1c8ebba8db0b44fe'/>
<id>urn:sha1:6e779e953e9d526e215e64bd1c8ebba8db0b44fe</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>[WebAssembly] Allow multivalue signatures in object files</title>
<updated>2019-10-18T20:27:30+00:00</updated>
<author>
<name>Thomas Lively</name>
<email>tlively@google.com</email>
</author>
<published>2019-10-18T20:27:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=393d0f799f8828e9d8002766a9e9db21797451df'/>
<id>urn:sha1:393d0f799f8828e9d8002766a9e9db21797451df</id>
<content type='text'>
Summary:
Also changes the wasm YAML format to reflect the possibility of having
multiple return types and to put the returns after the params for
consistency with the binary encoding.

Reviewers: aheejin, sbc100

Subscribers: dschuff, jgravelle-google, hiraditya, sunfish, arphaman, rupprecht, llvm-commits

Tags: #llvm

Differential Revision: https://reviews.llvm.org/D69156

llvm-svn: 375283
</content>
</entry>
<entry>
<title>[yaml2obj/ObjectYAML] - Cleanup the error reporting API, add custom errors handlers.</title>
<updated>2019-09-13T16:00:16+00:00</updated>
<author>
<name>George Rimar</name>
<email>grimar@accesssoftek.com</email>
</author>
<published>2019-09-13T16:00:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=850110272783e85bc79d9fad64add5d303a23ad1'/>
<id>urn:sha1:850110272783e85bc79d9fad64add5d303a23ad1</id>
<content type='text'>
This is a continuation of the YAML library error reporting
refactoring/improvement and the idea by itself was mentioned
in the following thread:
https://reviews.llvm.org/D67182?id=218714#inline-603404

This performs a cleanup of all object emitters in the library.
It allows using the custom one provided by the caller.

One of the nice things is that each tool can now print its tool name,
e.g: "yaml2obj: error: &lt;text&gt;"

Also, the code became a bit simpler.

Differential revision: https://reviews.llvm.org/D67445

llvm-svn: 371865
</content>
</entry>
<entry>
<title>[ObjectYAML] Fix lifetime issue in dumpDebugLines</title>
<updated>2019-08-29T02:36:48+00:00</updated>
<author>
<name>Vitaly Buka</name>
<email>vitalybuka@google.com</email>
</author>
<published>2019-08-29T02:36:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=db751c37782d10548e62d08bf23075ac9b5d4362'/>
<id>urn:sha1:db751c37782d10548e62d08bf23075ac9b5d4362</id>
<content type='text'>
Subscribers: llvm-commits

Tags: #llvm

Differential Revision: https://reviews.llvm.org/D66901

llvm-svn: 370289
</content>
</entry>
<entry>
<title>[yaml2obj/obj2yaml][MachO] Fix a test failure in big endian hosts</title>
<updated>2019-08-20T09:58:31+00:00</updated>
<author>
<name>Seiya Nuta</name>
<email>nuta@seiya.me</email>
</author>
<published>2019-08-20T09:58:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=b8dcc193890c70f7b7b4fc762a0b535f6e9fadfa'/>
<id>urn:sha1:b8dcc193890c70f7b7b4fc762a0b535f6e9fadfa</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>[yaml2obj/obj2yaml][MachO] Allow setting custom section data</title>
<updated>2019-08-20T08:49:07+00:00</updated>
<author>
<name>Seiya Nuta</name>
<email>nuta@seiya.me</email>
</author>
<published>2019-08-20T08:49:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=522377494b3d7c4bfcaa9a632497231ac3c19143'/>
<id>urn:sha1:522377494b3d7c4bfcaa9a632497231ac3c19143</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>[yaml2obj][MachO] Don't fill dummy data for virtual sections</title>
<updated>2019-06-17T02:07:20+00:00</updated>
<author>
<name>Seiya Nuta</name>
<email>nuta@seiya.me</email>
</author>
<published>2019-06-17T02:07:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=4f15732067602c38f5280899971bb24f43612dd4'/>
<id>urn:sha1:4f15732067602c38f5280899971bb24f43612dd4</id>
<content type='text'>
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 &lt;= 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
</content>
</entry>
<entry>
<title>[llvm-readobj] Change -long-option to --long-option in tests. NFC</title>
<updated>2019-05-01T05:27:20+00:00</updated>
<author>
<name>Fangrui Song</name>
<email>maskray@google.com</email>
</author>
<published>2019-05-01T05:27:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=e29e30b1397f3e50f3487491f8a77ae08e4e3471'/>
<id>urn:sha1:e29e30b1397f3e50f3487491f8a77ae08e4e3471</id>
<content type='text'>
We use both -long-option and --long-option in tests. Switch to --long-option for consistency.

In the "llvm-readelf" mode, -long-option is discouraged as it conflicts with grouped short options and it is not accepted by GNU readelf.

While updating the tests, change llvm-readobj -s to llvm-readobj -S to reduce confusion ("s" is --section-headers in llvm-readobj but --symbols in llvm-readelf).

llvm-svn: 359649
</content>
</entry>
<entry>
<title>[WebAssembly] Target features section</title>
<updated>2019-03-20T20:26:45+00:00</updated>
<author>
<name>Thomas Lively</name>
<email>tlively@google.com</email>
</author>
<published>2019-03-20T20:26:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=f6f4f84378ea07e8cb976631dd82079c027d7cf4'/>
<id>urn:sha1:f6f4f84378ea07e8cb976631dd82079c027d7cf4</id>
<content type='text'>
Summary:
Implements a new target features section in assembly and object files
that records what features are used, required, and disallowed in
WebAssembly objects. The linker uses this information to ensure that
all objects participating in a link are feature-compatible and records
the set of used features in the output binary for use by optimizers
and other tools later in the toolchain.

The "atomics" feature is always required or disallowed to prevent
linking code with stripped atomics into multithreaded binaries. Other
features are marked used if they are enabled globally or on any
function in a module.

Future CLs will add linker flags for ignoring feature compatibility
checks and for specifying the set of allowed features, implement using
the presence of the "atomics" feature to control the type of memory
and segments in the linked binary, and add front-end flags for
relaxing the linkage policy for atomics.

Reviewers: aheejin, sbc100, dschuff

Subscribers: jgravelle-google, hiraditya, sunfish, mgrang, jfb, jdoerfert, llvm-commits

Tags: #llvm

Differential Revision: https://reviews.llvm.org/D59173

llvm-svn: 356610
</content>
</entry>
<entry>
<title>[WebAssembly] Update MC for bulk memory</title>
<updated>2019-02-19T22:56:19+00:00</updated>
<author>
<name>Thomas Lively</name>
<email>tlively@google.com</email>
</author>
<published>2019-02-19T22:56:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=2e1504091e2b6e949290b4792224c4b833acda99'/>
<id>urn:sha1:2e1504091e2b6e949290b4792224c4b833acda99</id>
<content type='text'>
Summary:
Rename MemoryIndex to InitFlags and implement logic for determining
data segment layout in ObjectYAML and MC. Also adds a "passive" flag
for the .section assembler directive although this cannot be assembled
yet because the assembler does not support data sections.

Reviewers: sbc100, aardappel, aheejin, dschuff

Subscribers: jgravelle-google, hiraditya, sunfish, rupprecht, llvm-commits

Tags: #llvm

Differential Revision: https://reviews.llvm.org/D57938

llvm-svn: 354397
</content>
</entry>
</feed>
