<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm5719-llvm/llvm/unittests/ADT/StringRefTest.cpp, 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>2020-01-01T22:29:04+00:00</updated>
<entry>
<title>[polly][Support] Un-break polly tests</title>
<updated>2020-01-01T22:29:04+00:00</updated>
<author>
<name>Alexandre Ganea</name>
<email>alexandre.ganea@ubisoft.com</email>
</author>
<published>2020-01-01T22:23:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=92b68c1937cd065a2fc44d18c1099de7da19b356'/>
<id>urn:sha1:92b68c1937cd065a2fc44d18c1099de7da19b356</id>
<content type='text'>
Previously, the polly unit tests were stuck in a infinite loop.
There was an edge case in StringRef::count() introduced by 9f6b13e5cce96066d7262d224c971d93c2724795, where an empty 'Str' would cause the function to never exit.
Also fixed usage in polly.
</content>
</entry>
<entry>
<title>[Support] Fix behavior of StringRef::count with overlapping occurrences, add tests</title>
<updated>2019-12-25T00:30:41+00:00</updated>
<author>
<name>Johannes Doerfert</name>
<email>johannes@jdoerfert.de</email>
</author>
<published>2019-12-24T23:25:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=9f6b13e5cce96066d7262d224c971d93c2724795'/>
<id>urn:sha1:9f6b13e5cce96066d7262d224c971d93c2724795</id>
<content type='text'>
Summary:
Fix the behavior of StringRef::count(StringRef) to not count overlapping occurrences, as is stated in the documentation.
Fixes bug https://bugs.llvm.org/show_bug.cgi?id=44072

I added Krzysztof Parzyszek to review this change because a use of this function in HexagonInstrInfo::getInlineAsmLength might depend on the overlapping-behavior. I don't have enough domain knowledge to tell if this change could break anything there.

All other uses of this method in LLVM (besides the unit tests) only use single-character search strings. In those cases, search occurrences can not overlap anyway.

Patch by Benno (@Bensge)

Reviewed By: jdoerfert

Differential Revision: https://reviews.llvm.org/D70585
</content>
</entry>
<entry>
<title>[StringRef] Test all default characters in unit test</title>
<updated>2019-12-11T18:46:07+00:00</updated>
<author>
<name>Jonas Devlieghere</name>
<email>jonas@devlieghere.com</email>
</author>
<published>2019-12-11T18:43:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=db76588964ee255da1f32b06565a2cd899a82947'/>
<id>urn:sha1:db76588964ee255da1f32b06565a2cd899a82947</id>
<content type='text'>
The default characters for trim, ltrim and rtrim are " \t\n\v\f\r" but
only spaces were tested. Test that the others are trimmed as well.
</content>
</entry>
<entry>
<title>[ADT] Make StringRef(const char*) constexpr</title>
<updated>2019-08-26T20:47:56+00:00</updated>
<author>
<name>Benjamin Kramer</name>
<email>benny.kra@googlemail.com</email>
</author>
<published>2019-08-26T20:47:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=57effbdadc0b382db4ef86addcfd03a64c9eda0a'/>
<id>urn:sha1:57effbdadc0b382db4ef86addcfd03a64c9eda0a</id>
<content type='text'>
This should let us get rid of StringLiteral in the long term and avoid
chasing accidental StringRef globals once and for all.

This requires C++14, I godbolted it on every compiler I know we support
so I hope there won't be much fallout.

llvm-svn: 369961
</content>
</entry>
<entry>
<title>reland [gtest] Fix printing of StringRef and SmallString in assert messages.</title>
<updated>2019-08-21T13:56:29+00:00</updated>
<author>
<name>Sam McCall</name>
<email>sam.mccall@gmail.com</email>
</author>
<published>2019-08-21T13:56:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=a451156bb6ceb3700f6ea42e47e9a95d67723318'/>
<id>urn:sha1:a451156bb6ceb3700f6ea42e47e9a95d67723318</id>
<content type='text'>
Renames GTEST_NO_LLVM_RAW_OSTREAM -&gt; GTEST_NO_LLVM_SUPPORT and guards
the new features behind it.

This reverts commit a063bcf3ef5a879adbe9639a3c187d876eee0e66.

llvm-svn: 369527
</content>
</entry>
<entry>
<title>Revert "[gtest] Fix printing of StringRef and SmallString in assert messages."</title>
<updated>2019-08-21T13:31:44+00:00</updated>
<author>
<name>Sam McCall</name>
<email>sam.mccall@gmail.com</email>
</author>
<published>2019-08-21T13:31:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=e7c0356b69acd9e7b536c843c056db98f043961d'/>
<id>urn:sha1:e7c0356b69acd9e7b536c843c056db98f043961d</id>
<content type='text'>
This reverts commit 4becb2ab4e9f52ce98272d1f5930d6942af5172b.

