<feed xmlns='http://www.w3.org/2005/Atom'>
<title>llvm/test, branch master</title>
<subtitle>http://llvm.org</subtitle>
<id>https://git.amat.us/llvm/atom/test?h=master</id>
<link rel='self' href='https://git.amat.us/llvm/atom/test?h=master'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/'/>
<updated>2013-05-14T02:00:24Z</updated>
<entry>
<title>This is the first of three patches which creates stubs used for</title>
<updated>2013-05-14T02:00:24Z</updated>
<author>
<name>Reed Kotler</name>
<email>rkotler@mips.com</email>
</author>
<published>2013-05-14T02:00:24Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=eafa96485a6c3ce0de4f511ed080a64a7a44f2bb'/>
<id>urn:sha1:eafa96485a6c3ce0de4f511ed080a64a7a44f2bb</id>
<content type='text'>
Mips16/32 floating point interoperability.

When Mips16 code calls external functions that would normally have some
of its parameters or return values passed in floating point registers,
it needs (Mips32) helper functions to do this because while in Mips16 mode
there is no ability to access the floating point registers.

In Pic mode, this is done with a set of predefined functions in libc.
This case is already handled in llvm for Mips16.

In static relocation mode, for efficiency reasons, the compiler generates
stubs that the linker will use if it turns out that the external function
is a Mips32 function. (If it's Mips16, then it does not need the helper
stubs).

These stubs are identically named and the linker knows about these tricks
and will not create multiple copies and will delete them if they are not
needed.



git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181753 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
<entry>
<title>StackColoring: don't clear an instruction's mem operand if the underlying</title>
<updated>2013-05-14T01:42:44Z</updated>
<author>
<name>Akira Hatanaka</name>
<email>ahatanaka@mips.com</email>
</author>
<published>2013-05-14T01:42:44Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=dd29df06fa72de9e370cdd9d8e32ac5437a578c7'/>
<id>urn:sha1:dd29df06fa72de9e370cdd9d8e32ac5437a578c7</id>
<content type='text'>
object is a PseudoSourceValue and PseudoSourceValue::isConstant returns true (i.e.,
points to memory that has a constant value).



git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181751 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
<entry>
<title>LoopVectorize: Handle loops with multiple forward inductions</title>
<updated>2013-05-14T00:21:18Z</updated>
<author>
<name>Arnold Schwaighofer</name>
<email>aschwaighofer@apple.com</email>
</author>
<published>2013-05-14T00:21:18Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=123f18bcb9baeb6dc177cb642126a3a4d9ca8b43'/>
<id>urn:sha1:123f18bcb9baeb6dc177cb642126a3a4d9ca8b43</id>
<content type='text'>
We used to give up if we saw two integer inductions. After this patch, we base
further induction variables on the chosen one like we do in the reverse
induction and pointer induction case.

Fixes PR15720.

radar://13851975

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181746 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
<entry>
<title>[objc-arc-opts] In the presense of an alloca unconditionally remove RR pairs if and only if we are both KnownSafeBU/KnownSafeTD rather than just either or.</title>
<updated>2013-05-13T23:49:42Z</updated>
<author>
<name>Michael Gottesman</name>
<email>mgottesman@apple.com</email>
</author>
<published>2013-05-13T23:49:42Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=acfb3584c58159ec20a8379c864c9d644f8d967e'/>
<id>urn:sha1:acfb3584c58159ec20a8379c864c9d644f8d967e</id>
<content type='text'>
In the presense of a block being initialized, the frontend will emit the
objc_retain on the original pointer and the release on the pointer loaded from
the alloca. The optimizer will through the provenance analysis realize that the
two are related (albiet different), but since we only require KnownSafe in one
direction, will match the inner retain on the original pointer with the guard
release on the original pointer. This is fixed by ensuring that in the presense
of allocas we only unconditionally remove pointers if both our retain and our
release are KnownSafe (i.e. we are KnownSafe in both directions) since we must
deal with the possibility that the frontend will emit what (to the optimizer)
appears to be unbalanced retain/releases.

An example of the miscompile is:

  %A = alloca
  retain(%x)
  retain(%x) &lt;--- Inner Retain
  store %x, %A
  %y = load %A
  ... DO STUFF ...
  release(%y)
  call void @use(%x)
  release(%x) &lt;--- Guarding Release

getting optimized to:

  %A = alloca
  retain(%x)
  store %x, %A
  %y = load %A
  ... DO STUFF ...
  release(%y)
  call void @use(%x)

