Displaying 7 results from an estimated 7 matches for "exc_bad_instruct".
2014 Sep 17
2
[LLVMdev] [cfe-dev] exc_bad_instruction on arm
Hi Anton,
I've added the llvmdev list, since the issues you're seeing are coming
from the backend, which is more their side.
On 17 September 2014 08:43, Anton Smirnov <dev at antonsmirnov.name> wrote:
> i've changed lli arguments to the next (instead of default):
>
> return llvm_interpret(
> InputFile,
> std::vector<std::string>(),
> false,
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 17
2
[LLVMdev] [cfe-dev] exc_bad_instruction on arm
I've also tried the next combination:
true, // ForceInterpreter
false, // UseMCJIT
and ios app just crashed with no output
2014-09-18 0:47 GMT+06:00 Anton Smirnov <dev at antonsmirnov.name>:
> Hey.
>
> I've checked out LLVM/Clang 3.5 and modified my static libs source code to
> use the latest llvm/clang sources.
> Also i'm trying triple
2014 Sep 18
2
[LLVMdev] [cfe-dev] exc_bad_instruction on arm
Hi, Lang.
Thanks for clarification. I will check out current branch tomorrow and
report you back.
Most likely i will create bug issue with cleaned sources for static lib and
test ios app.
Actually i'm not professional c++ dev so my question is - is there any
chance to do the next:
1. compile .cpp code to .ll code (seems i already did it)
2. interpret .ll file by any supported at the moment
2014 Sep 18
2
[LLVMdev] [cfe-dev] exc_bad_instruction on arm
Hi, Lang.
2014-09-19 0:39 GMT+06:00 Lang Hames <lhames at gmail.com>:
> Hi Anton,
>
> I don't follow what you're asking?
>
> For (1): You can compile c++ files to .ll files with clang - it seems like
> you've already worked that out.
>
> For (2): What do you mean "supported at the moment"? In the 3.5 release
> MCJIT is known to be broken for
2007 Apr 07
0
[ wxruby-Bugs-9930 ] StaticBoxSizer causes segfault on exit
...it seems to cause a segfault on exit. Adding just this line to MinimalFrame#initialize in the minimal sample shows the error:
sizer = Wx::StaticBoxSizer.new( Wx::HORIZONTAL, self, ''foo'' )
On OS X 10.3, working on the wxw28 branch, the backtrace is:
Program received signal EXC_BAD_INSTRUCTION, Illegal instruction/operand.
0x00836264 in ?? ()
(gdb) whe
#0 0x00836264 in ?? ()
#1 0x034a9850 in wxStaticBoxSizer::~wxStaticBoxSizer() ()
#2 0x0001d6f0 in rb_gc_call_finalizer_at_exit () at gc.c:1858
#3 0x000041d4 in ruby_finalize_1 () at eval.c:1418
#4 0x00004340 in ruby_cleanup (ex=0)...
2018 Dec 01
2
Restrict global constructors to base ISA
...t believe it has global data provided by
us: https://github.com/weidai11/cryptopp/blob/master/chacha_avx.cpp
==========
(lldb) r v
...
* thread #1: tid = 0x19f83aa, 0x000000010016ec49
cryptest.exe`_GLOBAL__sub_I_chacha_avx.cpp at string:1322, queue =
'com.apple.main-thread', stop reason = EXC_BAD_INSTRUCTION
(code=EXC_I386_INVOP, subcode=0x0)
frame #0: 0x000000010016ec49
cryptest.exe`_GLOBAL__sub_I_chacha_avx.cpp at string:1322
1319 {
1320 size_type (&__a)[__n_words] = __r_.first().__r.__words;
1321 for (unsigned __i = 0; __i < __n_words; ++__i)
-&...