llvm-svn: 369525
</content>
</entry>
<entry>
<title>[gtest] Fix printing of StringRef and SmallString in assert messages.</title>
<updated>2019-08-21T11:37:06+00:00</updated>
<author>
<name>Sam McCall</name>
<email>sam.mccall@gmail.com</email>
</author>
<published>2019-08-21T11:37:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=2fe9ce60640762f27294ae60c6b508a5bfb72f2b'/>
<id>urn:sha1:2fe9ce60640762f27294ae60c6b508a5bfb72f2b</id>
<content type='text'>
Summary:
These are detected by gtest as containers, and so previously printed as e.g.
  { '.' (46, 0x2E), 's' (115, 0x73), 'e' (101, 0x65), 'c' (99, 0x63), '0' (48, 0x30) },

gtest itself overloads PrintTo for std::string and friends, we use the same mechanism.

Reviewers: labath

Subscribers: dexonsmith, llvm-commits

Tags: #llvm

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

llvm-svn: 369518
</content>
</entry>
<entry>
<title>[ADT] Enable ArrayRef/StringRef is_assignable tests on MSVC</title>
<updated>2019-07-09T12:20:04+00:00</updated>
<author>
<name>Simon Pilgrim</name>
<email>llvm-dev@redking.me.uk</email>
</author>
<published>2019-07-09T12:20:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=e995ce5498fe255b2a9f69dceb39044de4e8651f'/>
<id>urn:sha1:e995ce5498fe255b2a9f69dceb39044de4e8651f</id>
<content type='text'>
Now that we've dropped VS2015 support (D64326) we can enable these static_asserts on MSVC builds as VS2017+ correctly handles them

llvm-svn: 365471
</content>
</entry>
<entry>
<title>Replace llvm::isPodLike&lt;...&gt;  by llvm::is_trivially_copyable&lt;...&gt;</title>
<updated>2019-01-20T21:19:56+00:00</updated>
<author>
<name>Serge Guelton</name>
<email>sguelton@quarkslab.com</email>
</author>
<published>2019-01-20T21:19:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=be88539b85204041f727ec6499315884b3d886b0'/>
<id>urn:sha1:be88539b85204041f727ec6499315884b3d886b0</id>
<content type='text'>
As noted in https://bugs.llvm.org/show_bug.cgi?id=36651, the specialization for
isPodLike&lt;std::pair&lt;...&gt;&gt; did not match the expectation of
std::is_trivially_copyable which makes the memcpy optimization invalid.

This patch renames the llvm::isPodLike trait into llvm::is_trivially_copyable.
Unfortunately std::is_trivially_copyable is not portable across compiler / STL
versions. So a portable version is provided too.

Note that the following specialization were invalid:

    std::pair&lt;T0, T1&gt;
    llvm::Optional&lt;T&gt;

Tests have been added to assert that former specialization are respected by the
standard usage of llvm::is_trivially_copyable, and that when a decent version
of std::is_trivially_copyable is available, llvm::is_trivially_copyable is
compared to std::is_trivially_copyable.

As of this patch, llvm::Optional is no longer considered trivially copyable,
even if T is. This is to be fixed in a later patch, as it has impact on a
long-running bug (see r347004)

Note that GCC warns about this UB, but this got silented by https://reviews.llvm.org/D50296.

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

llvm-svn: 351701
</content>
</entry>
<entry>
<title>Update the file headers across all of the LLVM projects in the monorepo</title>
<updated>2019-01-19T08:50:56+00:00</updated>
<author>
<name>Chandler Carruth</name>
<email>chandlerc@gmail.com</email>
</author>
<published>2019-01-19T08:50:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=2946cd701067404b99c39fb29dc9c74bd7193eb3'/>
<id>urn:sha1:2946cd701067404b99c39fb29dc9c74bd7193eb3</id>
<content type='text'>
to reflect the new license.

We understand that people may be surprised that we're moving the header
entirely to discuss the new license. We checked this carefully with the
Foundation's lawyer and we believe this is the correct approach.

Essentially, all code in the project is now made available by the LLVM
project under our new license, so you will see that the license headers
include that license only. Some of our contributors have contributed
code under our old license, and accordingly, we have retained a copy of
our old license notice in the top-level files in each project and
repository.

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