<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm5719-llvm/lldb/utils/TableGen, 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-12-16T22:31:42+00:00</updated>
<entry>
<title>[lldb] Respect previously set values of LLDB_TABLEGEN_EXE</title>
<updated>2019-12-16T22:31:42+00:00</updated>
<author>
<name>Alex Langford</name>
<email>apl@fb.com</email>
</author>
<published>2019-12-16T22:29:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=3fbe518a102a344abbd837e364a404c0c695d183'/>
<id>urn:sha1:3fbe518a102a344abbd837e364a404c0c695d183</id>
<content type='text'>
If you set LLDB_TABLEGEN_EXE in a CMake cache file or in the CMake
invocation line, your setting isn't respected. Setting up the tablegen
for the host will overwrite the value that we set LLDB_TABLEGEN_EXE to,
which defeats the whole point of setting it in the first place.
</content>
</entry>
<entry>
<title>[LLDB] Fix inline variable only used in assertion. (NFC)</title>
<updated>2019-10-25T22:47:17+00:00</updated>
<author>
<name>Jonas Devlieghere</name>
<email>jonas@devlieghere.com</email>
</author>
<published>2019-10-25T22:46:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=10b5cd8ed5272d135ac75a94d3cf5854a0912f84'/>
<id>urn:sha1:10b5cd8ed5272d135ac75a94d3cf5854a0912f84</id>
<content type='text'>
This prevents unused variable warning/error in -DNDEBUG builds. The
variable was introduced in 5934cd11ea3e.

Patch by: Shu-Chun Weng

Differential revision: https://reviews.llvm.org/D69451
</content>
</entry>
<entry>
<title>[TableGen] Add asserts to make sure default values match property type</title>
<updated>2019-10-25T17:18:38+00:00</updated>
<author>
<name>Jonas Devlieghere</name>
<email>jonas@devlieghere.com</email>
</author>
<published>2019-10-25T17:17:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=5934cd11ea3e15dd9f13a9ee960012b5b64463ec'/>
<id>urn:sha1:5934cd11ea3e15dd9f13a9ee960012b5b64463ec</id>
<content type='text'>
This adds a few asserts to the property TableGen backend to prevent
mismatches between property types and their default values. This
would've prevented a copy-paste mistake we discovered downstream.
</content>
</entry>
<entry>
<title>[TableGen] Move helpers into LLDBTableGenUtils.</title>
<updated>2019-07-31T00:47:00+00:00</updated>
<author>
<name>Jonas Devlieghere</name>
<email>jonas@devlieghere.com</email>
</author>
<published>2019-07-31T00:47:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=be019c7a1f84cbdf8e6910fde34da120b19114b1'/>
<id>urn:sha1:be019c7a1f84cbdf8e6910fde34da120b19114b1</id>
<content type='text'>
Instead of polluting the LLDBTableGenBackends header with helpers used
by both emitters, move them into a separate files.

llvm-svn: 367377
</content>
</entry>
<entry>
<title>[TableGen] Include vector</title>
<updated>2019-07-31T00:20:55+00:00</updated>
<author>
<name>Jonas Devlieghere</name>
<email>jonas@devlieghere.com</email>
</author>
<published>2019-07-31T00:20:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=f63054f4008d5456f7a08c48cc0c8469e9cc1487'/>
<id>urn:sha1:f63054f4008d5456f7a08c48cc0c8469e9cc1487</id>
<content type='text'>
Fixes "no member named 'vector' in namespace 'std'" compile error.

llvm-svn: 367375
</content>
</entry>
<entry>
<title>[TableGen] Reuse typedef across emitters (NFC)</title>
<updated>2019-07-30T22:50:37+00:00</updated>
<author>
<name>Jonas Devlieghere</name>
<email>jonas@devlieghere.com</email>
</author>
<published>2019-07-30T22:50:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=310f6b89b198a2e7138c401fd442c98d84e14bb2'/>
<id>urn:sha1:310f6b89b198a2e7138c401fd442c98d84e14bb2</id>
<content type='text'>
This moves the std::map typedef into the header so it can be reused by
all the emitter implementations.

llvm-svn: 367363
</content>
</entry>
<entry>
<title>[lldb] Also include the array definition in Properties.inc</title>
<updated>2019-07-29T16:41:30+00:00</updated>
<author>
<name>Jonas Devlieghere</name>
<email>jonas@devlieghere.com</email>
</author>
<published>2019-07-29T16:41:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=a8ea595509f33834091fb9e3234a373f83d709a8'/>
<id>urn:sha1:a8ea595509f33834091fb9e3234a373f83d709a8</id>
<content type='text'>
Right now our Properties.inc only generates the initializer for the
options list but not the array declaration boilerplate around it. As the
array definition is identical for all arrays, we might as well also let
the Properties.inc generate it alongside the initializers.

Unfortunately we cannot do the same for enums, as there's this magic
ePropertyExperimental, which needs to come at the end to be interpreted
correctly. Hopefully we can get rid of this in the future and do the
same for the property enums.

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

llvm-svn: 367238
</content>
</entry>
<entry>
<title>[lldb][NFC] Split emitting and parsing in LLDBOptionDefEmitter</title>
<updated>2019-07-29T08:22:41+00:00</updated>
<author>
<name>Raphael Isemann</name>
<email>teemperor@gmail.com</email>
</author>
<published>2019-07-29T08:22:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=4e44c77ab3b7b2898319877a9dcc544ac9d460dd'/>
<id>urn:sha1:4e44c77ab3b7b2898319877a9dcc544ac9d460dd</id>
<content type='text'>
Splitting the different logic is cleaner and we it will be easier
to implement the enum emitting (which otherwise would have to
reimplement the Record parsing).

llvm-svn: 367207
</content>
</entry>
<entry>
<title>[lldb] Also include the array definition in CommandOptions.inc</title>
<updated>2019-07-28T06:24:07+00:00</updated>
<author>
<name>Raphael Isemann</name>
<email>teemperor@gmail.com</email>
</author>
<published>2019-07-28T06:24:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=bd68a052f292b5df7c5717bd880d796ac7507fc0'/>
<id>urn:sha1:bd68a052f292b5df7c5717bd880d796ac7507fc0</id>
<content type='text'>
Summary:
Right now our CommandOptions.inc only generates the initializer for the options list but
not the array declaration boilerplate around it. As the array definition is identical for all arrays,
we might as well also let the CommandOptions.inc generate it alongside the initializers.

This patch will also allow us to generate additional declarations related to that option list in
the future (e.g. a enum class representing the specific options which would make our
handling code less prone).

This patch also fixes a few option tables that didn't follow our naming style.

Reviewers: JDevlieghere

Reviewed By: JDevlieghere

Subscribers: abidh, lldb-commits

Tags: #lldb

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

llvm-svn: 367186
</content>
</entry>
<entry>
<title>[lldb] Don't dynamically allocate the posix option validator.</title>
<updated>2019-07-26T11:46:21+00:00</updated>
<author>
<name>Raphael Isemann</name>
<email>teemperor@gmail.com</email>
</author>
<published>2019-07-26T11:46:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=0ab0bb91aad5fd880399ab78bc06d7e140e66b84'/>
<id>urn:sha1:0ab0bb91aad5fd880399ab78bc06d7e140e66b84</id>
<content type='text'>
We dynamically allocate the option validator which means we
can't mark this list of OptionDefinitions as constexpr. It's also
more complicated than necessary.

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