Displaying 6 results from an estimated 6 matches for "disablecorefiles".
2013 Mar 20
0
[LLVMdev] Problems with parallelizing lli
...and
- // usable by the JIT.
- InitializeNativeTarget();
- InitializeNativeTargetAsmPrinter();
-
- cl::ParseCommandLineOptions(argc, argv,
- "llvm interpreter & dynamic compiler\n");
-
- // If the user doesn't want core files, disable them.
- if (DisableCoreFiles)
- sys::Process::PreventCoreFiles();
-
+typedef struct {
+ int argc;
+ char **argv;
+ char *const *envp;
+} arg_t;
+
+void *run(void *arg) {
+ int argc = ((arg_t *) arg)->argc;
+ char **argv = ((arg_t *) arg)->argv;
+ char *const *envp = ((arg_t *) arg)->envp;
+ LLVMContext...
2014 Sep 17
2
[LLVMdev] [cfe-dev] exc_bad_instruction on arm
...vector<std::string>(), // ExtraModules
> std::vector<std::string>(), // ExtraObjects
> std::vector<std::string>(), // ExtraArchives
> false, // EnableCacheManager
> std::string(), // ObjectCacheDir
> std::string(), // FakeArgv0
> false, // DisableCoreFiles
> false, // NoLazyCompilation
> Reloc::PIC_, // RelocModel
> CodeModel::JITDefault, // CMModel
> true, // GenerateSoftFloatCalls
> FloatABI::Soft, // FloatABIForCalls
> false, // EmitJitDebugInfo
> false // EmitJitDebugInfoToDisk
> );
>
&g...
2014 Sep 17
2
[LLVMdev] [cfe-dev] exc_bad_instruction on arm
Both Clang/LLVM 3.4 -> Clang/LLVM 3.5
And i will also try using MCJIT.
2014-09-17 18:56 GMT+06:00 Anton Smirnov <dev at antonsmirnov.name>:
> Hi, Tim.
>
> I've used Clang 3.4 final release and now i'm going to test it with 3.5
> release (since i've read about arm64 improvements).
> I will report my results.
>
> BTW, is it possible to get smth like
2014 Sep 18
2
[LLVMdev] [cfe-dev] exc_bad_instruction on arm
...;>> std::vector<std::string>(), // ExtraObjects
>>> std::vector<std::string>(), // ExtraArchives
>>> false, // EnableCacheManager
>>> std::string(), // ObjectCacheDir
>>> std::string(), // FakeArgv0
>>> false, // DisableCoreFiles
>>> false, // NoLazyCompilation
>>> Reloc::PIC_, // RelocModel
>>> CodeModel::JITDefault, // CMModel
>>> true, // GenerateSoftFloatCalls
>>> FloatABI::Soft, // FloatABIForCalls
>>> false, // EmitJitDebugInfo
>>>...
2014 Sep 18
2
[LLVMdev] [cfe-dev] exc_bad_instruction on arm
...>(), // ExtraObjects
>>>>> std::vector<std::string>(), // ExtraArchives
>>>>> false, // EnableCacheManager
>>>>> std::string(), // ObjectCacheDir
>>>>> std::string(), // FakeArgv0
>>>>> false, // DisableCoreFiles
>>>>> false, // NoLazyCompilation
>>>>> Reloc::PIC_, // RelocModel
>>>>> CodeModel::JITDefault, // CMModel
>>>>> true, // GenerateSoftFloatCalls
>>>>> FloatABI::Soft, // FloatABIForCalls
>>>>&...
2007 Jul 05
2
[LLVMdev] PATCH (rest of code changes) "bytecode" --> "bitcode"
Here is the bulk of the sanitizing.
My residual doubts center around the question
whether we still do/want to support (un)compressed *byte*code
in 2.0/2.1.
I need a definitive word on this to proceed.
My understanding is that bytecode is already gone, but there are
still some functions/enums that really deal with *byte*code
(instead of *bit*code).
I did not touch those areas, so the attached