Displaying 4 results from an estimated 4 matches for "incapsulation".
Did you mean:
encapsulation
2010 Jun 24
1
[LLVMdev] Why would -disable-fp-elim cause SEGV in JIT, when without it code works fine?
...as all the code you're running has frame pointers enabled.
>
> Reid
I think there is some bug in indirectbr instruction. It actually doesn't
work in JIT in the current trunk, but I submitted a patch some time ago
that implements it. Someone suggested that I should eliminate code
incapsulation breach, but this is besides the point here.
Once this patch applied, JIT supports address of label for instruction.
It works, except in one large case. In this case I spotted the entry in
one table of labels that contains pointer to invalid code.
-print-machine-code prints assembly that looks c...
2006 Jun 15
1
multple sqlite connections from single rails application
Please help to work out solution for the following task :
There are several users of my application and I want to allow each one
to have personal sqlite database. It''s going to be very useful for me
when all user''s data incapsulated in one single file. All users can be
logged-in at one time. Is it possible to implement it with ruby on
rails? If so what is the best way to
2010 Jun 23
0
[LLVMdev] Why would -disable-fp-elim cause SEGV in JIT, when without it code works fine?
You said this is on 32-bit x86? My understanding is that in that
case, gdb will use ebp/esp to unwind the stack and doesn't need dwarf.
It may have different behavior on FreeBSD if frame pointers are
normally omitted on that platform. gdb ignores them on Linux x86_64
because they are generally omitted.
This might actually be the best explanation for your symptoms, since
this is what a gdb
2010 Jun 23
2
[LLVMdev] Why would -disable-fp-elim cause SEGV in JIT, when without it code works fine?
I have this situation when the same code SEGVs in JIT with option
-disable-fp-elim and works fine without it.
How can this possibly happen?
Is it possible that there is a bug in JIT that stack isn't properly
lowered for local variables when prologs are present?
Or maybe JIT can accidentally use ebp for some values when it's supposed
to be only used by frame pointer value.
Stack (see