Displaying 3 results from an estimated 3 matches for "abfef465".
2010 Jun 24
1
[LLVMdev] Why would -disable-fp-elim cause SEGV in JIT, when without it code works fine?
...he printout
is missing memory location information: where each line is laid in memory.
Yuri
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: llvm-patch-address-of-label.txt
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100623/abfef465/attachment.txt>
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