<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm5719-llvm/llvm/test/Bitcode, 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-14T13:41:32+00:00</updated>
<entry>
<title>AArch64: fix bitcode upgrade of @llvm.neon.addp.</title>
<updated>2020-01-14T13:41:32+00:00</updated>
<author>
<name>Tim Northover</name>
<email>t.p.northover@gmail.com</email>
</author>
<published>2020-01-09T14:28:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=77cc690bae310f4cba0a34f2da8a37a7c9a10a82'/>
<id>urn:sha1:77cc690bae310f4cba0a34f2da8a37a7c9a10a82</id>
<content type='text'>
We were upgrading it to faddp, but a version taking two type parameters instead
of one. This then got upgraded a second time to the version with just one
parameter, but occasionally (for reasons I don't understand) this unusual
two-stage process corrupted a use-list, leading to a crash when the two faddp
declarations didn't match.
</content>
</entry>
<entry>
<title>Ignore "no-frame-pointer-elim" and "no-frame-pointer-elim-non-leaf" in favor of "frame-pointer"</title>
<updated>2019-12-30T17:46:19+00:00</updated>
<author>
<name>Fangrui Song</name>
<email>maskray@google.com</email>
</author>
<published>2019-12-25T02:12:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=03b9f0a5e19aa68fb0a82d80e409333db7ee511c'/>
<id>urn:sha1:03b9f0a5e19aa68fb0a82d80e409333db7ee511c</id>
<content type='text'>
D56351 (included in LLVM 8.0.0) introduced "frame-pointer".  All tests
which use "no-frame-pointer-elim" or "no-frame-pointer-elim-non-leaf"
have been migrated to use "frame-pointer".

Implement UpgradeFramePointerAttributes to upgrade the two obsoleted
function attributes for bitcode. Their semantics are ignored.

Differential Revision: https://reviews.llvm.org/D71863
</content>
</entry>
<entry>
<title>Migrate function attribute "no-frame-pointer-elim"="false" to "frame-pointer"="none" as cleanups after D56351</title>
<updated>2019-12-25T00:27:51+00:00</updated>
<author>
<name>Fangrui Song</name>
<email>maskray@google.com</email>
</author>
<published>2019-12-25T00:11:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=a36ddf0aa9db5c1086e04f56b5f077b761712eb5'/>
<id>urn:sha1:a36ddf0aa9db5c1086e04f56b5f077b761712eb5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Migrate function attribute "no-frame-pointer-elim" to "frame-pointer"="all" as cleanups after D56351</title>
<updated>2019-12-24T23:57:33+00:00</updated>
<author>
<name>Fangrui Song</name>
<email>maskray@google.com</email>
</author>
<published>2019-12-24T23:52:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=502a77f125f43ffde57af34d3fd1b900248a91cd'/>
<id>urn:sha1:502a77f125f43ffde57af34d3fd1b900248a91cd</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add support for multi-module bitcode files to llvm-dis</title>
<updated>2019-11-14T18:40:41+00:00</updated>
<author>
<name>Matthew Voss</name>
<email>matthew.voss@sony.com</email>
</author>
<published>2019-11-13T00:29:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=141bb5f308fa108045400622889a21a12c4ed41c'/>
<id>urn:sha1:141bb5f308fa108045400622889a21a12c4ed41c</id>
<content type='text'>
Summary:
This change allows llvm-dis to disassemble multi-module bitcode
files, including the associated module summary.

Reviewers: tejohnson, pcc, mehdi_amini

Subscribers: llvm-commits

Tags: #llvm

Differential Revision: https://reviews.llvm.org/D70153
</content>
</entry>
<entry>
<title>[IR] Redefine Freeze instruction</title>
<updated>2019-11-12T01:49:00+00:00</updated>
<author>
<name>aqjune</name>
<email>aqjune@gmail.com</email>
</author>
<published>2019-11-06T16:17:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=e87d71668e10f51abe4b2f1f3c44591aca783750'/>
<id>urn:sha1:e87d71668e10f51abe4b2f1f3c44591aca783750</id>
<content type='text'>
Summary:
This patch redefines freeze instruction from being UnaryOperator to a subclass of UnaryInstruction.

ConstantExpr freeze is removed, as discussed in the previous review.
FreezeOperator is not added because there's no ConstantExpr freeze.
`freeze i8* null` test is added to `test/Bindings/llvm-c/freeze.ll` as well, because the null pointer-related bug in `tools/llvm-c/echo.cpp` is now fixed.
InstVisitor has visitFreeze now because freeze is not unaryop anymore.

Reviewers: whitequark, deadalnix, craig.topper, jdoerfert, lebedev.ri

Reviewed By: craig.topper, lebedev.ri

Subscribers: regehr, nlopes, mehdi_amini, hiraditya, steven_wu, dexonsmith, jfb, llvm-commits

Tags: #llvm

Differential Revision: https://reviews.llvm.org/D69932
</content>
</entry>
<entry>
<title>[ThinLTO] Import readonly vars with refs</title>
<updated>2019-11-07T12:13:35+00:00</updated>
<author>
<name>evgeny</name>
<email>eleviant@accesssoftek.com</email>
</author>
<published>2019-11-07T12:13:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=dde589389fcb8b5098f7a47f1b781b27d29a0cac'/>
<id>urn:sha1:dde589389fcb8b5098f7a47f1b781b27d29a0cac</id>
<content type='text'>
Patch allows importing declarations of functions and variables, referenced
by the initializer of some other readonly variable.
Differential revision: https://reviews.llvm.org/D69561
</content>
</entry>
<entry>
<title>[IR] Add Freeze instruction</title>
<updated>2019-11-05T06:54:56+00:00</updated>
<author>
<name>aqjune</name>
<email>aqjune@gmail.com</email>
</author>
<published>2019-11-05T06:53:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=58acbce3def63a207b8f5a69318a99666a4aac53'/>
<id>urn:sha1:58acbce3def63a207b8f5a69318a99666a4aac53</id>
<content type='text'>
Summary:
- Define Instruction::Freeze, let it be UnaryOperator
- Add support for freeze to LLLexer/LLParser/BitcodeReader/BitcodeWriter
  The format is `%x = freeze &lt;ty&gt; %v`
- Add support for freeze instruction to llvm-c interface.
- Add m_Freeze in PatternMatch.
- Erase freeze when lowering IR to SelDag.

Reviewers: deadalnix, hfinkel, efriedma, lebedev.ri, nlopes, jdoerfert, regehr, filcab, delcypher, whitequark

Reviewed By: lebedev.ri, jdoerfert

Subscribers: jfb, kristof.beyls, hiraditya, lebedev.ri, steven_wu, dexonsmith, xbolva00, delcypher, spatel, regehr, trentxintong, vsk, filcab, nlopes, mehdi_amini, deadalnix, llvm-commits

Differential Revision: https://reviews.llvm.org/D29011
</content>
</entry>
<entry>
<title>[IR] Allow fast math flags on calls with floating point array type.</title>
<updated>2019-10-30T14:00:33+00:00</updated>
<author>
<name>Jay Foad</name>
<email>jay.foad@amd.com</email>
</author>
<published>2019-10-17T08:25:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=2da4b6e51450e8a6a40755cc5a40ebb6289766a5'/>
<id>urn:sha1:2da4b6e51450e8a6a40755cc5a40ebb6289766a5</id>
<content type='text'>
Summary:
This extends the rules for when a call instruction is deemed to be an
FPMathOperator, which is based on the type of the call (i.e. the return
type of the function being called). Previously we only allowed
floating-point and vector-of-floating-point types. Now we also allow
arrays (nested to any depth) of floating-point and
vector-of-floating-point types.

This was motivated by llpc, the pipeline compiler for AMD GPUs
(https://github.com/GPUOpen-Drivers/llpc). llpc has many math library
functions that operate on vectors, typically represented as &lt;4 x float&gt;,
and some that operate on matrices, typically represented as
[4 x &lt;4 x float&gt;], and it's useful to be able to decorate calls to all
of them with fast math flags.

Reviewers: spatel, wristow, arsenm, hfinkel, aemerson, efriedma, cameron.mcinally, mcberg2017, jmolloy

Subscribers: wdng, llvm-commits

Tags: #llvm

Differential Revision: https://reviews.llvm.org/D69161
</content>
</entry>
<entry>
<title>Add Windows Control Flow Guard checks (/guard:cf).</title>
<updated>2019-10-28T15:19:39+00:00</updated>
<author>
<name>Andrew Paverd</name>
<email>andrew.paverd@microsoft.com</email>
</author>
<published>2019-10-28T13:22:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=d157a9bc8ba1085cc4808c6941412322a7fd884e'/>
<id>urn:sha1:d157a9bc8ba1085cc4808c6941412322a7fd884e</id>
<content type='text'>
Summary:
A new function pass (Transforms/CFGuard/CFGuard.cpp) inserts CFGuard checks on
indirect function calls, using either the check mechanism (X86, ARM, AArch64) or
or the dispatch mechanism (X86-64). The check mechanism requires a new calling
convention for the supported targets. The dispatch mechanism adds the target as
an operand bundle, which is processed by SelectionDAG. Another pass
(CodeGen/CFGuardLongjmp.cpp) identifies and emits valid longjmp targets, as
required by /guard:cf. This feature is enabled using the `cfguard` CC1 option.

Reviewers: thakis, rnk, theraven, pcc

Subscribers: ychen, hans, metalcanine, dmajor, tomrittervg, alex, mehdi_amini, mgorny, javed.absar, kristof.beyls, hiraditya, steven_wu, dexonsmith, cfe-commits, llvm-commits

Tags: #clang, #llvm

Differential Revision: https://reviews.llvm.org/D65761
</content>
</entry>
</feed>
