<feed xmlns='http://www.w3.org/2005/Atom'>
<title>llvm/test/CodeGen, branch master</title>
<subtitle>http://llvm.org</subtitle>
<id>https://git.amat.us/llvm/atom/test/CodeGen?h=master</id>
<link rel='self' href='https://git.amat.us/llvm/atom/test/CodeGen?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>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>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>
<entry>
<title>Add -mtriple=mipsel-linux-gnu to the test so that the compiler does</title>
<updated>2013-05-11T01:02:20Z</updated>
<author>
<name>Reed Kotler</name>
<email>rkotler@mips.com</email>
</author>
<published>2013-05-11T01:02:20Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=a6e31cf69e1c9853bb02bad2fa0bcac0dd67997d'/>
<id>urn:sha1:a6e31cf69e1c9853bb02bad2fa0bcac0dd67997d</id>
<content type='text'>
not think it can support small data sections.



git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181654 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
<entry>
<title>Checkin in of first of several patches to finish implementation of</title>
<updated>2013-05-10T22:25:39Z</updated>
<author>
<name>Reed Kotler</name>
<email>rkotler@mips.com</email>
</author>
<published>2013-05-10T22:25:39Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=46090914b783b632618268f2a5c99aab83732688'/>
<id>urn:sha1:46090914b783b632618268f2a5c99aab83732688</id>
<content type='text'>
mips16/mips32 floating point interoperability. 

This patch fixes returns from mips16 functions so that if the function
was in fact called by a mips32 hard float routine, then values
that would have been returned in floating point registers are so returned.

Mips16 mode has no floating point instructions so there is no way to
load values into floating point registers.

This is needed when returning float, double, single complex, double complex
in the Mips ABI.

Helper functions in libc for mips16 are available to do this.

For efficiency purposes, these helper functions have a different calling
convention from normal Mips calls.

Registers v0,v1,a0,a1 are used to pass parameters instead of
a0,a1,a2,a3.

This is because v0,v1,a0,a1 are the natural registers used to return
floating point values in soft float. These values can then be moved
to the appropriate floating point registers with no extra cost.

The only register that is modified is ra in this call.

The helper functions make sure that the return values are in the floating
point registers that they would be in if soft float was not in effect
(which it is for mips16, though the soft float is implemented using a mips32
library that uses hard float).
 


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181641 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
<entry>
<title>Hexagon: Fix switch cases in HexagonVLIWPacketizer.cpp.</title>
<updated>2013-05-10T20:27:34Z</updated>
<author>
<name>Jyotsna Verma</name>
<email>jverma@codeaurora.org</email>
</author>
<published>2013-05-10T20:27:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=1a35b8e2eb165624013d5a2eaf8b673f026999fc'/>
<id>urn:sha1:1a35b8e2eb165624013d5a2eaf8b673f026999fc</id>
<content type='text'>
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181624 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
<entry>
<title>DAGCombiner: Generate a correct constant for vector types when folding (xor (and)) into (and (not)).</title>
<updated>2013-05-10T14:09:52Z</updated>
<author>
<name>Benjamin Kramer</name>
<email>benny.kra@googlemail.com</email>
</author>
<published>2013-05-10T14:09:52Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=768ebcdf631baa1b18dc65a5983a237b307a99c2'/>
<id>urn:sha1:768ebcdf631baa1b18dc65a5983a237b307a99c2</id>
<content type='text'>
PR15948.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181597 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
</feed>
