llvm/lib/IR, branch release_33http://llvm.orghttps://git.amat.us/llvm/atom/lib/IR?h=release_332013-05-06T01:48:55ZFix const merging when an alias of a const is llvm.used.2013-05-06T01:48:55ZRafael Espindolarafael.espindola@gmail.com2013-05-06T01:48:55Zurn:sha1:eaf14786ca3975266ed7041ac242122c02baf1cf
We used to disable constant merging not only if a constant is llvm.used, but
also if an alias of a constant is llvm.used. This change fixes that.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181175 91177308-0d34-0410-b5e6-96231b3b80d8
Add ArrayRef constructor from None, and do the cleanups that this constructor enables2013-05-05T00:40:33ZDmitri Gribenkogribozavr@gmail.com2013-05-05T00:40:33Zurn:sha1:5c332dbd30d9398ed25b30c3080506f7b8e92290
Patch by Robert Wilhelm.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181138 91177308-0d34-0410-b5e6-96231b3b80d8
This patch breaks up Wrap.h so that it does not have to include all of 2013-05-01T20:59:00ZFilip Pizlofpizlo@apple.com2013-05-01T20:59:00Zurn:sha1:40be1e85665d10f5444186f0e7106e368dd735b8
the things, and renames it to CBindingWrapping.h. I also moved
CBindingWrapping.h into Support/.
This new file just contains the macros for defining different wrap/unwrap
methods.
The calls to those macros, as well as any custom wrap/unwrap definitions
(like for array of Values for example), are put into corresponding C++
headers.
Doing this required some #include surgery, since some .cpp files relied
on the fact that including Wrap.h implicitly caused the inclusion of a
bunch of other things.
This also now means that the C++ headers will include their corresponding
C API headers; for example Value.h must include llvm-c/Core.h. I think
this is harmless, since the C API headers contain just external function
declarations and some C types, so I don't believe there should be any
nasty dependency issues here.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@180881 91177308-0d34-0410-b5e6-96231b3b80d8
Now that the underlying issue is fixed, revert r180750 and r180722.2013-05-01T13:07:03ZRafael Espindolarafael.espindola@gmail.com2013-05-01T13:07:03Zurn:sha1:aae0298921d946a64385052ce6e678d36f936fb3
The cause of the windows failures was fixed by r180791. Revert to the state
after Sabre's original revert.
Original message:
revert r179735, it has no testcases, and doesn't really make sense.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@180844 91177308-0d34-0410-b5e6-96231b3b80d8
Change getSlotIndex to return unsigned.2013-04-30T16:53:38ZRafael Espindolarafael.espindola@gmail.com2013-04-30T16:53:38Zurn:sha1:76f103e02164d27b41bd92a9767c7012482ba31a
The actual storage was already using unsigned, but the interface was using
uint64_t. This is wasteful on 32 bits and looks to be the root causes of
a miscompilation on Windows where a value was being sign extended to 64bits
to compare with the result of getSlotIndex.
Patch by Pasi Parviainen!
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@180791 91177308-0d34-0410-b5e6-96231b3b80d8
Revert the command line option patch. However, keep the part that makes this pass on Windows. I.e., we don't emit the target dependent attributes in a comment before the function.2013-04-29T23:48:06ZBill Wendlingisanbard@gmail.com2013-04-29T23:48:06Zurn:sha1:725dae57916800c7371c5008bd451fb3edb273b2
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@180750 91177308-0d34-0410-b5e6-96231b3b80d8
Revert "revert r179735, it has no testcases, and doesn't really make sense."2013-04-29T18:23:53ZReid Klecknerreid@kleckner.net2013-04-29T18:23:53Zurn:sha1:f2e83499fcc41484cb5dac073c4fe87525926d2b
This un-reverts r179735 and reverts commit r180574.
This fixes assertion failures for me locally and should fix the failures
on Windows reported widely on llvm-dev. We should check if the bots
caught this and if so why not.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@180722 91177308-0d34-0410-b5e6-96231b3b80d8
revert r179735, it has no testcases, and doesn't really make sense.2013-04-25T20:34:16ZChris Lattnersabre@nondot.org2013-04-25T20:34:16Zurn:sha1:29fce9ad39636d38f43add5d7c23e83d9d1cc249
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@180574 91177308-0d34-0410-b5e6-96231b3b80d8
Add some constraints to use of 'returned':2013-04-23T16:31:56ZStephen Linstephenwlin@gmail.com2013-04-23T16:31:56Zurn:sha1:13aba14eb5c643234f5d756b94f30afb28f8cd5d
1) Disallow 'returned' on parameter that is also 'sret' (no sensible semantics, as far as I can tell).
2) Conservatively disallow tail calls through 'returned' parameters that also are 'zext' or 'sext' (for consistency with treatment of other zero-extending and sign-extending operations in tail call position detection...can be revised later to handle situations that can be determined to be safe).
This is a new attribute that is not yet used, so there is no impact.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@180118 91177308-0d34-0410-b5e6-96231b3b80d8
Expose IRBuilder::CreateAtomicRMW as LLVMBuildAtomicRMW in llvm-c.2013-04-23T13:21:19ZCarlo Kokck@remobjects.com2013-04-23T13:21:19Zurn:sha1:8effd8dc98a793181b086dbfde31cdcbd2047200
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@180100 91177308-0d34-0410-b5e6-96231b3b80d8