Displaying 6 results from an estimated 6 matches for "x86machobjectwrit".
Did you mean:
x86machobjectwriter
2012 Jun 29
0
[LLVMdev] Comment "FIXME" in X86MachObjectWriter::RecordX86Relocation
...elocation model is very tied to Darwin.
I believe some folks doing JIT on Windows have had some success w/ ELF. Hopefully someone more familiar with the specifics of that will chime in.
-Jim
On Jun 29, 2012, at 8:58 AM, Verena Beckham <verena at codeplay.com> wrote:
> Hi,
>
> In X86MachObjectWriter::RecordX86Relocation I found the comment
>
>
> if (Target.isAbsolute()) { // constant
> // SymbolNum of 0 indicates the absolute section.
> //
> // FIXME: Currently, these are never generated (see code below). I
> cannot
> // find a case where they are...
2012 Jun 29
2
[LLVMdev] Comment "FIXME" in X86MachObjectWriter::RecordX86Relocation
Hi,
In X86MachObjectWriter::RecordX86Relocation I found the comment
if (Target.isAbsolute()) { // constant
// SymbolNum of 0 indicates the absolute section.
//
// FIXME: Currently, these are never generated (see code below). I
cannot
// find a case where they are actually emitted.
Type = mach...
2012 Jul 02
0
[LLVMdev] Comment "FIXME" in X86MachObjectWriter::RecordX86Relocation
...>
> -----Original Message-----
> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Jim Grosbach
> Sent: Friday, June 29, 2012 9:54 AM
> To: Verena Beckham
> Cc: llvmdev at cs.uiuc.edu
> Subject: Re: [LLVMdev] Comment "FIXME" in X86MachObjectWriter::RecordX86Relocation
>
> Hi Verena,
>
> Windows + MachO is likely to run into lots of problems once you start passing in non-trivial code. The relocation model is very tied to Darwin.
>
> I believe some folks doing JIT on Windows have had some success w/ ELF. Hopefully someone m...
2012 Jun 29
2
[LLVMdev] Comment "FIXME" in X86MachObjectWriter::RecordX86Relocation
...rally acceptable solution.
-Andy
-----Original Message-----
From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Jim Grosbach
Sent: Friday, June 29, 2012 9:54 AM
To: Verena Beckham
Cc: llvmdev at cs.uiuc.edu
Subject: Re: [LLVMdev] Comment "FIXME" in X86MachObjectWriter::RecordX86Relocation
Hi Verena,
Windows + MachO is likely to run into lots of problems once you start passing in non-trivial code. The relocation model is very tied to Darwin.
I believe some folks doing JIT on Windows have had some success w/ ELF. Hopefully someone more familiar with the speci...
2013 Dec 12
3
[LLVMdev] [RFC PATCH 1/2] x86: Fix ModR/M byte output in 16-bit addressing mode
This attempts to address http://llvm.org/bugs/show_bug.cgi?id=18220
It also fixes a test which was requiring the *wrong* output.
I'm relatively happy with this part, and it even solves most of the hard
part of feature request for .code16 in bug 8684 — which was actually why
I started prodding at this. But I could do with some help with the
16-bit signed relocation handling, which I've
2015 Jul 29
1
[LLVMdev] Error when i am using command make -j4 command in cygwin to compile safecode
...g directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/lib/ExecutionEngine/MCJIT'
llvm[4]: Compiling X86MachORelocationInfo.cpp for Release+Asserts build
llvm[3]: Compiling MCJIT.cpp for Release+Asserts build
llvm[2]: Compiling BasicTargetTransformInfo.cpp for Release+Asserts build
llvm[4]: Compiling X86MachObjectWriter.cpp for Release+Asserts build
llvm[3]: Compiling SampleProfile.cpp for Release+Asserts build
llvm[3]: Building Release+Asserts Archive Library libLLVMMCJIT.a
make[3]: Leaving directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/lib/ExecutionEngine/MCJIT'
make[3]: Entering directory '/home/NIKHI...