similar to: [LLVMdev] compiling rev. 116572 on you-know-what

Hi, I stumbled across three warnings in LLVM when building with MS Visual Studio 2010. It has been my experience that different compilers detect different things, so I thought I'd pass them on to you (in case your compiler does not warn about these things): warning C4805: '==' : unsafe mix of type 'bool' and type 'unsigned int' in operation

Hi, I have included the oggvorbis encoding and playback stuff in the Linux-Mandrake distro back in August 2000. At that time I put the "nightly CVS" version, which worked just fine. Then on Mon Nov 27 I noticed some RPM's labelled "1.0beta3" on the website so I upgraded with these ones. Since then we have had some serious problems in encoding: approx 20% of the WAV

We still have the program called "KillTheDoctor" [1] in our source tree. Its original intention was to stop requiring user interaction for crashing regression tests under Windows (infamous Dr. Watson, nowadays "[program] has stopped working" [2]), I don't think it is useful anymore. It's also a very hacky approach, as admitted in the source comment itself ("I hate

Hi Eli and Others In response to your feedback, I have taken care of all your review comments - I removed clangOMP.a and moved the implementation of "class OmpPragmaHandler" to "clangLex.a". The attached zipped file - namely - 'OpenMP_support_in_Clang.tar.gz' contains all the implemented "patches" along with *newly* added source files. Another attached text

I am willing to take code ownership responsibilities for the following: {include/llvm,lib}/{Object,Support} tools/{ar,nm,objdump,ranlib,size} utils/{kate,KillTheDoctor,obj2yaml,yaml2obj,yaml-bench} - Michael Spencer

On Wed, Oct 10, 2012 at 5:40 AM, Eli Friedman <eli.friedman at gmail.com>wrote: > On Tue, Oct 9, 2012 at 4:37 AM, Mahesha HS <mahesha.llvm at gmail.com> wrote: > > Hello All, > > > > We would like to make a proposal to support OpenMP in CLANG. The goal of > > this effort is to provide support for syntax > > > > analysis (parsing), semantic

The fact that the templatized constructor falls down because of the possibility of initializing StringRef with a stack-allocated char array kills that idea in my mind. I feel like the only two reasonable solutions are 1) allow UDL for this case, document that this is an exception and that UDLs are still not permitted anywhere else, and require (by policy, since I don't know of a way to have

share/compat.h contains the following code: /* adjust for compilers that can't understand using LLU suffix for uint64_t literals */ #ifdef _MSC_VER #define FLAC__U64L(x) x #else #define FLAC__U64L(x) x##LLU #endif I tested MSVS 2005 and indeed it doesn't support LLU suffix, but it can compile a code with ULL suffix. Also, http://gcc.gnu.org/onlinedocs/gcc/Long-Long.html mentions ?ULL?

AIX 7.1 & Power5 I have downloaded the llvm source and ran the following steps: 1. ./configure --enable-targets=powerpc 2. gmake Apart from it, i had to make a few changes. i. dladdr code has been commented for the time being and using the default constructor code for that method ii. In Makefile.config, 2 changes were done. +153 # Linker flags. +154 LDFLAGS+=-Wl,-G,-bexpfull +211

I googled and found that there was a bug raised with similar issue. http://llvm.org/bugs/show_bug.cgi?id=2210 I applied the code changes mentioned in the bug and it worked. Now, i am stuck at the following error. Working overit .. llvm[2]: Compiling SmallVectorTest.cpp for Release+Asserts build llvm[2]: Compiling SparseBitVectorTest.cpp for Release+Asserts build llvm[2]: Compiling

I now have an implementation of FileOutputBuffer (OutputBuffer was already taken). The patch supports the functionality listed below and I've tested that it works for lld. -------------- next part -------------- A non-text attachment was scrubbed... Name: FileOutputBuffer.patch Type: application/octet-stream Size: 25308 bytes Desc: not available URL:

On 10/23/2012 12:20 PM, Sunil Saggar wrote: > I was able to process further by making some code changes and replacing > export-dynamic with -bexpfull in Makefile.config. Now, i am getting > following error while linking .. > > llvm[3]: Linking Release+Asserts Loadable Module LLVMHello.so What exactly was the linking command? -Krzysztof -- Qualcomm Innovation Center, Inc. is a

Hey there, I'm having trouble getting speex working with a project that uses it. For some quick background, the game Quake 3 was GPL'ed a while ago. Some programmers decided to throw it into a public svn and improve on it, called it ioquake3. One of the blokes integrated speex into ioquake3 and it works, but I have troubles getting it to compile/link properly with Visual Studio 2005. I

Is this a common warning? The decoder doesn't return an error on it, but I see it a lot in my test application on windows. It is non existent on my linux box. I haven't tried mingw yet. please note that I'm using visual studio 2008 w/the vcproj that Bjoern Rasmussen made for 0.5.2 (w/some file references removed) at the moment and it is giving a lot of C4554 warnings

On Thu, May 17, 2012 at 3:25 PM, Nick Kledzik <kledzik at apple.com> wrote: > I now have an implementation of FileOutputBuffer (OutputBuffer was already taken).  The patch supports the functionality listed below and I've tested that it works for lld. > > To implement the FileOutputBuffer, I needed to add some more functions to llvm/Support/FileSystem.h, including: >  

llvm[4]: Compiling PoolAllocate.cpp for Release+Asserts build /home/NIKHILREDDY/WORK/LLVM_SRC/projects/poolalloc/lib/PoolAllocate/PoolAllocate.cpp: In member function ‘virtual bool llvm::PoolAllocate::runOnModule(llvm::Module&)’: /home/NIKHILREDDY/WORK/LLVM_SRC/projects/poolalloc/lib/PoolAllocate/PoolAllocate.cpp:403:16: error: ‘class llvm::Constant’ has no member named

On Mon, Dec 16, 2013 at 04:16:29PM -0800, Michael Dalton wrote: > Commit 2613af0ed18a ("virtio_net: migrate mergeable rx buffers to page frag > allocators") changed the mergeable receive buffer size from PAGE_SIZE to > MTU-size, introducing a single-stream regression for benchmarks with large > average packet size. There is no single optimal buffer size for all >

On Mon, Dec 16, 2013 at 04:16:29PM -0800, Michael Dalton wrote: > Commit 2613af0ed18a ("virtio_net: migrate mergeable rx buffers to page frag > allocators") changed the mergeable receive buffer size from PAGE_SIZE to > MTU-size, introducing a single-stream regression for benchmarks with large > average packet size. There is no single optimal buffer size for all >

Also available here: https://github.com/rwmjones/nbdkit/tree/2020-windows-mingw This is the port to Windows using native Windows APIs (not MSYS or Cygwin). This patch series is at the point where it basically now works. I can run the server with the memory plugin, and access it remotely using guestfish, creating filesystems and so on without any apparent problems. Nevertheless there are many

Also available here: https://github.com/rwmjones/nbdkit/tree/2020-windows-mingw-nolib After a lot of work I have made the port to Windows work without using a separate library. Instead, on Windows only, we build an "import library" (library of stubs) which resolves references to nbdkit_* functions in the main program and fixes up the plugin, basically the first technique outlined in