search for: armjitinfo

The Compilation error I am getting: "Error while compiling ARMJITInfo.cpp.. Selected processor does not support fstmfdd sp!,{d0,d1,d2,d3,d4,d5,d6,d7}.... On Thu, Sep 24, 2009 at 8:45 PM, kapil anand <kapilanand2 at gmail.com> wrote: > Hi all, > > I have an ARM virtual machine with ubuntu and want to port LLVM over that. > In release documents, A...

Hi all, I have an ARM virtual machine with ubuntu and want to port LLVM over that. In release documents, ARM is not in the list of supported platforms. I tried to compile LLVM on ARM platform and ran into an error. Has anyone tried to port LLVM onto ARM before? Is it going to require lots of changes? Thanks --Kapil -------------- next part -------------- An HTML attachment was scrubbed...

...Stub() from MachineCodeEmitter, ELFWriter, and MachOWriter classes. * modified include/llvm/Target/TargetJITInfo.h to use JITEmitter rather than MachineCodeEmitter. * modified :- - lib/Target/PowerPC/PPCJITInfo.h - lib/Target/PowerPC/PPCJITInfo.cpp - lib/Target/ARM/ARMJITInfo.cpp - lib/Target/ARM/ARMJITInfo.h - lib/Target/Alpha/AlphaJITInfo.cpp - lib/Target/Alpha/AlphaJITInfo.h - lib/Target/X86/X86JITInfo.h - lib/Target/X86/X86JITInfo.cpp to use JITEmitter rather than MachineCodeEmitter. * renamed multiple MCE's to...

...sing GCC 4.3.3 on a Ubuntu Jaunty system and GCC 4.4 on a Ubuntu Karmic system. Do you use cross compilation to build llvm for your ARM system or do you compile natively on your ARM board? Cheers Xerxes kapil anand skrev: > The Compilation error I am getting: > "Error while compiling ARMJITInfo.cpp.. > Selected processor does not support fstmfdd > sp!,{d0,d1,d2,d3,d4,d5,d6,d7}.... > > > > On Thu, Sep 24, 2009 at 8:45 PM, kapil anand <kapilanand2 at gmail.com > <mailto:kapilanand2 at gmail.com>> wrote: > > Hi all, > > I have an ARM virtu...

...ter, and MachOWriter > classes. > * modified include/llvm/Target/TargetJITInfo.h to use JITEmitter > rather than MachineCodeEmitter. > * modified :- > - lib/Target/PowerPC/PPCJITInfo.h > - lib/Target/PowerPC/PPCJITInfo.cpp > - lib/Target/ARM/ARMJITInfo.cpp > - lib/Target/ARM/ARMJITInfo.h > - lib/Target/Alpha/AlphaJITInfo.cpp > - lib/Target/Alpha/AlphaJITInfo.h > - lib/Target/X86/X86JITInfo.h > - lib/Target/X86/X86JITInfo.cpp > to use JITEmitter rather than MachineCodeEmitter. >...

...ced references to MachineCodeEmitter with JITCodeEmitter. lib/Target/ARM/ARM.h lib/Target/ARM/ARMTargetMachine.h lib/Target/ARM/ARMTargetMachine.cpp lib/Target/ARM/ARMCodeEmitter.cpp * Parameterized to support JITCodeEmitter and in future ObjectCodeEmitter lib/Target/ARM/ARMJITInfo.h lib/Target/ARM/ARMJITInfo.cpp * Replaced references to MachineCodeEmitter with JITCodeEmitter. lib/Target/Alpha/Alpha.h lib/Target/Alpha/AlphaTargetMachine.h lib/Target/Alpha/AlphaTargetMachine.cpp lib/Target/Alpha/AlphaCodeEmitter.cpp * Parameterized to support J...

...4 on a Ubuntu Karmic system. > > Do you use cross compilation to build llvm for your ARM system or do you > compile natively on your ARM board? > > Cheers > Xerxes > > > kapil anand skrev: > > The Compilation error I am getting: > > "Error while compiling ARMJITInfo.cpp.. > > Selected processor does not support fstmfdd > > sp!,{d0,d1,d2,d3,d4,d5,d6,d7}.... > > > > > > > > On Thu, Sep 24, 2009 at 8:45 PM, kapil anand <kapilanand2 at gmail.com > > <mailto:kapilanand2 at gmail.com>> wrote: > > > >...

