Project Ortega BCM5719 LLVM https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1 2019-09-05T02:20:39+00:00 2019-09-05T02:20:39+00:00 Matt Arsenault Matthew.Arsenault@amd.com 2019-09-05T02:20:39+00:00 urn:sha1:f581d575ce0a8bdcd580c2c6626c10cda6873100 The library currently uses ptrtoint and directly checks the queue ptr for this, which counts as a pointer capture. llvm-svn: 371009 2019-06-17T14:13:29+00:00 Matt Arsenault Matthew.Arsenault@amd.com 2019-06-17T14:13:29+00:00 urn:sha1:1df203d78e478bea989736fd9f1657adea70db0d If an addrspacecast needed to be inserted again, this was creating a clone of the original cast for each user. Just use the original, which also saves losing the value name. llvm-svn: 363562 2019-06-17T14:13:24+00:00 Matt Arsenault Matthew.Arsenault@amd.com 2019-06-17T14:13:24+00:00 urn:sha1:b10f0978334ab2beb4477497323ddb6d44399b62 Even if the target doesn't have flat instructions, addrspace(0) is still flat. It just happens to not work. llvm-svn: 363561 2019-06-17T09:51:07+00:00 Fangrui Song maskray@google.com 2019-06-17T09:51:07+00:00 urn:sha1:ac14f7b10cffe2be548607269e036244cd16acc3 llvm-svn: 363538 2019-05-10T14:57:42+00:00 Michael Liao michael.hliao@gmail.com 2019-05-10T14:57:42+00:00 urn:sha1:b284414a1bf1be379cd28c8a10075f0d5238d18d Summary: - Constant expressions may not be added in strict postorder as the forward instruction scan order. Thus, for a constant express (CE0), if its operand (CE1) is used in an previous instruction, they are not in postorder. However, different from `cloneInstructionWithNewAddressSpace`, `cloneConstantExprWithNewAddressSpace` doesn't bookkeep uninferred instructions for later resolving. That results in failure of inferring constant address. - This patch adds the support to infer constant expression operand recursively, since there won't be loop, if that operand is another constant expression. Reviewers: arsenm Subscribers: jholewinski, jvesely, wdng, nhaehnle, hiraditya, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D61760 llvm-svn: 360431 2019-04-17T04:52:47+00:00 Eric Christopher echristo@gmail.com 2019-04-17T04:52:47+00:00 urn:sha1:cee313d288a4faf0355d76fb6e0e927e211d08a5 The reversion apparently deleted the test/Transforms directory. Will be re-reverting again. llvm-svn: 358552 2019-04-17T02:12:23+00:00 Eric Christopher echristo@gmail.com 2019-04-17T02:12:23+00:00 urn:sha1:a86343512845c9c1fdbac865fea88aa5fce7142a As it's causing some bot failures (and per request from kbarton). This reverts commit r358543/ab70da07286e618016e78247e4a24fcb84077fda. llvm-svn: 358546 2019-03-12T21:02:54+00:00 Matt Arsenault Matthew.Arsenault@amd.com 2019-03-12T21:02:54+00:00 urn:sha1:caf1316f7100e1ba1e7e800eae6a5adf0d48bf90 This indicates an intrinsic parameter is required to be a constant, and should not be replaced with a non-constant value. Add the attribute to all AMDGPU and generic intrinsics that comments indicate it should apply to. I scanned other target intrinsics, but I don't see any obvious comments indicating which arguments are intended to be only immediates. This breaks one questionable testcase for the autoupgrade. I'm unclear on whether the autoupgrade is supposed to really handle declarations which were never valid. The verifier fails because the attributes now refer to a parameter past the end of the argument list. llvm-svn: 355981 2019-03-02T08:32:32+00:00 Xing GUO higuoxing@gmail.com 2019-03-02T08:32:32+00:00 urn:sha1:23b1dfe675cb026e746d85d648b2ecdf07067eb7 llvm-svn: 355265 2019-02-21T12:31:36+00:00 Joey Gouly joey.gouly@gmail.com 2019-02-21T12:31:36+00:00 urn:sha1:92af1360f33178a5d8d02afb5a81d185cec2acc1 Check the operands of a select are pointers, to determine if it is an address expression or not. https://reviews.llvm.org/D58226 llvm-svn: 354576