Displaying 3 results from an estimated 3 matches for "thirumurthi".
Did you mean:
athirumurthi
2013 Feb 15
0
[LLVMdev] assert when mixing static and non-static members with an external AST source
...se the case of a non-defining external (i.e. a static member variable) wasn't being handled with a variable lookup to dig up the location. I'll put a patch together for lldb-commits,
- Ashok
From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Thirumurthi, Ashok
Sent: Friday, February 08, 2013 5:59 PM
To: llvmdev at cs.uiuc.edu
Cc: Greg Clayton
Subject: [LLVMdev] assert when mixing static and non-static members with an external AST source
So, when performing expression evaluation, lldb trips over an assert in clang/lib/AST/RecordLayoutBuilder becau...
2013 Feb 08
2
[LLVMdev] assert when mixing static and non-static members with an external AST source
...or clang. The problem isn't related to the order of the definition of npos and m_a. It reproduces with "static int npos" as well. Any thoughts on how to dig deeper into this interaction would be appreciated. Some steps to reproduce and stack trace below. Thanks,
- Ashok Thirumurthi
clang++ -gdwarf-2 -O0 -c -o main.o main.cpp
clang++ -gdwarf-2 -O0 -arch x86_64 main.o -o "a.out"
$ lldb a.out
(lldb) b main.cpp:13
(lldb) r
10 int main (int argc, char const *argv[])
11 {
12 test my_test;
-> 13 my_test.length();...
2015 Jan 18
3
[LLVMdev] [MCJIT] Multiple GOT handling in RuntimeDyldELF
Hello everyone,
As part of my quest to add TLS relocation support to MCJIT, I've been
taking a closer look at the GOT implementation in RuntimeDyldELF and I
believe that is not valid as currently implemented. In particular, I am
wondering about the multiple GOT handling support introduced in r192020. If
I understand correctly this can make code reuse the GOT table entry in a
different object