search for: codei

Hi, I am trying to use some LLVM API in my C++ code, and I end up getting linker errors. I am working on Apple MacOSX Lion. Using g++ for the compile. It is the CreateGlobalStringPtr which is throwing the error. This is LLVM 3.0. Here's the codeI am trying to use some LLVM API in my C++ code, and I end up getting linker errors. I am working on Apple MacOSX Lion. Using g++ for the compile. It is the CreateGlobalStringPtr which is throwing the error. This is LLVM 3.0. Here's the code: #define __STDC_LIMIT_MACROS #define __STDC_CONSTANT_...

...n at gmail.com>: > Hi, > > I am trying to use some LLVM API in my C++ code, and I end up getting linker > errors. I am working on Apple MacOSX Lion. Using g++ for the compile. It is > the CreateGlobalStringPtr which is throwing the error. This is LLVM 3.0. > > Here's the codeI am trying to use some LLVM API in my C++ code, and I end up > getting linker errors. I am working on Apple MacOSX Lion. Using g++ for the > compile. It is the CreateGlobalStringPtr which is throwing the error. This > is LLVM 3.0. > > Here's the code: > > #define __STDC_LIMI...

...; <- not pointer related. > int i; <- not pointer related > for (i =0; i< 2; i++) { <- not pointer related > printf("i is %d, aa is %d\n", i, aa); <- not pointer related > ptr[i]->index = 0; <- Here is where it gets wonky. > > <rest of codeis irrelevan> > > First, ptr[i] is an lvalue, of type struct heap *, and ptr[i]-> is an > lvalue of type struct heap (in C++03, this is 5.2.5 paragraph 3, check > footnote 59). > This is where we get the undefined behavior. 3.8/6: "[If you have a glvalue referring to stora...

+aliasing people I *think* this is valid, because the rules have always been described to me in terms of underlying storage type, and not access path. These are all ints, so all loads and stores can alias. On Sat, Aug 9, 2014 at 3:07 PM, Hal Finkel <hfinkel at anl.gov> wrote: > ----- Original Message ----- > > From: "Tim Northover" <t.p.northover at gmail.com>