<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm5719-llvm/clang/test/Lexer, 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-02-19T21:37:59+00:00</updated>
<entry>
<title>Add -std=c++20 flag, replace C++2a with C++20 throughout the Clang</title>
<updated>2020-02-19T21:37:59+00:00</updated>
<author>
<name>Richard Smith</name>
<email>richard@metafoo.co.uk</email>
</author>
<published>2020-02-19T00:13:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=5175565cf154aede57354336102a7f6e15a16a20'/>
<id>urn:sha1:5175565cf154aede57354336102a7f6e15a16a20</id>
<content type='text'>
user interface and documentation, and update __cplusplus for C++20.

WG21 considers the C++20 standard to be finished (even though it still
has some more steps to pass through in the ISO process).

The old flag names are accepted for compatibility, as usual, and we
still have lots of references to C++2a in comments and identifiers;
those can be cleaned up separately.

(cherry picked from commit 24ad121582454e625bdad125c90d9ac0dae948c8)
</content>
</entry>
<entry>
<title>[Concepts] Deprecate -fconcepts-ts, enable Concepts under -std=c++2a</title>
<updated>2020-01-24T00:28:33+00:00</updated>
<author>
<name>Saar Raz</name>
<email>saar@raz.email</email>
</author>
<published>2020-01-23T22:43:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=2ec65e229314d468006998eaef7074b86ef7482d'/>
<id>urn:sha1:2ec65e229314d468006998eaef7074b86ef7482d</id>
<content type='text'>
Now with concepts support merged and mostly complete, we do not need -fconcepts-ts
(which was also misleading as we were not implementing the TS) and can enable
concepts features under C++2a. A warning will be generated if users still attempt
to use -fconcepts-ts.

(cherry picked from commit 67c608a9695496cfc9d3fdf9d0b12b554ac6b4df)
</content>
</entry>
<entry>
<title>Fix crash on init-capture packs where the type of the initializer is non-dependent.</title>
<updated>2019-12-19T23:20:10+00:00</updated>
<author>
<name>Richard Smith</name>
<email>richard@metafoo.co.uk</email>
</author>
<published>2019-12-19T23:18:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=f4a45c2ce4ce2a7a33d5773048682e65f348a486'/>
<id>urn:sha1:f4a45c2ce4ce2a7a33d5773048682e65f348a486</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Implement latest C++ feature test macro recommendations.</title>
<updated>2019-12-19T20:59:13+00:00</updated>
<author>
<name>Richard Smith</name>
<email>richard@metafoo.co.uk</email>
</author>
<published>2019-12-19T20:57:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=df2e2ab07b48b81fb440e3522c6e639e8ef8f2e9'/>
<id>urn:sha1:df2e2ab07b48b81fb440e3522c6e639e8ef8f2e9</id>
<content type='text'>
We don't yet advertise init capture packs, because I found some bugs
while testing it. We reject-valid and then crash on both of these:

template&lt;int ...a&gt; auto x = [...y = a] {};
template&lt;int ...a&gt; auto x = [y = a...] {};
</content>
</entry>
<entry>
<title>Mark the major papers for C++20 consistent comparisons as "done", and</title>
<updated>2019-12-16T06:20:06+00:00</updated>
<author>
<name>Richard Smith</name>
<email>richard@metafoo.co.uk</email>
</author>
<published>2019-12-16T06:20:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=bc633a42dd409dbeb456263e3388b8caa4680aa0'/>
<id>urn:sha1:bc633a42dd409dbeb456263e3388b8caa4680aa0</id>
<content type='text'>
start publishing the corresponding feature-test macro.
</content>
</entry>
<entry>
<title>Revert "Revert "As a follow-up to my initial mail to llvm-dev here's a first pass at the O1 described there.""</title>
<updated>2019-11-27T04:28:52+00:00</updated>
<author>
<name>Eric Christopher</name>
<email>echristo@gmail.com</email>
</author>
<published>2019-11-27T04:28:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=fd39b1bb20cec32c310ae9b6f1b4603c17a5f832'/>
<id>urn:sha1:fd39b1bb20cec32c310ae9b6f1b4603c17a5f832</id>
<content type='text'>
This reapplies: 8ff85ed905a7306977d07a5cd67ab4d5a56fafb4

Original commit message:

As a follow-up to my initial mail to llvm-dev here's a first pass at the O1 described there.

This change doesn't include any change to move from selection dag to fast isel
and that will come with other numbers that should help inform that decision.
There also haven't been any real debuggability studies with this pipeline yet,
this is just the initial start done so that people could see it and we could start
tweaking after.

Test updates: Outside of the newpm tests most of the updates are coming from either
optimization passes not run anymore (and without a compelling argument at the moment)
that were largely used for canonicalization in clang.

Original post:

