<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size: 12pt; color: rgb(0, 0, 0); font-family: Calibri,Helvetica,sans-serif,"EmojiFont","Apple Color Emoji","Segoe UI Emoji",NotoColorEmoji,"Segoe UI Symbol","Android Emoji",EmojiSymbols;" dir="ltr">
<p>Hi Alex,</p>
<p><br>
</p>
<p>> <font size="2"><span style="font-size:10pt;">Question to my readers: Given Arm's recent rebranding, should that be Armv8.2a or armv8.2a instead?</span></font></p>
<p><font size="2"><span style="font-size:10pt;"><br>
</span></font></p>
<p><font size="2"><span style="font-size:10pt;">None of the above <span>:-) </span>
<br>
</span></font></p>
<p><font size="2"><span style="font-size:10pt;">That should be Armv8.2-A.<br>
</span></font></p>
<p><br>
</p>
<p>Find more info and examples here:<br>
<font size="2"><span style="font-size:10pt;"></span></font></p>
<p><a href="https://www.arm.com/company/policies/trademarks/arm-trademark-list/arm-trademark" class="OWAAutoLink">https://www.arm.com/company/policies/trademarks/arm-trademark-list/arm-trademark</a></p>
<p><br>
</p>
<p>Cheers,</p>
<p>Sjoerd.<br>
</p>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" color="#000000" face="Calibri, sans-serif"><b>From:</b> llvm-dev <llvm-dev-bounces@lists.llvm.org> on behalf of Alex Bradbury via llvm-dev <llvm-dev@lists.llvm.org><br>
<b>Sent:</b> 14 August 2017 19:37<br>
<b>To:</b> llvm-dev<br>
<b>Subject:</b> [llvm-dev] LLVM Weekly - #189, Aug 14th 2017</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">LLVM Weekly - #189, Aug 14th 2017<br>
=================================<br>
<br>
If you prefer, you can read a HTML version of this email at<br>
<<a href="http://llvmweekly.org/issue/189">http://llvmweekly.org/issue/189</a>>.<br>
<br>
Welcome to the one hundred and eighty-ninth issue of LLVM Weekly, a weekly<br>
newsletter (published every Monday) covering developments in LLVM, Clang, and<br>
related projects. LLVM Weekly is brought to you by [Alex<br>
Bradbury](<a href="http://asbradbury.org">http://asbradbury.org</a>). Subscribe to future issues at<br>
<<a href="http://llvmweekly.org">http://llvmweekly.org</a>> and pass it on to anyone else you think may be<br>
interested. Please send any tips or feedback to <asb@asbradbury.org>, or<br>
@llvmweekly or @asbradbury on Twitter.<br>
<br>
<br>
## News and articles from around the web<br>
<br>
If you haven't submitted your talk/tutorial/BoF/panel proposal for the<br>
upcoming LLVM Dev Meeting, you [have a little more<br>
time](<a href="http://lists.llvm.org/pipermail/llvm-dev/2017-August/116437.html">http://lists.llvm.org/pipermail/llvm-dev/2017-August/116437.html</a>). Get<br>
your submission in by today, Monday 14th at 11:59PM PDT.<br>
<br>
LLVM 5.0.0-rc2 has [been<br>
tagged](<a href="http://lists.llvm.org/pipermail/llvm-dev/2017-August/116405.html">http://lists.llvm.org/pipermail/llvm-dev/2017-August/116405.html</a>).<br>
<br>
The call for papers for the LLVM in HPC worksohp at SC17 is [still<br>
open](<a href="http://lists.llvm.org/pipermail/llvm-dev/2017-August/116342.html">http://lists.llvm.org/pipermail/llvm-dev/2017-August/116342.html</a>).<br>
<br>
<br>
## On the mailing lists<br>
<br>
* Marc-André Laperle has given an<br>
[update](http://lists.llvm.org/pipermail/cfe-dev/2017-August/054955.html) on<br>
his prototype to implement indexing support in clangd.<br>
<br>
* Brian Gesiak has posted an [RFC on expanding<br>
-ftime-report](<a href="http://lists.llvm.org/pipermail/cfe-dev/2017-August/054964.html">http://lists.llvm.org/pipermail/cfe-dev/2017-August/054964.html</a>)<br>
to give more information about how time was spent in tasks such as<br>
preprocessing and template instantiation.<br>
<br>
* Alex Bradbury has posted an RFC on [the future of the `va_arg`<br>
instruction](<a href="http://lists.llvm.org/pipermail/llvm-dev/2017-August/116337.html">http://lists.llvm.org/pipermail/llvm-dev/2017-August/116337.html</a>)<br>
in LLVM IR. This RFC hopes to explore where `va_arg` can be used for more<br>
targets and be expanded to handle aggregates, as well as whether that's even a<br>
desirable direction.<br>
<br>
* Kuba Mracek has proposed [dropping the %T expansion in<br>
lit](<a href="http://lists.llvm.org/pipermail/llvm-dev/2017-August/116320.html">http://lists.llvm.org/pipermail/llvm-dev/2017-August/116320.html</a>).<br>
<br>
<br>
## LLVM commits<br>
<br>
* Assembler support has been added for ARMv8.3-A pointer authentication<br>
instructions. [r310709](http://reviews.llvm.org/rL310709).<br>
<br>
* Assembler support has been added for the new release consistent and<br>
processor consistent loads in ARMv8.3-A.<br>
[r310575](http://reviews.llvm.org/rL310575).<br>
<br>
* A basic RISCVAsmParser has landed.<br>
[r310363](http://reviews.llvm.org/rL310363).<br>
<br>
* The TargetTransformInfo::isFoldableMemAccess hook has been removed, as its<br>
functionality is subsumed by isLegalAddressingMode.<br>
[r310463](http://reviews.llvm.org/rL310463).<br>
<br>
* The AArch64 and ARM backends gained assembler support for the ARMv8.2a dot<br>
product instructions. (Question to my readers: Given Arm's recent rebranding,<br>
should that be Armv8.2a or armv8.2a instead?).<br>
[r310480](http://reviews.llvm.org/rL310480),<br>
[r310701](http://reviews.llvm.org/rL310701).<br>
<br>
* A new "Restored" flag has been added to CalleeSavedInfo.<br>
[r310619](http://reviews.llvm.org/rL310619).<br>
<br>
* Most AVX512 broadcast intrinsics have been removed and will be auto-upgraded<br>
when loaded old IR. [r310725](http://reviews.llvm.org/rL310725).<br>
<br>
<br>
## Clang commits<br>
<br>
* The clang-proto-fuzzer tool has been created. This models a subset of C++ as<br>
a protobuf and uses libprotobuf-mutator to generate mutations.<br>
[r310408](http://reviews.llvm.org/rL310408).<br>
<br>
* A couple of minor ABI differences between Clang and GCC related to move<br>
constructors and deleted copy constructors have been fixed.<br>
[r310401](http://reviews.llvm.org/rL310401).<br>
<br>
* clang-tidy gained a new integer division check.<br>
[r310589](http://reviews.llvm.org/rL310589).<br>
<br>
* clang-import-test gained a `-dump-ir` argument, which can be used to help<br>
test completions. [r310318](http://reviews.llvm.org/rL310318).<br>
<br>
<br>
## Other project commits<br>
<br>
* A new tool has been added to LLDB to support Intel Processor Trace.<br>
[r310261](http://reviews.llvm.org/rL310261).<br>
<br>
* AddressSanitizer now supports Fuchsia.<br>
[r310431](http://reviews.llvm.org/rL310431).<br>
<br>
* Polly is now run "before-vectorizer" rather than at the beginning of the<br>
pass pipeline. The advantages of this move are explained in the commit<br>
message. [r310319](http://reviews.llvm.org/rL310319).<br>
_______________________________________________<br>
LLVM Developers mailing list<br>
llvm-dev@lists.llvm.org<br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</div>
</span></font></div>
</div>
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose,
or store or copy the information in any medium. Thank you.
</body>
</html>