similar to: [LLVMdev] Clang Integration with MSVS 2013

Displaying 20 results from an estimated 2000 matches similar to: "[LLVMdev] Clang Integration with MSVS 2013"

2015 Mar 09
2
[LLVMdev] LLVM 3.6: problems building on Windows using MSVC 2013
Hi, I have been using LLVM+Clang in my project for some time and it has been working just fine up to now (I am currently using version 3.5.1). However, with version 3.6 having just been released, I thought I would give it a try and update my code to use MCJIT rather than the now discontinued JIT. Well, this proved to be a relatively smooth process, and everything is now working fine on
2015 Mar 09
2
[LLVMdev] LLVM 3.6: problems building on Windows using MSVC 2013
Sorry, I am using CMake+JOM or CMake+Ninja, if Ninja is available on the developer’s machine. Either way, it fails in both cases with a message similar to the one I included below (which was obtained using CMake+Ninja). Just in case, my (current) CMakeLists.txt file can be found at here
2012 Sep 27
4
[LLVMdev] Clang bug?
Is this a relevant location to provide information about what I believe is a compiler bug in clang? If not, please forgive me for posting it here. (Perhaps you can redirect me to some place more appropriate.) If so, here are the details: I have a short 15-line C++ program using only one standard header that clang fails to compile properly under C++11 with the new standard library (although the
2012 Jul 09
2
[LLVMdev] Unable to do even basic Clang tutorial
I'm trying to do the tutorials at: https://github.com/loarabia/Clang-tu...i/TutorialOrig and I can't even do the first tutorial. I installed LLVM 3.1 and Clang 3.1 and when I do: ~/loarabia-Clang-tutorial-3d79443$ clang++ tutorial1.cpp In file included from tutorial1.cpp:5: In file included from ./llvm/Support/raw_ostream.h:17: ./llvm/Support/llvm/ADT/StringRef.h:13:10: fatal error:
2012 Sep 28
0
[LLVMdev] Clang bug?
That is one evil bug! I just tested it against tip-of-trunk clang and it appears to be fixed there (just fyi for everyone). Howard On Sep 27, 2012, at 7:17 PM, Adam Peterson <alpha.eta.pi at gmail.com> wrote: > Is this a relevant location to provide information about what I > believe is a compiler bug in clang? If not, please forgive me for > posting it here. (Perhaps you can
2012 Sep 29
2
[LLVMdev] Clang bug?
On Fri, Sep 28, 2012 at 6:45 PM, Howard Hinnant <hhinnant at apple.com> wrote: > On Sep 28, 2012, at 5:54 PM, Richard Smith <richard at metafoo.co.uk> wrote: > > > Reduced testcase: > > > > template<typename T> struct A { typedef decltype(T() + 0) type; }; > > template<typename T> struct B { > > struct C { typedef typename
2012 Sep 29
0
[LLVMdev] Clang bug?
On Sep 28, 2012, at 10:18 PM, Richard Smith <richard at metafoo.co.uk> wrote: > On Fri, Sep 28, 2012 at 6:45 PM, Howard Hinnant <hhinnant at apple.com> wrote: > On Sep 28, 2012, at 5:54 PM, Richard Smith <richard at metafoo.co.uk> wrote: > > > Reduced testcase: > > > > template<typename T> struct A { typedef decltype(T() + 0) type; }; > >
2019 Feb 11
2
[cfe-dev] [8.0.0 Release] rc2 has been tagged
On Fri, Feb 8, 2019 at 9:53 AM Paweł Sikora via cfe-dev < cfe-dev at lists.llvm.org> wrote: > ----- Oryginalna wiadomość ----- > > Dear testers, > > > > 8.0.0-rc2 has been tagged from the release_80 branch at r353413. > > Hi, > > i've noticed a compile error with rc2 and libc++ (release_80 @svn). looks > similar to
2012 Sep 28
4
[LLVMdev] Clang bug?
Reduced testcase: template<typename T> struct A { typedef decltype(T() + 0) type; }; template<typename T> struct B { struct C { typedef typename A<C*>::type type; }; typedef typename A<C*>::type type; }; B<int> b; ... produces ... <stdin>:3:38: error: no type named 'type' in 'A<B<int>::C *>' struct C { typedef typename
2012 Jul 09
3
[LLVMdev] Unable to do even basic Clang tutorial
On 7/9/2012 1:42 PM, Chad Rosier wrote: > Have you looked here: http://clang.llvm.org/get_started.html > > Chad > > > On Jul 9, 2012, at 11:33 AM, NY Knicks Fan wrote: > >> I'm trying to do the tutorials at: >> >> https://github.com/loarabia/Clang-tu...i/TutorialOrig >> <https://github.com/loarabia/Clang-tutorial/wiki/TutorialOrig> >>
2012 Sep 29
0
[LLVMdev] Clang bug?
This doesn't appear to me to be the same issue (but of course I don't know clang as well as you all do). This code appears invalid (and G++ rejects it with a similar "no type named ..." error message), whereas the original code is valid C++ (both C++98 and C++11). On Fri, Sep 28, 2012 at 3:54 PM, Richard Smith <richard at metafoo.co.uk> wrote: > Reduced testcase: >
2012 Jul 09
1
[LLVMdev] Unable to do even basic Clang tutorial
I'm trying to do the tutorials at: https://github.com/loarabia/Clang-tu...i/TutorialOrig and I can't even do the first tutorial. I installed LLVM 3.1 and Clang 3.1 and when I do: ~/loarabia-Clang-tutorial-3d79443$ clang++ tutorial1.cpp In file included from tutorial1.cpp:5: In file included from ./llvm/Support/raw_ostream.h:17: ./llvm/Support/llvm/ADT/StringRef.h:13:10: fatal error:
2012 Jul 09
0
[LLVMdev] Unable to do even basic Clang tutorial
Have you looked here: http://clang.llvm.org/get_started.html Chad On Jul 9, 2012, at 11:33 AM, NY Knicks Fan wrote: > I'm trying to do the tutorials at: > > https://github.com/loarabia/Clang-tu...i/TutorialOrig > > and I can't even do the first tutorial. I installed LLVM 3.1 and Clang 3.1 and when I do: > > ~/loarabia-Clang-tutorial-3d79443$ clang++
2012 Jul 09
0
[LLVMdev] Unable to do even basic Clang tutorial
Hi Ashok, The documentation suggests that I put clang inside of llvm/tools and so I have two separate include directories.  I tried both of them and neither worked: $ clang++ -I llvm/include tutorial1.cpp  In file included from tutorial1.cpp:5: In file included from llvm/include/llvm/Support/raw_ostream.h:17: In file included from llvm/include/llvm/ADT/StringRef.h:13:
2014 Dec 17
5
[LLVMdev] How to figure out what #includes are needed?
This is partly an llvm question, and maybe partly C++. I am trying to make calls on code in the llvm infrastructure.(3.4.2) I appear to be missing some include files, but don't know how to track them down. I get compile errors on existing llvm header files, like the following two examples: -------------------------------------------------------------------------------- In file included
2012 Jul 09
3
[LLVMdev] Unable to do even basic Clang tutorial
The "make install" should collect everything into your <install path>. The <install path> will then have bin, lib and include dirs. On 7/9/2012 3:52 PM, NY Knicks Fan wrote: > Hi Ashok, > > The documentation suggests that I put clang inside of llvm/tools and so > I have two separate include directories. I tried both of them and > neither worked: > > $
2012 Jul 09
4
[LLVMdev] Unable to do even basic Clang tutorial
Use the -I<install path>/include . This directory <install path>/include should look something like: clang/ clang-c/ llvm/ llvm-c/ HTH ashok On 7/9/2012 3:15 PM, NY Knicks Fan wrote: > I downloaded the 3.1 LLVM and Clang sources. > > I followed the directions at: http://clang.llvm.org/get_started.html > > I am able to use Clang to compile stuff, but I could
2012 Jul 09
0
[LLVMdev] Unable to do even basic Clang tutorial
I downloaded the 3.1 LLVM and Clang sources. I followed the directions at: http://clang.llvm.org/get_started.html I am able to use Clang to compile stuff, but I could already do that with GCC. I'm trying to use Clang for parsing code, but I can't even get started. Can you tell me how to "include the installed location of  clang/llvm headers directories in your include path"?
2012 Jul 09
0
[LLVMdev] Unable to do even basic Clang tutorial
On Jul 9, 2012, at 4:00 PM, Ashok Nalkund wrote: > The "make install" should collect everything into your <install path>. > The <install path> will then have bin, lib and include dirs. And you should be able to specify the install path with the --prefix option when configuring. I believe the default is /usr/local (see: configure --help to verify). Chad > On
2019 Aug 03
3
conflicting builtins in clang with musl (stddef.h)
Hello there, I'm building a Linux distribution based on musl and LLVM as default toolchain (including lld/libc++/libc++abi/libunwind rather than GNU). For most of the time this works pretty well. However I'm having troubles with few packages, webkit for instance fails because of max_align_t being redeclared in musl's stddef.h I see that stddef.h is provided by both musl and in the