search for: __null

Displaying 8 results from an estimated 8 matches for "__null".

Did you mean: z_null
2011 Aug 18
1
[LLVMdev] [cfe-dev] Style question: NULL or 0?
On Wed, Aug 17, 2011 at 4:41 PM, Jordy Rose <jediknil at belkadan.com> wrote: > But I think I read somewhere that 0 is more C++esque. I believe Stroustrup espoused this at one point (perhaps even on his website) on the basis that using NULL gives you a false sense of security - which isn't entirely true now that compilers (GCC & clang presumably) will warn you about using NULL
2011 Aug 18
0
[LLVMdev] [cfe-dev] Style question: NULL or 0?
> using NULL gives you a false sense of security - which isn't entirely > true now that compilers (GCC & clang > presumably) will warn you about using NULL in non-pointer contexts. Hmm, nope, can't seem to find that warning in clang - gcc gives it though: foo.cpp:4:11: warning: converting to non-pointer type "int" from NULL
2011 Dec 17
2
[LLVMdev] Unable to build vmkit
...I attempted to make some minor fixes to get by this and I did, but when it was building mmtk-vmkit.jar (I think that's what it is doing) I got an assertion while running the vmjc command in the Makefile: vmjc: JavaRuntimeJIT.cpp:469: void *j3ResolveSpecialStub(): Assertion `FI->Metadata != __null && "Wrong stack trace"' failed. So, either my "fixes" were bad, or I have another problem that I don't know how to solve :) Should I be grabbing a specific version of LLVM/Clang from SVN (instead of the head)? Thank you, Jeff
2017 May 02
1
R 3.4 and mclapply assertion failure - is this a bug?
Dear all,? I am not sure if this is a bug, so I prefer to post it here before filing. After upgrading to 3.4 I encounter the following message with mclapply: Assertion failure at kmp_runtime.cpp(6480): __kmp_thread_pool == __null.OMP: Error #13: Assertion failure at kmp_runtime.cpp(6480).OMP: Hint: Please submit a bug report with this message, compile and run commands used, and machine configuration info including native compiler and operating system versions. Faster response will be obtained by including all program source...
2014 Apr 06
2
[LLVMdev] Using StartJnjvmWithJIT from jnjvm.cpp in VMKit
Hi Does anybody use *StartJnjvmWithJIT* from jvjvm.cpp in VMKit? Becuase , I am looking to use without JIT when we are running the Java byte code. My concern is StartJnjvmWithJIT getting three argument *int argc, char** argv, char* mainClass* - why we need to pass *argv and mainclass* arguments here? please help me on this. Regards Sri. -------------- next part -------------- An
2017 May 02
0
R 3.4 and mclapply assertion failure - is this a bug?
...ct.org> wrote: > > Dear all, > > > I am not sure if this is a bug, so I prefer to post it here before filing. > > > After upgrading to 3.4 I encounter the following message with mclapply: > > > Assertion failure at kmp_runtime.cpp(6480): __kmp_thread_pool == > __null.OMP : Error #13: Assertion failure at kmp_runtime.cpp(6480).OMP: > Hint: Please submit a bug report with this message, compile and run > commands used, and machine configuration info including native compiler and > operating system versions. Faster response will be obtained by including &g...
2014 Sep 09
2
[LLVMdev] VMKit is retired (but you can help if you want!)
...asonable hack or if it's causing problems. > > * I get the following error at runtime (because some fields are NULL) > and I can't make progress: > > HelloWorld.class.exe: JavaRuntimeJIT.cpp:381: void > *j3ResolveVirtualStub(j3::JavaObject *): Assertion `FI->Metadata != __null > && "Wrong stack trace"' failed. > > > > Am I on the right path, or should I be considering other methods? Or > wrong entirely? > > > > Ultimately, I propose changing `llcj` into something like a Python > script that executes the appropriate...
2014 Sep 09
2
[LLVMdev] VMKit is retired (but you can help if you want!)
...don't know if this is a reasonable hack or if it's causing problems. * I get the following error at runtime (because some fields are NULL) and I can't make progress: HelloWorld.class.exe: JavaRuntimeJIT.cpp:381: void *j3ResolveVirtualStub(j3::JavaObject *): Assertion `FI->Metadata != __null && "Wrong stack trace"' failed. Am I on the right path, or should I be considering other methods? Or wrong entirely? Ultimately, I propose changing `llcj` into something like a Python script that executes the appropriate utilities to start from Java source and resulting in...