similar to: [LLVMdev] Interactions between LLVM and the Microsoft C++ runtime

On Jan 20, 2009, at 1:41 PM, Tim Foley wrote: > Hello! I am trying to use LLVM 2.4 in a project built with MS Visual > Studio 2008. I've been building LLVM with the llvm/win32/llvm.sln > solution successfully for x86 and x64. I haven't yet tried to move > to the CMake build process, so I'd be interested to hear if the > following issues have been resolved on

Hi, > The problem that I've run into is that the LLVM codebase does > certain "idiomatic" things with STL containers that cause assertion > failures in the Microsoft runtime. Most notably: > - Taking the address of the "first element" of an emtpy vector > (either &v[0] or &*v.begin()) > - Using an iterator into a collection (even if just for

Hi, I upgraded the Visual Studio SLN file to work with 2005 and had to make some changes. The first two have to do with the fact that the debug implementation of 2005's STL does all sort of validation, that's why they didn’t show up on 2003. I'm not set up for patch submission yet, but if somebody has time to review these changes that'd be greatly appreciated. Meanwhile

Hi All, I am in the process of writing an R extension in c++ and am using several STL containers (e.g., vector<double>, map<int, double>, multimap<int, double>). I make sure to clear all these containers at the end of the .Call. Everything compiles and runs just fine, but I'm a bit worried since I haven't found any other packages that use STL. So, my question: is it

On May 23, 2008, at 4:10 AM, Nicolas Capens wrote: > Hi all, > > I updated from 2.2 to the latest SVN head and I now get a debug > assert in BranchFolder::RemoveBlocksWithHash: “vector iterators > incompatible”. I’m using Visual C++ 2005. I think this is the > culprit code: > > MergePotentials.erase(CurMPIter); > if (CurMPIter==B) > break; >

On 30 Aug 2013, at 19:42, Duncan Sands <baldrick at free.fr> wrote: > First off, is libc++ supposed to be incompatible with > libstdc++? libc++ does not, and never had, ABI compatibility with libstdc++ as a goal. Actually, libstdc++ periodically breaks ABI compatibility too, as we have recently found in the FreeBSD ports tree with certain projects requiring a newer libstdc++ than

On 3/10/07, Jeff Cohen <jeffc at jolt-lang.org> wrote: > It is, if only because it's the version I use, but 2005 is supposed to > work also. That being said, I wouldn't be surprised to learn that it > doesn't due to recent STL issues. Versions prior to 2003 won't work. I'm using the basic stuff (just libraries, 1.9) with 2005, although we had to fix a few

Hi all, I updated from 2.2 to the latest SVN head and I now get a debug assert in BranchFolder::RemoveBlocksWithHash: "vector iterators incompatible". I'm using Visual C++ 2005. I think this is the culprit code: MergePotentials.erase(CurMPIter); if (CurMPIter==B) break; The erase clears the _Mycont field (i.e. the iterator's container), while the ==

The recent issues concern the head revision, post 1.9. As no one has ever submitted patches to fix 2005 problems with the 1.9 release, it is safe to say they still exist. Andreas Fredriksson wrote: > On 3/10/07, Jeff Cohen <jeffc at jolt-lang.org> wrote: >> It is, if only because it's the version I use, but 2005 is supposed to >> work also. That being said, I

Reviving the discussion. The cool cmake-build of compiler-rt is not completely functional, but allows sanitizer runtimes to reuse LLVM code with almost no dirty hacks. Suppose I want to run call functions from LLVM libs (currently: LLVMDebugInfo, LLVMSupport) from sanitizer runtime. 1) I can simply include LLVM headers in sanitizer runtime, and it compiles and builds static asan runtime

UniqueVector is an stl map coupled with an stl vector[1], which seems very undesirable for you. As far as SmallVector + slow search, I believe that is precisely what the implementation of SmallSet does until it has to grow, after which it uses an stl set[2]. If you're always staying within your small number, SmallSetVector would be wasteful as the SmallSet would itself also have a SmallVector.

The R docs say that there are two methods that the C programmer can allocate memory, one where R automatically frees the memory on return from .C/.Call, and the other where the user takes responsibility for freeing the storage. Both methods involve using R-provided functions. What happens when the user uses the standard "new" allocator? What about when a C++ application uses STL and

On Thu, Jun 21, 2012 at 1:30 PM, Chandler Carruth <chandlerc at google.com>wrote: > Can we alter the build system so that when building a run-time library it >>>>> modifies all .cpp files like this: >>>>> namespace FOO { >>>>> <file body> >>>>> } >>>>> This will give us essentially the same thing,

On Thu, Jun 21, 2012 at 2:29 AM, Dmitry Vyukov <dvyukov at google.com> wrote: > On Thu, Jun 21, 2012 at 1:23 PM, Kostya Serebryany <kcc at google.com> wrote: > >> On Thu, Jun 21, 2012 at 12:52 PM, Chandler Carruth <chandlerc at google.com>wrote: >> >>> On Thu, Jun 21, 2012 at 1:42 AM, Kostya Serebryany <kcc at google.com>wrote: >>>

I am trying to understand the nuances of STL (seasonal trend decomposition with loess) based on William Cleveland's (and others?) original development. I do not understand the specification or use of "frequency components" or equivalent "low-pass filter" components in the stl() function. I have run the stl() function on a standard example data (co2) in both S-Plus and

Hi, I tried using lldb built from master, but still seeing some STL container member functions not recognizable in a debugging session. I am wondering if the work has been pushed to master; also if it's pushed but not enabled by default yet, is there a flag I can use to turn on the expression evaluator using Clang modules. Thanks a lot for the great work. Best Regards, Jiading

Hello, is there any one who uses C++ STL classes when programming shared libs for R and has had any problems with STL? In the very simple example below I am constantly getting segfaults when trying to populate the queue. The segfault occurs at what looks like a random index in the loop when pushing another element to the queue. Reproduced on 4 machines. Object x is an Image as in EBImage,

G'day, I am looking at monthly reports, and have three series of monthly data from 2007 to 2009. I would like to show the season decomposition of these two series side by side on the one device, however using plot doesn't seem to respect any use of layout(matrix(1:3, ncol=3)) or par(mfcol=c(1,3)). I'm guessing that this means that the plot(stl) perhaps uses them, but I can't find

R Help Community I'm trying to understand time series (TS) objects. Thought I understood but recently have run into a series of error messages that I'm not sure how to handle. I have 15 years of quarterly data and I typically create a TS object via something like... data.ts <- ts(mydata, start = 2002, frequency = 4) this create a matric as opposed to a vector object as I receive a

> Quite the contrary, knowing that Clang's C++ ABI is completely > incompatible with MS is a maintenance *simplification*. Yes, for example, as explained by Bjarne once, incompatible name mangling schemes for ABIs that are not guaranteed to be 100% binary compatible is a _feature_, not a bug, since it prevents anyone from even beginning to develop a workflow that relies upon linking