similar to: [LLVMdev] Windows build problems for LLVM 3.1

GCC is smart enough to realize it doesn't return. That's because the declaration of abort() is decorated with __attribute__((__noreturn__)). So is GCC smarter than VC++? As it turns out, in VC++ the declaration of abort() is decorated with __declspec(noreturn). Whidbey is not stricter than 2003, it is merely buggier. VC++ has always complained about functions failing to return a

> GCC is smart enough to realize it doesn't return. That's because the > declaration of abort() is decorated with __attribute__((__noreturn__)). > > So is GCC smarter than VC++? As it turns out, in VC++ the declaration of > abort() is decorated with __declspec(noreturn). > > Whidbey is not stricter than 2003, it is merely buggier. VC++ has always > complained

I'm following the instructions here: http://clasg.llvm.org/get_started.html and, while running cmake, I get: > CMake Error at cmake/modules/LLVM-Config.cmake:141 (message): > Library `vectorize' not found in list of llvm libraries. > Call Stack (most recent call first): > cmake/modules/LLVM-Config.cmake:54 (explicit_map_components_to_libraries) >

Hi Jean-Daniel, Thank I use VC++ 9 (express version). I have also an error in TableGen: The "strtoll" could not be found under win32. Have you fixed it ? Regards Quang -----Ursprüngliche Nachricht----- Von: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] Im Auftrag von Jean-Daniel Dupas Gesendet: Montag, 30. Juni 2008 22:00 An: LLVM Developers Mailing List

Not this one, I have a different error here. One related to hasmap and pair templates. I will check this on my Windows machine later. Le 1 juil. 08 à 16:44, Le Anh Quang a écrit : > Hi Jean-Daniel, > Thank > I use VC++ 9 (express version). I have also an error in TableGen: The > "strtoll" could not be found under win32. Have you fixed it ? > > Regards > Quang

Chris Lattner wrote: > On Thu, 9 Jun 2005, Alexander Friedman wrote: > >> On Jun 9, Chris Lattner wrote: >> >>>> I'm happy with .so. What purpose would .o files serve? >>> >>> >>> Speeds up compile time by not having to write out a .s file then run >>> the >>> system assembler on it. Likewise, emitting a .so file

----Original Message Follows---- From: Jeff Cohen <jeffc at jolt-lang.org> Reply-To: jeffc at jolt-lang.org, LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Subject: Re: [LLVMdev] VC++: Cannot open include file: 'windows.h': No suchfile or directory Date: Tue, 21 Dec 2004 16:29:47 -0800

Hi Jean-Daniel, thank for ur fast answer, i have fixed this error, another function was defined inside llvm source code. So, my only problem now is, I cannot create the file "configure.lib" (belongs to project "Configure"). I can build this project without error, but it didn't generate the lib data ?! Can you build this file ? if yes, I will be very happy if you send it to

On Mar 22, 2012, at 11:40 AM, Paul J. Lucas <paul at lucasmail.org> wrote: > On Mar 22, 2012, at 12:28 AM, Bill Wendling wrote: > >> On Mar 20, 2012, at 7:38 PM, Paul J. Lucas wrote: >> >>> I've read the docs on LLVM exceptions, but I don't see any examples. A little help? >> >> I don't think this has anything to do with LLVM's

Yes, it should find windows.h with the default configuration. But you have to be suspicious of beta code that Microsoft gives out for free. It might just be very buggy, or it might be deliberately crippled. Considering the price tag on Visual Studio, it's one or the other (and probably both). Out of curiosity, did it accept the solution and project files as is, or did it want to

Aaron Gray wrote: >> GCC is smart enough to realize it doesn't return. That's because the >> declaration of abort() is decorated with __attribute__((__noreturn__)). >> >> So is GCC smarter than VC++? As it turns out, in VC++ the >> declaration of abort() is decorated with __declspec(noreturn). >> >> Whidbey is not stricter than 2003, it is

Switching to CodeGenOpt::None reduced the execution time from 5.74s to 0.84s. By just tweaking things randomly, changing to CodeModel::Small reduced it further to 0.22s. We have some old, ugly, pure C++ code that we're trying to replace (both because it's ugly and because it's slow). It's execution time is about 0.089s, so that's the time to beat. Hence, I'd like to

AFAK, the Configuration project does not generate any output. It just patch and generate some required header file. Le 1 juil. 08 à 17:32, Le Anh Quang a écrit : > Hi Jean-Daniel, > thank for ur fast answer, i have fixed this error, another function > was > defined inside llvm source code. > So, my only problem now is, I cannot create the file "configure.lib" >

I have searched through the threads and "Rprintf" causing a build error dosen't seem to be a problem for anyone else. And I've read through "R Extensions" and "An Introduction to the .C Interface to R" and there doesn't seem to be any troubleshooting for my problem. My code is straight from "An Introduction to the .C Interface to R" pg. 3. And

Hi all, While testing my compiler on win32 in JIT mode, I ran into a couple of issues: 1. I linked the compiler with the lib files resulting from the cmake created VS.NET build. While everything built just fine, the ExecutionEngine::create call always returned NULL. The fix was to also link with JIT.obj (thanks aKor for pointing me in the right direction). I would have thought that linking

On Oct 2, 2012, at 2:34 PM, Eli Friedman <eli.friedman at gmail.com> wrote: > On Tue, Oct 2, 2012 at 11:33 AM, Paul J. Lucas <paul at lucasmail.org> wrote: > >> My understanding is that, in order to use GEP, you have to provide the LLVM code with the struct layout, i.e., build a StructType object. In my case, that struct is declared in C++ code already and, in order to

Chris Lattner <sabre at nondot.org> writes: [snip] > Others have suggested alternative build systems before like cmake. > Apparently cmake can autogenerate VC++ and Xcode project files from > the same thing that it builds from on unix systems. cmake creating VC++ project files does not appeal much to me. First, project files are not mandatory for using MS compiler. Second,

On Sun, Oct 27, 2013 at 5:09 PM, Chris Lattner <clattner at apple.com> wrote: > On Oct 27, 2013, at 12:07 PM, Óscar Fuentes <ofv at wanadoo.es> wrote: >> Chris Lattner <clattner at apple.com> writes: >> >>>> One short term caveat: Windows is special. >> >> s/Windows/Visual Studio. >> >> MinGW has the latest and greatest gcc.

Le 30 juin 08 à 21:28, Le Anh Quang a écrit : > Hi, > I have tried to compile LLVM with Visual C++. Some subprojects work > now. > > Other subprojects require the file "configure.lib". So I tried to > compile > the project "Configure". It could be built successfully, but the file > "configure.lib" is not generated. So, what is the problem

I've been profiling more; see <https://dl.dropbox.com/u/46791180/perf.png>. One thing I'm a bit confused about is why I see a FunctionPassManager there. I use a FunctionPassManager at the end of LLVM IR code generation, write the IR to disk, then read it back later. Why is apparently another FunctionPassManager being used during the JIT'ing of the IR code? And how do I