Displaying 8 results from an estimated 8 matches for "x86codegener".
Did you mean:
x86codegen
2010 Jul 26
2
[LLVMdev] LLVM Dependency Graph
Based on cmake/modules/LLVMLibDeps.cmake, I produced a graphviz dot file and then manually removed components and edges until the graph was small enough to be presentable. I don't know if I can actually use LLVM due to its humongousness, but I hope the graph will be helpful to others attempting to comprehend LLVM. PNG attached; dot file follows.
digraph G {
ipo
2009 Jun 10
3
[LLVMdev] Why does the x86-64 JIT emit stubs for external calls?
In X86CodeGen.cpp, the following code appears in the handler used for
CALL64pcrel32 instructions:
// Assume undefined functions may be outside the Small codespace.
bool NeedStub =
(Is64BitMode &&
(TM.getCodeModel() == CodeModel::Large ||
TM.getSubtarget<X86Subtarget>().isTargetDarwin())) ||
Opcode == X86::TAILJMPd;
2009 Jun 11
0
[LLVMdev] Why does the x86-64 JIT emit stubs for external calls?
On Jun 10, 2009, at 12:17 PM, Jeffrey Yasskin wrote:
> In X86CodeGen.cpp, the following code appears in the handler used for
> CALL64pcrel32 instructions:
>
> // Assume undefined functions may be outside the Small
> codespace.
> bool NeedStub =
> (Is64BitMode &&
> (TM.getCodeModel() == CodeModel::Large ||
>
2009 Jun 11
1
[LLVMdev] [unladen-swallow] Re: Why does the x86-64 JIT emit stubs for external calls?
On Thu, Jun 11, 2009 at 12:54 PM, Evan Cheng<evan.cheng at apple.com> wrote:
>
>
>
> On Jun 10, 2009, at 12:17 PM, Jeffrey Yasskin wrote:
>
>> In X86CodeGen.cpp, the following code appears in the handler used for
>> CALL64pcrel32 instructions:
>>
>> // Assume undefined functions may be outside the Small codespace.
>> bool NeedStub =
2009 Mar 31
3
[LLVMdev] assert problem embedding llvm libs in linux - stuck
Hi,
I have a shared library that makes use of LLVM/clang to add JIT
capabilities to a front-end interface in Lua. This shared library is
used within an executable application. This all works and builds fine
on OSX, but I'm having trouble replicating it for Linux. The build
process goes fine, with no changes to the library code, however I'm
receiving a SIGABRT caused by an
2013 Apr 09
0
[LLVMdev] Please document the layers
On Apr 8, 2013, at 2:55 PM, "Robinson, Paul" <Paul_Robinson at playstation.sony.com> wrote:
I keep seeing "this is a layering violation" comments on the lists.
> While there are a few llvm.org pages that mention layers in passing,
> there is nothing (that I've found) actually specifying the layers.
> Trying to infer the layering from the code is tedious and
2013 Apr 08
2
[LLVMdev] Please document the layers
I keep seeing "this is a layering violation" comments on the lists.
While there are a few llvm.org pages that mention layers in passing,
there is nothing (that I've found) actually specifying the layers.
Trying to infer the layering from the code is tedious and error-prone
(or we wouldn't see so many violations in code reviews, eh?).
Now, I understand that Google has some sort
2010 Apr 10
3
[LLVMdev] darwin dragon-egg build issues
Is anyone building dragon-egg on darwin? I am trying
to build against the fink gcc45 package that I have prepared
for darwin and a updated fink llvm 2.7 package that is built
as...
../llvm-2.7/configure --prefix=/sw --prefix=/sw/lib/llvm --mandir=/sw/share/man --infodir=/sw/share/info --with-gmp=/sw --with-libiconv-prefix=/usr --with-system-zlib --with-as=/Developer/usr/bin/as