<feed xmlns='http://www.w3.org/2005/Atom'>
<title>llvm/lib/Transforms/IPO, branch release_30</title>
<subtitle>http://llvm.org</subtitle>
<id>https://git.amat.us/llvm/atom/lib/Transforms/IPO?h=release_30</id>
<link rel='self' href='https://git.amat.us/llvm/atom/lib/Transforms/IPO?h=release_30'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/'/>
<updated>2011-10-01T01:39:05Z</updated>
<entry>
<title>Inlining and unrolling heuristics should be aware of free truncs.</title>
<updated>2011-10-01T01:39:05Z</updated>
<author>
<name>Andrew Trick</name>
<email>atrick@apple.com</email>
</author>
<published>2011-10-01T01:39:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=b2ab2fa524f3f90376639037bd81924483cca0af'/>
<id>urn:sha1:b2ab2fa524f3f90376639037bd81924483cca0af</id>
<content type='text'>
We want heuristics to be based on accurate data, but more importantly
we don't want llvm to behave randomly. A benign trunc inserted by an
upstream pass should not cause a wild swings in optimization
level. See PR11034. It's a general problem with threshold-based
heuristics, but we can make it less bad.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@140919 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
<entry>
<title>whitespace</title>
<updated>2011-10-01T01:27:56Z</updated>
<author>
<name>Andrew Trick</name>
<email>atrick@apple.com</email>
</author>
<published>2011-10-01T01:27:56Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=5c655413cf9466c29e38204ab3f19b33fffd7996'/>
<id>urn:sha1:5c655413cf9466c29e38204ab3f19b33fffd7996</id>
<content type='text'>
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@140916 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
<entry>
<title>Stop emitting instructions with the name "tmp" they eat up memory and have to be uniqued, without any benefit.</title>
<updated>2011-09-27T20:39:19Z</updated>
<author>
<name>Benjamin Kramer</name>
<email>benny.kra@googlemail.com</email>
</author>
<published>2011-09-27T20:39:19Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=a9390a4d5f5d568059a80970d22194b165d097a7'/>
<id>urn:sha1:a9390a4d5f5d568059a80970d22194b165d097a7</id>
<content type='text'>
If someone prefers %tmp42 to %42, run instnamer.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@140634 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
<entry>
<title>Place the check for an exit landing pad where it will be run on both code paths through the if-then-else.</title>
<updated>2011-09-20T22:27:16Z</updated>
<author>
<name>Bill Wendling</name>
<email>isanbard@gmail.com</email>
</author>
<published>2011-09-20T22:27:16Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=b7e807f9a9a74d743547856c4275a320f7b5b15e'/>
<id>urn:sha1:b7e807f9a9a74d743547856c4275a320f7b5b15e</id>
<content type='text'>
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@140195 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
<entry>
<title>Omit extracting a loop if one of the exits is a landing pad.</title>
<updated>2011-09-20T22:23:09Z</updated>
<author>
<name>Bill Wendling</name>
<email>isanbard@gmail.com</email>
</author>
<published>2011-09-20T22:23:09Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=84b6706d9003f6078a81ed7d84f4e49ee70f7ef8'/>
<id>urn:sha1:84b6706d9003f6078a81ed7d84f4e49ee70f7ef8</id>
<content type='text'>
The landing pad must accompany the invoke when it's extracted. However, if it
does, then the loop isn't properly extracted. I.e., the resulting extraction has
a loop in it. The extracted function is then extracted, etc. resulting in an
infinite loop.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@140193 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
<entry>
<title>Check the terminator, not the basic block.</title>
<updated>2011-09-20T20:20:50Z</updated>
<author>
<name>Bill Wendling</name>
<email>isanbard@gmail.com</email>
</author>
<published>2011-09-20T20:20:50Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=8c93d5b602377e9860c32a1367fc697d9684e3ee'/>
<id>urn:sha1:8c93d5b602377e9860c32a1367fc697d9684e3ee</id>
<content type='text'>
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@140176 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
<entry>
<title>When extracting a basic block that ends in an 'invoke' instruction, we need to</title>
<updated>2011-09-20T19:10:24Z</updated>
<author>
<name>Bill Wendling</name>
<email>isanbard@gmail.com</email>
</author>
<published>2011-09-20T19:10:24Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=2f1cd85598d260e5567804460e87f8bee0c5e1e5'/>
<id>urn:sha1:2f1cd85598d260e5567804460e87f8bee0c5e1e5</id>
<content type='text'>
extract its associated landing pad block as well. However, that landing pad
block may have more than one predecessor. So split the landing pad block so that
individual landing pads have only one predecessor.

This type of transformation may produce a false positive with bugpoint.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@140173 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
<entry>
<title>C API functions must be able to see their extern "C" definitions, or it will be impossible to call them from C.</title>
<updated>2011-08-19T01:36:54Z</updated>
<author>
<name>Benjamin Kramer</name>
<email>benny.kra@googlemail.com</email>
</author>
<published>2011-08-19T01:36:54Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=613d13beb03bb56a17e6b3262c5e8e539a7e9db8'/>
<id>urn:sha1:613d13beb03bb56a17e6b3262c5e8e539a7e9db8</id>
<content type='text'>
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@138022 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
<entry>
<title>Add a mechanism for optimisation plugins to register passes that all front ends can use without needing to be aware of the plugin (or the plugin be aware of the front end).</title>
<updated>2011-08-16T13:58:41Z</updated>
<author>
<name>David Chisnall</name>
<email>csdavec@swan.ac.uk</email>
</author>
<published>2011-08-16T13:58:41Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=7a817eae6cb00a2ba5ec2a4127775b839a357e4c'/>
<id>urn:sha1:7a817eae6cb00a2ba5ec2a4127775b839a357e4c</id>
<content type='text'>
Before 3.0, I'd like to add a mechanism for automatically loading a set of plugins from a config file.  API suggestions welcome...



git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@137717 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
<entry>
<title>Revert a bit of r137667; the logic in question can safely handle atomic load/store.</title>
<updated>2011-08-16T01:28:22Z</updated>
<author>
<name>Eli Friedman</name>
<email>eli.friedman@gmail.com</email>
</author>
<published>2011-08-16T01:28:22Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/llvm/commit/?id=2199dfb0e6b98fdce0a3c863eb84d466d426b968'/>
<id>urn:sha1:2199dfb0e6b98fdce0a3c863eb84d466d426b968</id>
<content type='text'>
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@137702 91177308-0d34-0410-b5e6-96231b3b80d8
</content>
</entry>
</feed>
