search for: rwmutex

...en to: /home/selee/llvm/cmakebuild ~/llvm/cmakebuild$ make After awhile, I got the following error message and couldn't complete the build. ../../lib/libLLVMCore.a(Type.cpp.o): In function `llvm::IntegerType::get(unsigned int)': Type.cpp:(.text+0x394c): undefined reference to `llvm::sys::RWMutex::reader_acquire()' Type.cpp:(.text+0x397a): undefined reference to `llvm::sys::RWMutex::reader_release()' Type.cpp:(.text+0x3a7f): undefined reference to `llvm::sys::RWMutex::writer_acquire()' Type.cpp:(.text+0x3ab1): undefined reference to `llvm::sys::RWMutex::writer_release()' ../...

...63%] Built target LLVMExecutionEngine [ 64%] Built target LLVMInterpreter [ 64%] Built target LLVMJIT [ 67%] Built target LLVMTarget [ 67%] Built target LLVMAsmParser [ 68%] Built target LLVMDebugger [ 68%] Built target LLVMArchive Linking CXX executable ..\..\bin\opt.exe ..\..\lib\libLLVMSystem.a(RWMutex.cpp.obj):RWMutex.cpp:(.text+0x25): undefined r eference to `_imp__pthread_rwlockattr_init' ..\..\lib\libLLVMSystem.a(RWMutex.cpp.obj):RWMutex.cpp:(.text+0x5f): undefined r eference to `_imp__pthread_rwlockattr_setpshared' ..\..\lib\libLLVMSystem.a(RWMutex.cpp.obj):RWMutex.cpp:(.text+0x76):...

Hi, I'm confused by the comment and the source code of lib/Support/Mutex.cpp and lib/Support/RWMutex.cpp. In these files there are: // This variable is useful for situations where the pthread library has been // compiled with weak linkage for its interface symbols. This allows the // threading support to be turned off by simply *not linking against -lpthread*. // In that situation, the value of...

Hi, The old llvm::sys::RWMutex use platform-specific lock mechanism to implement read/write lock. For example, SRWLock on Windows and pthread read/write lock on *nix systems. However, in comparison with the approach that implement read/write lock base on std::atomic, the old methods not only has potential performance issue(Sorr...

Reza Sheykhi <hajishey at msu.edu> writes: > I got the following answers: > > which perl > /usr/bin/perl > > which llvm-config > /usr/local/bin/llvm-config > > which llvm-as > /usr/local/bin/llvm-as > > /usr/bin/llvm-confing --version > bash: /usr/bin/llvm-confing: No such file or directory Uh, there is a typo on the command above, it should be

I got the following answers: which perl /usr/bin/perl which llvm-config /usr/local/bin/llvm-config which llvm-as /usr/local/bin/llvm-as /usr/bin/llvm-confing --version bash: /usr/bin/llvm-confing: No such file or directory /usr/local/bin/llvm-config --version 2.8 Quoting Óscar Fuentes <ofv at wanadoo.es>: > Reza Sheykhi <hajishey at msu.edu> writes: > >> Thank you

OK, it's not that bad - it's even better than before :) The main issue is RWMutex.inc and the use of PSRWLOCK. This requires _WIN32_WINNT to be >= 0x0600, which is not true for VS2005 SP1. Rather than #define _WIN32_WINNT 0x0600 (the file notes that this should build on all Win32 variants), extending the copy/paste of winbase.h to this works fine: #if defined(__MINGW32__) |...

Hi, what are the goals of VS2005 support for building LLVM? I'm syncing to the v3 branch and while the branch compiles perfectly with VS2008, there are a significant amount of compile errors and warnings with VS2005 SP1 (8.0.50727.867 with KB926601 SP1, to be precise). I also have the latest WSDK installed. A few months back there were only a few minor issues that I managed to clear up.

On Tue, Nov 8, 2011 at 8:02 AM, Don Williamson <don.williamson at yahoo.com> wrote: > > > OK, it's not that bad - it's even better than before :) > > The main issue is RWMutex.inc and the use of PSRWLOCK. This requires _WIN32_WINNT to be >= 0x0600, which is not true for VS2005 SP1. > > Rather than #define _WIN32_WINNT 0x0600 (the file notes that this should build on all Win32 variants), extending the copy/paste of winbase.h to this works fine: > > #if defi...

...0, at 14:09, Vincent Richomme wrote: > On Sun, 14 Feb 2010 14:26:38 +0100, Vincent Richomme > <forumer at smartmobili.com> wrote: >> Hi, >> >> When testing clang on mingw platform I got some errors when pthread was >> enabled. >> Problem was in line 87 in RWMutex.cpp: >> >> // Initialize the rwlock >> errorcode = pthread_rwlock_init(rwlock, &attr); >> assert(errorcode == 0); >> >> >> on mingw platform, pthread only support NULL attribues as shown below: >> >> int >> pthread_rwlock_ini...

