similar to: [LLVMdev] [CMake] Generated LLVMConfig.cmake and LLVMExports.cmake broken under Visual Studio 2015

On 06/18/2015 06:46 PM, Dan Liew wrote: >> The issue is the that that generated LLVMExports.cmake file has this in it >> INTERFACE_LINK_LIBRARIES "LLVMObject;LLVMSupport;C:\Program Files (x86)\Microsoft Visual Studio 14.0\DIA SDK\lib\diaguids.lib" > > Hmm actually this might be a bug in the > ``/lib/DebugInfo/PDB/CMakeLists.txt`` file. CC'ing Zach Turner seeing

Greetings, As of LLVM 5.0.1, LLVM generates a dependency on diaguids.lib if it finds DIA SDK available. This is ok, however llvm-config.exe does not expose the path to the library, so it results in these link errors: LLVMDebugInfoPDB.lib(DIASession.obj) : error LNK2019: unresolved external symbol "long __cdecl NoRegCoCreate(wchar_t const *,struct _GUID const &,struct _GUID const

Hi, On Sun, Jan 17, 2016 at 1:04 PM, Dan Liew <dan at su-root.co.uk> wrote: > On 16 January 2016 at 20:21, Ismail Donmez <ismail at i10z.com> wrote: >> On Sat, Jan 16, 2016 at 9:33 PM, Dan Liew <dan at su-root.co.uk> wrote: >>>> I am trying to enable this on openSUSE but it seems to break >>>> standalone lldb (note that we don't ship static

On Thu, Feb 18, 2016 at 10:03 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > > On Feb 18, 2016, at 8:42 AM, Philip Reames via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > On 02/18/2016 06:54 AM, Hal Finkel via llvm-dev wrote: > >> Hi Chandler, et al., > >> > >> While this proposal to put IR into the test suite

>I think the real question is: Is this the best way to have a kind of 'halide buildbot' that can inform the LLVM developer community? Halide already has a buildbot running every few hours which is being used to inform LLVM developer community when something breaks. It would be a lot more useful however to have the tests in an LLVM repository to inform LLVM devs which test broke right

On Mon, Oct 10, 2016 at 1:14 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 10 October 2016 at 19:39, Alina Sbirlea <alina.sbirlea at gmail.com> > wrote: > > Now, for ARM archs Halide is currently generating explicit VSTn > intrinsics, > > with some of the patterns I described, and I found no reason why Halide > > shouldn't generate a single

On 6 July 2015 at 10:34, Ben Pope <benpope81 at gmail.com> wrote: > On 7 July 2015 at 01:12, Dan Liew <dan at su-root.co.uk> wrote: >> >> >> @Ben Pope: Your uploaded binary tarball is the odd one out. Any idea >> as to why the CMake files are missing and why the root directory name >> inside the tarball is not consistent with the uploaded tarballs for

Hi Ben, Thanks for taking the time to look at this. >> It's not necessary for CMake to be installed when building with the >> Autoconf/Makefile build system. If you look in the build directory >> after a build has been performed you should see in cmake/modules >> >> ``` >> LLVMBuildExports.cmake LLVMConfig.cmake LLVMConfigVersion.cmake >>

On 02/18/2016 09:08 AM, David Blaikie wrote: > > > On Thu, Feb 18, 2016 at 8:42 AM, Philip Reames via llvm-dev > <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > > > > On 02/18/2016 06:54 AM, Hal Finkel via llvm-dev wrote: > > Hi Chandler, et al., > > While this proposal to put IR into the test suite

Sent from my iPhone > On Feb 29, 2016, at 3:39 PM, Alina Sbirlea <alina.sbirlea at gmail.com> wrote: > > > >> On Mon, Feb 29, 2016 at 2:06 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: >> >>> On Feb 29, 2016, at 1:50 PM, Alina Sbirlea <alina.sbirlea at gmail.com> wrote: >>> >>> >>> >>> On Mon, Feb

----- Original Message ----- > From: "Mehdi Amini via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Alina Sbirlea" <alina.sbirlea at gmail.com> > Cc: "llvm-dev" <llvm-dev at lists.llvm.org> > Sent: Monday, February 29, 2016 7:06:51 PM > Subject: Re: [llvm-dev] RFC: Add bitcode tests to test-suite > Sent from my iPhone > On Feb

On Mon, Feb 29, 2016 at 2:06 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > On Feb 29, 2016, at 1:50 PM, Alina Sbirlea <alina.sbirlea at gmail.com> > wrote: > > > > On Mon, Feb 29, 2016 at 12:18 PM, Mehdi Amini <mehdi.amini at apple.com> > wrote: > >> >> On Feb 29, 2016, at 11:40 AM, Mehdi Amini via llvm-dev < >> llvm-dev at

> On Feb 29, 2016, at 11:28 PM, Chandler Carruth <chandlerc at google.com> wrote: > > I really don't understand this. Why is a C++ reference useful? Instead, we have an IR reference: the unoptimized IR. Mmmmm, thinking more about it, yes we could compile the IR two times and use the unoptimized one as a reference. However, right now the tests are only running llc, so the

Some perhaps relevant aspects that make testing users of LLVM like Halide challenging: Halide uses the LLVM C++ APIs, but there isn't a good way to lock-step update it. So if we were to directly test Halide, it wouldn't link against the new LLVM. Practically speaking though, the LLVM IR generated by Halide should continue to work with newer LLVM optimizations and code generation. So the

I really don't understand this. Why is a C++ reference useful? Instead, we have an IR reference: the unoptimized IR. I think it pretty important to not phrase everything in terms of C or C++ or Clang... =/ What if there are IR constructs that simply cannot be produced by C++? We're adding lots of those for managed languages. If there is a practical concern with having IR-based test

On Thu, Feb 18, 2016 at 10:03 AM, Mehdi Amini via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > On Feb 18, 2016, at 8:42 AM, Philip Reames via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > On 02/18/2016 06:54 AM, Hal Finkel via llvm-dev wrote: > >> Hi Chandler, et al., > >> > >> While this proposal to put IR into the

Hi, I can't reproduce your issue on the LLVM 3.5 release branch or trunk it. Looking at your bug report I think your install is messed up ``` CMake Error at /usr/local/Cellar/llvm/HEAD/share/llvm/cmake/LLVMExports.cmake:6 (set_property): set_property could not find TARGET LLVMSupport. Perhaps it has not yet been created. Call Stack (most recent call first):

On 09/09/2014 10:12 AM, Dan Liew wrote: > because my Linux distribution just upgraded to LLVM/Clang 3.5 and I > noticed that trying use find_package(LLVM ...) was broken :( AFAIK, that never worked in any version of LLVM not built by CMake before. That's why we taught cmake/modules/Makefile to generate LLVMConfig.cmake and LLVMExports.cmake. > What is happening is that none of the

Hi Renato, Thank you for the answers! First, let me clarify a couple of things and give some context. The patch it looking at VSTn, rather than VLDn (stores seem to be somewhat harder to get the "right" patterns, the pass is doing a good job for loads already) The examples you gave come mostly from loop vectorization, which, as I understand it, was the reason for adding the

Hi again, On Fri, Jan 15, 2016 at 11:05 AM, Ismail Donmez <ismail at i10z.com> wrote: > Hi, > > On Fri, Jan 15, 2016 at 12:59 AM, Chris Bieneman <beanz at apple.com> wrote: >> I’m kinda scared that you’re using it. What are you trying to accomplish >> that you are using it? Generally having LLVM split among that many >> dynamically loaded libraries results