search for: getelemntptr

I got a little problems with strings (const char pointers). Global variables holding the string literal are declared correctly, but i have a problem when I pass this string to a function: it asserts with this message. Assertion failed: ((i >= FTy->getNumParams() || FTy->getParamType(i) == Args[i]->getType()) && "Calling a function with a bad signature!"), function

Ok, thank you. I have also one question about getelementptr. In different versions of clang I see that sometimes array[i][i] is preceded by two getelementptr instructions and sometimes only by one - with an already complex index. 2017-09-01 12:50 GMT+02:00 David Chisnall <David.Chisnall at cl.cam.ac.uk>: > On 1 Sep 2017, at 11:44, Anastasiya Ruzhanskaya via llvm-dev < > llvm-dev

...trying to understand or recover array indexes from GEP's, that is non-trivial. On Sat, Sep 2, 2017 at 3:53 AM, Anastasiya Ruzhanskaya via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Is there a way to set always a defined behavior here - for example that we > will always one getelemntptr with complex index? > > 2017-09-02 12:53 GMT+02:00 Anastasiya Ruzhanskaya < > anastasiya.ruzhanskaya at frtk.ru>: > >> Ok, thank you. I have also one question about getelementptr. In different >> versions of clang I see that sometimes array[i][i] is preceded by two &gt...

...nd our run time routines use 8, in MS Windows. If a use #pragma pack(4) in my C programs, the routines run fine, but I must ensure that all external call should use the #pragma directive. If I change the llvm layout f64:64:64, the LLVM calls C functions and the struct is OK, in the C side, but the getelemntptr fails in LLVM side. Is there on way to ensure that the LLVM reads the correct memory position in this case? //#pragma pack(4) struct xfirstStru { int var1; double var2; int var3; char *var4; }; typedef struct xfirstStru osX ; typedef stru...

...use 8, in MS Windows. > If a use #pragma pack(4) in my C programs, the routines run fine, but > I must ensure that all external call should use the #pragma directive. > > If I change the llvm layout f64:64:64, the LLVM calls C functions and > the struct is OK, in the C side, but the getelemntptr fails in LLVM side. > Is there on way to ensure that the LLVM reads the correct memory position > in this case? > > //#pragma pack(4) > struct xfirstStru > { > int var1; > double var2; > int var3; > char *var...