...i686-pc-mingw32/sys-include -E -dM - | \ sed -n -e 's/^#define \([^_][a-zA-Z0-9_]*\).*/\1/p' \ -e 's/^#define \(_[^_A-Z][a-zA-Z0-9_]*\).*/\1/p' | \ sort -u > tmp-macro_list Assertion failed: errorcode == 0, file c:/Temp/llvm-2.6/lib/System/RWMutex.cpp, line 87 This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. xgcc.exe: Internal error: Aborted (program cc1) Please submit a full bug report. See <URL:http://llvm.org/bugs/> for inst...

...the PassRegistrar object is wrapped in a ManagedStatic object which gets deleted at shutdown. The second issue is that the critical section created in Signals.inc was still active when the DLL was unloaded. There are three places where critical sections are used in Windows, these are Mutex.inc/h, RWMutex.inc/h and Signals.inc/h. The first two define classes that use the critical sections and have destructors that delete them. The critical section in Signals has no mechanism for deleting. I again added a function to my local copy a function to delete the critical section. This cleanup function is ca...

...te: > >> On Sun, 14 Feb 2010 14:26:38 +0100, Vincent Richomme >> <forumer at smartmobili.com> wrote: >>> Hi, >>> >>> When testing clang on mingw platform I got some errors when pthread was >>> enabled. >>> Problem was in line 87 in RWMutex.cpp: >>> >>> // Initialize the rwlock >>> errorcode = pthread_rwlock_init(rwlock, &attr); >>> assert(errorcode == 0); >>> >>> >>> on mingw platform, pthread only support NULL attribues as shown below: >>> >>&g...

2017-05-26 17:47 GMT-07:00 Zachary Turner via llvm-dev < llvm-dev at lists.llvm.org>: > Changing a header file somewhere and having to spend 10 minutes waiting > for a build leads to a lot of wasted developer time. > > The real culprit here is tablegen. Can we split support and ADT into two > - the parts that tablegen depends on and the parts that it doesn't? >

...dows Vista and higher, since the functionality is available in the OS there. It falls back on the heavyweight critical sections implementation for Windows XP because the reader/writer locks are unavailable. ~Aaron -------------- next part -------------- A non-text attachment was scrubbed... Name: RWMutex.diff Type: application/octet-stream Size: 4339 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111004/7ae876a5/attachment.obj>

...t cs.uiuc.edu> Sent: Tuesday, November 8, 2011 1:30 PM Subject: Re: [LLVMdev] VS2005 compatibility On Tue, Nov 8, 2011 at 8:02 AM, Don Williamson <don.williamson at yahoo.com> wrote: > > > OK, it's not that bad - it's even better than before :) > > The main issue is RWMutex.inc and the use of PSRWLOCK. This requires _WIN32_WINNT to be >= 0x0600, which is not true for VS2005 SP1. > > Rather than #define _WIN32_WINNT 0x0600 (the file notes that this should build on all Win32 variants), extending the copy/paste of winbase.h to this works fine: > > #if defi...

....h > Options.h > Parallel.h > Path.h > PointerLikeTypeTraits.h > PrettyStackTrace.h > Printable.h > Process.h > Program.h > RandomNumberGenerator.h > raw_os_ostream.h > raw_ostream.h > raw_sha1_ostream.h > Recycler.h > RecyclingAllocator.h > Regex.h > RWMutex.h > SaveAndRestore.h > ScaledNumber.h > SHA1.h > Signals.h > StringPool.h > StringSaver.h > SwapByteOrder.h > SystemUtils.h > thread.h > Threading.h > ThreadLocal.h > ThreadPool.h > Timer.h > TrailingObjects.h > Unicode.h > UnicodeCharRanges.h > Un...

On Jan 13, 2012, at 11:17 PM, David Blaikie wrote: >> On some (linux?) implementations, various pthread APIs are defined as "weak extern" symbols in libc and strong definitions in libpthreads. The idea of this check is thus to detect if pthreads is linked into the app and enable threads if so. > > Sorry, right - I should've been more clear. I understand that that's

...& all the conditions (unconditionally using >> pthreads), or reinstate the smarts it used to have (testing the weak >> symbol)? > > Aha, I'm completely fine with constant folding this all away.  Simple is good. Sounds good. Committed as r148206 (including a similar fix in RWMutex.cpp - which propagated the same quirk when it was copy/pasted/created from Mutex.cpp) I've attached a patch containing some other fixes to remove unreachable code in LLVM - this isn't comprehensive, but a start based on -Wunreachable-code. Is this sort of thing OK to commit as I work throu...

...core` `llvm-config --ldflags` This compiled just fine, with no warnings; but when I tried to run the program, as soon as I entered an expression for Kaleidoscope to compile, I got an assert failure like this: define double @0()Assertion failed: errorcode == 0, file c:/llvm-2.7/lib/System/RWMutex.cpp, line 87 When I built the examples using Eclipse CDT (via the CMake-generated project files), the Kaleidoscope examples all worked perfectly. So what's the scoop? Is there any way I can conveniently create a project with Eclipse CDT that uses LLVM? What do I actually need to include and l...