http://lists.llvm.org/pipermail/llvm-dev/2019-April/131494.html

Tags: #llvm
Differential Revision: https://reviews.llvm.org/D65410

This reverts commit c9ddb02659e3ece7a0d9d6b4dac7ceea4ae46e6d.
</content>
</entry>
<entry>
<title>Revert "As a follow-up to my initial mail to llvm-dev here's a first pass at the O1 described there."</title>
<updated>2019-11-26T04:32:13+00:00</updated>
<author>
<name>Muhammad Omair Javaid</name>
<email>omair.javaid@linaro.org</email>
</author>
<published>2019-11-26T04:32:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=c9ddb02659e3ece7a0d9d6b4dac7ceea4ae46e6d'/>
<id>urn:sha1:c9ddb02659e3ece7a0d9d6b4dac7ceea4ae46e6d</id>
<content type='text'>
This reverts commit 8ff85ed905a7306977d07a5cd67ab4d5a56fafb4.

This commit introduced 9 new failures on lldb buildbot host at http://lab.llvm.org:8014/builders/lldb-aarch64-ubuntu

Following tests were failing:
    lldb-api :: functionalities/tail_call_frames/ambiguous_tail_call_seq1/TestAmbiguousTailCallSeq1.py
    lldb-api :: functionalities/tail_call_frames/ambiguous_tail_call_seq2/TestAmbiguousTailCallSeq2.py
    lldb-api :: functionalities/tail_call_frames/disambiguate_call_site/TestDisambiguateCallSite.py
    lldb-api :: functionalities/tail_call_frames/disambiguate_paths_to_common_sink/TestDisambiguatePathsToCommonSink.py
    lldb-api :: functionalities/tail_call_frames/disambiguate_tail_call_seq/TestDisambiguateTailCallSeq.py
    lldb-api :: functionalities/tail_call_frames/inlining_and_tail_calls/TestInliningAndTailCalls.py
    lldb-api :: functionalities/tail_call_frames/sbapi_support/TestTailCallFrameSBAPI.py
    lldb-api :: functionalities/tail_call_frames/thread_step_out_message/TestArtificialFrameStepOutMessage.py
    lldb-api :: functionalities/tail_call_frames/thread_step_out_or_return/TestSteppingOutWithArtificialFrames.py
    lldb-api :: functionalities/tail_call_frames/unambiguous_sequence/TestUnambiguousTailCalls.py

Tags: #llvm
Differential Revision: https://reviews.llvm.org/D65410
</content>
</entry>
<entry>
<title>As a follow-up to my initial mail to llvm-dev here's a first pass at the O1 described there.</title>
<updated>2019-11-26T01:16:46+00:00</updated>
<author>
<name>Eric Christopher</name>
<email>echristo@gmail.com</email>
</author>
<published>2019-11-26T00:33:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=8ff85ed905a7306977d07a5cd67ab4d5a56fafb4'/>
<id>urn:sha1:8ff85ed905a7306977d07a5cd67ab4d5a56fafb4</id>
<content type='text'>
This change doesn't include any change to move from selection dag to fast isel
and that will come with other numbers that should help inform that decision.
There also haven't been any real debuggability studies with this pipeline yet,
this is just the initial start done so that people could see it and we could start
tweaking after.

Test updates: Outside of the newpm tests most of the updates are coming from either
optimization passes not run anymore (and without a compelling argument at the moment)
that were largely used for canonicalization in clang.

Original post:

http://lists.llvm.org/pipermail/llvm-dev/2019-April/131494.html

Tags: #llvm
Differential Revision: https://reviews.llvm.org/D65410
</content>
</entry>
<entry>
<title>Mark P0784R7 as complete and start defining its feature-test macro.</title>
<updated>2019-10-03T00:39:37+00:00</updated>
<author>
<name>Richard Smith</name>
<email>richard-llvm@metafoo.co.uk</email>
</author>
<published>2019-10-03T00:39:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=69e9d84b1ad1c208a4c502d3def8e9234b161e65'/>
<id>urn:sha1:69e9d84b1ad1c208a4c502d3def8e9234b161e65</id>
<content type='text'>
Note that this only covers the language side of this feature. (The
library side has its own feature test macro.)

llvm-svn: 373548
</content>
</entry>
<entry>
<title>Move normalization of `\` in #includes from -fms-compatibility to -fms-extensions</title>
<updated>2019-09-26T17:19:22+00:00</updated>
<author>
<name>Reid Kleckner</name>
<email>rnk@google.com</email>
</author>
<published>2019-09-26T17:19:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=adc183018715ee979c2e2532b9669f480b6bf37c'/>
<id>urn:sha1:adc183018715ee979c2e2532b9669f480b6bf37c</id>
<content type='text'>
Handling backslashes in include paths in the implementation isn't
non-conforming.

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