...y > similar to the default behavior, but you have implemented it without using > the existing code. Did you consider implementing it using the LLVM > defaults? > I spend over a day trying to follow your suggestion. In the end I was not successful. Here is what Iearned: After setting ARMJITInfo::hasCustomJumpTables -> true setOperationAction for ISD::BR_JT -> Expand I needed to add a "brind" definition to ARMInstrInfo.td I picked "bx" but to do a proper job one would have to take older architectures into account.. The next thing was to to set setOperationAction...

...that is at least very similar to the default behavior, but you have implemented it without using the existing code. Did you consider implementing it using the LLVM defaults? Using TargetAsmInfo::JumpTableDataSection is one piece of that, but there is more. As a start, you could change ARMJITInfo::hasCustomJumpTables and the "Custom" argument to setOperationAction for ISD::BR_JT in the ARMTargetLowering constructor to be conditional on your new flag. I'm sure there is more required than that, but maybe that will get you started. Otherwise, there are some problems with...

On Jul 2, 2009, at 10:48 AM, robert muth wrote: > I spend over a day trying to follow your suggestion. In the end I > was not successful. Here is what Iearned: > > After setting > > ARMJITInfo::hasCustomJumpTables -> true > setOperationAction for ISD::BR_JT -> Expand > > I needed to add a "brind" definition to ARMInstrInfo.td > I picked "bx" but to do a proper job one would have to take older > architectures > into account.. > The next thi...

...t;evan.cheng at apple.com> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Tuesday, November 25, 2008 1:51:35 AM GMT -05:00 US/Canada Eastern Subject: Re: [LLVMdev] MachineCodeEmitter Patch Thanks. But we need to match the type changes in all the target. e.g. ARMJITInfo.cpp, X86CodeEmitter.cpp. Also in MachineRelocation, e.g. getBB. Could you prepare a patch with all those fixed as well? Evan On Nov 22, 2008, at 1:19 PM, Thomas Jablin wrote: > Here is the corrected version. > > Thomas Jablin wrote: >> Actually, there is a problem with the patch...

...t;evan.cheng at apple.com> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Tuesday, November 25, 2008 1:51:35 AM GMT -05:00 US/Canada Eastern Subject: Re: [LLVMdev] MachineCodeEmitter Patch Thanks. But we need to match the type changes in all the target. e.g. ARMJITInfo.cpp, X86CodeEmitter.cpp. Also in MachineRelocation, e.g. getBB. Could you prepare a patch with all those fixed as well? Evan On Nov 22, 2008, at 1:19 PM, Thomas Jablin wrote: > Here is the corrected version. > > Thomas Jablin wrote: >> Actually, there is a problem with the patch...

Evan: Sorry for the late follow up, I was out of town last week. Enclosed please find the updated patch including all your suggestions and a dejagnus test. Robert On Thu, Jun 11, 2009 at 2:27 PM, Evan Cheng <evan.cheng at apple.com> wrote: > > On Jun 8, 2009, at 2:42 PM, robert muth wrote: > > > On Sun, Jun 7, 2009 at 11:53 PM, Evan Cheng <evan.cheng at apple.com>

Here is the corrected version. Thomas Jablin wrote: > Actually, there is a problem with the patch. Please delay review. > > Thomas Jablin wrote: > >> Hi, >> The following code: >> >> #include<stdio.h> >> >> char bigArray[0x1000000]; >> >> int main(int argc, char **argv) { >> printf("mem: 0x%x\n", (unsigned)

On Tue, Jul 14, 2009 at 6:48 PM, Bob Wilson <bob.wilson at apple.com> wrote: > > On Jul 2, 2009, at 10:48 AM, robert muth wrote: > > I spend over a day trying to follow your suggestion. In the end I was not > successful. Here is what Iearned: > > After setting > > ARMJITInfo::hasCustomJumpTables -> true > setOperationAction for ISD::BR_JT -> Expand > > I needed to add a "brind" definition to ARMInstrInfo.td > I picked "bx" but to do a proper job one would have to take older > architectures > into account.. > The next thing...