rdar://13750319

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181743 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
<entry>
<title>Mips assembler: Assembler macro ADDIU $rs,imm</title>
<updated>2013-05-13T20:26:46Z</updated>
<author>
<name>Jack Carter</name>
<email>jack.carter@imgtec.com</email>
</author>
<published>2013-05-13T20:26:46Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=f4a1377322a9234c17b1d324c47248bdb5f62158'/>
<id>urn:sha1:f4a1377322a9234c17b1d324c47248bdb5f62158</id>
<content type='text'>
This patch adds alias for addiu instruction which enables following syntax:

    addiu $rs,imm

The macro is translated as:

    addiu $rs,$rs,imm


Contributer: Vladimir Medic


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181729 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
<entry>
<title>PPC64: Constant initializers with dynamic relocations go in .data.rel.ro.</title>
<updated>2013-05-13T19:34:37Z</updated>
<author>
<name>Bill Schmidt</name>
<email>wschmidt@linux.vnet.ibm.com</email>
</author>
<published>2013-05-13T19:34:37Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=240b9b6078cdf8048945107b4ff7d517729dab96'/>
<id>urn:sha1:240b9b6078cdf8048945107b4ff7d517729dab96</id>
<content type='text'>
This fixes warning messages observed in the oggenc application test in
projects/test-suite.  Special handling is needed for the 64-bit
PowerPC SVR4 ABI when a constant is initialized with a pointer to a
function in a shared library.  Because a function address is
implemented as the address of a function descriptor, the use of copy
relocations can lead to problems with initialization.  GNU ld
therefore replaces copy relocations with dynamic relocations to be
resolved by the dynamic linker.  This means the constant cannot reside
in the read-only data section, but instead belongs in .data.rel.ro,
which is designed for constants containing dynamic relocations.

The implementation creates a class PPC64LinuxTargetObjectFile
inheriting from TargetLoweringObjectFileELF, which behaves like its
parent except to place constants of this sort into .data.rel.ro.

The test case is reduced from the oggenc application.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181723 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
<entry>
<title>[mips] Add option -mno-ldc1-sdc1.</title>
<updated>2013-05-13T18:23:35Z</updated>
<author>
<name>Akira Hatanaka</name>
<email>ahatanaka@mips.com</email>
</author>
<published>2013-05-13T18:23:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=42f562a1694d24b41f36bbb4d4a086a2a470c625'/>
<id>urn:sha1:42f562a1694d24b41f36bbb4d4a086a2a470c625</id>
<content type='text'>
This option is used when the user wants to avoid emitting double precision FP
loads and stores. Double precision FP loads and stores are expanded to single
precision instructions after register allocation.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181718 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
<entry>
<title>The purpose of the patch is to fix the syntax of ARM mrc and mrc2 instructions when they are used to write to the APSR. In this case, the destination operand should be APSR_nzcv, and the encoding of the target should be 0b1111 (same as for PC). In pre-UAL syntax, this form used the PC register as a textual target. This is still allowed for backward compatibility.</title>
<updated>2013-05-13T14:10:04Z</updated>
<author>
<name>Mihai Popa</name>
<email>mihail.popa@gmail.com</email>
</author>
<published>2013-05-13T14:10:04Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=f86e436fb95670ed110818fefa403f21ae104639'/>
<id>urn:sha1:f86e436fb95670ed110818fefa403f21ae104639</id>
<content type='text'>
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181705 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
<entry>
<title>Correctly preserve the input chain for potential tailcall nodes whose</title>
<updated>2013-05-13T10:21:19Z</updated>
<author>
<name>Lang Hames</name>
<email>lhames@gmail.com</email>
</author>
<published>2013-05-13T10:21:19Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=d26c93d3a8a484c5b42f06163ae5de787f0ac276'/>
<id>urn:sha1:d26c93d3a8a484c5b42f06163ae5de787f0ac276</id>
<content type='text'>
return values are bitcasts.

The chain had previously been being clobbered with the entry node to
the dag, which sometimes caused other code in the function to be
erroneously deleted when tailcall optimization kicked in.

&lt;rdar://problem/13827621&gt;


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181696 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
<entry>
<title>Fix PR15950 A bug in DAG Combiner about undef mask</title>
<updated>2013-05-13T02:07:05Z</updated>
<author>
<name>Hao Liu</name>
<email>Hao.Liu@arm.com</email>
</author>
<published>2013-05-13T02:07:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=3778c04b2e3bc879cb7f175ba4d42f23fb9cef76'/>
<id>urn:sha1:3778c04b2e3bc879cb7f175ba4d42f23fb9cef76</id>
<content type='text'>
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181682 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
</feed>
