similar to: [LLVMdev] Visual C Patches for IsNAN.cpp and IsInf.cpp

I submitted a patch keeping the traditional approach, HAVE_FINITE_IN_FLOAT_H and HAVE_ISNAN_IN_FLOAT... Just another case added to the others instead of a custom approach. --- Paolo On Oct 19, 2004, at 12:16 PM, Morten Ofstad wrote: > I don't know if Paolo submitted his patches for these files, but they > are not in the CVS -- I've chosen a slightly different strategy, >

Hi >From: Chris Lattner <sabre at nondot.org> >Date: Thu, 15 Jul 2004 17:43:27 -0500 (CDT) >Ah, suddenly everything makes sense. If you're interested in LLVM on the >windows platform, *please* get CVS. Last night I've got the latest version of LLVM from CVS and now porting LLVM to Interix from this version on. I got this error: --------------------- gmake[1]:

Hi, I just started with LLVM so I'm not sure who's responsible for portability. Anyways, I found the following problems trying to compile llvm rev 94074 with the solution generated using cmake 2.8 (including the clang front end) on 32bit vista: lib/system Errno.cpp : had to add "#undef HAVE_STRERROR_R" raw_ostream.cpp: had to add "#undef HAVE_UNISTD_H"

Hi I'm trying to compile HowToUseJIT.cpp, but it seems that iterator definition is missing: --------------------Configuration: HowToUseJIT - Win32 Debug-------------------- Compiling... HowToUseJIT.cpp c:\sfu\usr\local\src\llvm\include\llvm\adt\ilist(41) : fatal error C1083: Cannot open include file: 'llvm/ADT/iterator': No such file or directory Error executing cl.exe. I've

Hi, i had the same troubles on Vista and on Win7... cmake fails on some tests (you should see this in the log) due to m$ UAC (or whatever the name is) and uses not-so-sane default values. You have to start a visual c-command prompt (to make sure it gets the right paths) with administrator privileges (!) , than cmake works fine and you get a correct config.h. best regards, Thomas 2010/1/22

By the way, somebody (I think it was Chuck, but I don't remember for certain) was asking for the BuildLog.htm from building the llvm.sln file under VS 2005 SP1 for diagnostic purposes; right now the SLN is configured to produce a new BuildLog for each and every one of the projects inside the solution. I don't know who's responsible for this guy, but that's probably not the best way

I've got comments on the code change. The test cases look ok, but I haven't fully checked the math on the half-values. I checked with reference to trunk top-of-tree at revision 156617. I have not compiled the code. lib/AsmParser/LLLexer.cpp Adds support to parse format: 0xH<hexdigits> Tha 0xH format should be described in LangRef.html alongside 0xK<hex> and

>There's a config.h file in the win32 subdirectory that implies that it's >supposed to be concatenated as part of the build process, but it doesn't >seem like that's happening from within the .sln script--am I missing a >pre-build step someplace? When config.h.in is hit in the build of configure the configure project, the configure.h file from the win32 directory is

More on this: Walking through the projects slowly: (*) "Configure" builds with no problem. (*) "support" fails: C:\Prg\llvm-2.2\llvm-2.2\win32>msbuild llvm.sln /t:Build Microsoft (R) Build Engine Version 2.0.50727.1433 [Microsoft .NET Framework, Version 2.0.50727.1433] Copyright (C) Microsoft Corporation 2005. All rights reserved. Build started 2/18/2008 12:07:45 AM.

Hi David, Many thanks for the comments! > Tha 0xH format should be described in LangRef.html alongside > 0xK<hex> and 0xM<hex> Done. > Declaration of "int shiftcount" should be moved to smallest nesting > possible, right after "if ( const ConstantFP ..." at line 710 > > (The code makes a lot more sense with a good comment on the

looks good here. > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Anton Lokhmotov > Sent: Thursday, May 17, 2012 4:51 AM > To: 'David Neto' > Cc: llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] [PATCH] OpenCL half support > > Hi David, > > Many thanks for the comments! > >

On Oct 25, 2011, at 6:09 AM, Marcello Maggioni wrote: > Hi, I'm trying to compile the latest clang/llvm SVN versions and I get > this error on multiple systems : Linking, not compiling, but still. I am getting a similar error when building this morning. > Undefined symbols for architecture x86_64: > "clang::Sema::checkPseudoObjectRValue(clang::Expr*)", referenced

Hi Brian Here's the config.log (I'm not posting it on the dev-list). The automatic gcc macro for Interix is __INTERIX if this is to any help. /Henrik >From: "Brian R. Gaeke" <gaeke at uiuc.edu> >Reply-To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> >To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> >Subject: Re: [LLVMdev]

I have a problem building an extension using ISNAN() on R version 2.0.x. In R 1.9.1 Arith.h and Rmath.h contained code like #ifdef IEEE_754 # define ISNAN(x) (isnan(x)!=0) #else # define ISNAN(x) R_IsNaNorNA(x) #endif #define R_FINITE(x) R_finite(x) int R_IsNaNorNA(double); int R_finite(double); which works. R 2.0.x has # define ISNAN(x) (isnan(x)!=0) unconditionally. This breaks

I have a problem building an extension using ISNAN() on R version 2.0.x. In R 1.9.1 Arith.h and Rmath.h contained code like #ifdef IEEE_754 # define ISNAN(x) (isnan(x)!=0) #else # define ISNAN(x) R_IsNaNorNA(x) #endif #define R_FINITE(x) R_finite(x) int R_IsNaNorNA(double); int R_finite(double); which works. R 2.0.x has # define ISNAN(x) (isnan(x)!=0) unconditionally. This breaks

In the hope of some meaningful response and ignoring the risk of further abuse, let me try to clarify the issue here. I have re-read the 'Writing R Extensions' manual. It seems to me that it clearly says R API functions can be called from from C++ programs, and the API includes the special values ISNAN() and R_FINITE() and the missing test ISNA(). R_FINITE is no problem. It is

Dear R users, Have you experienced any difficulty in calling R's ISNAN() from a C code? I have C codes including ISNAN() calls and they worked well until I upgraded my R from 1.7 to later versions. When I tried to compile the codes in the version 1.8 and 1.9, I got error messages like this: test.obj : error LNK2001: unresolved external symbol _isnan .\testR.dll : fatal error LNK1120: 1

Hi, I'm trying to compile the latest clang/llvm SVN versions and I get this error on multiple systems : (Compiling with gcc): llvm[4]: Compiling cc1_main.cpp for Debug+Asserts build llvm[4]: Compiling cc1as_main.cpp for Debug+Asserts build llvm[4]: Compiling driver.cpp for Debug+Asserts build llvm[4]: Linking Debug+Asserts executable clang

Hello, I submitted a package which used Fortran functions isnan and lgamma. However, I was told that: isnan and lgamma are not Fortran 95 functions. I was asked to write 'cross-platform portable code' and so should not be writing GNU extensions to Fortran. See http://cran.r-project.org/web/checks/check_results_mpath.html, which will shortly show installation failures under Solaris. I

This file is for configure+make build, not CMake, so I'm not sure why it's being included into your build (these failures aren't reproducible for me). Can you please list the exact steps you're doing to build LLVM with CMake and make sure you don't have additional CFLAGS (LDFLAGS etc) defined? On Mon, Nov 11, 2013 at 6:16 PM, Jack Howarth <howarth at bromo.med.uc.edu>