similar to: [LLVMdev] Newbie question for registering new target with LLVM

Hi, > 1.1) Please verify all above change(s) are OK? or I have modify some code? Parts will almost certainly have to change in future, but if it builds that's an excellent first step. > 1.2) In LLVM, can we proceed our development like as GCC i.e. incremental > approach? In case of yes, please provide me any reference. Incremental is definitely possible. I started out with

Hi Tim, Have you considered taking your knowledge about writing backends and improve the current documentation? I have made a document which should allow you to get up and running writing documentation extremely quickly and easily; you can find it at <http://llvm.org/docs/SphinxQuickstartTemplate.html>. Any help is greatly appreciated. Even just a slightly more expository coverage of the

On Thu, 2004-12-23 at 12:35, Markus F.X.J. Oberhumer wrote: > Yes, but "TARGET_HAS_JIT" seems to be unused, so what is this for ? projects/llvm-test/Makefile.programs:175:ifdef TARGET_HAS_JIT projects/llvm-test/Makefile.programs:182:endif#TARGET_HAS_JIT projects/llvm-test/LLVMSource/Makefile:22:ifdef TARGET_HAS_JIT projects/llvm-test/SingleSource/CustomChecked/Makefile:27:ifdef

On 2013-03-13 3:15 AM, "Jyotsna Verma" <jverma at codeaurora.org> wrote: > >I noticed "TARGET_HAS_JIT" flag in Makefile.config. Can I use this flag to >exclude MCJIT and JIT tests when not set? This will be a simpler change >than >modifying the macro. > >Thanks, >Jyotsna TARGET_HAS_JIT seems to be an autoconf thing (also, not really sure how it

I can configure it now. Thank You! --- On Wed, 6/17/09, Bill Wendling <isanbard at gmail.com> wrote: From: Bill Wendling <isanbard at gmail.com> Subject: Re: [LLVMdev] Configure problem of llvm2.5 in Mac OS X 10.4.11 To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Date: Wednesday, June 17, 2009, 6:26 PM Hi Murat, This looks suspicious:  

I tried building LLVM 2.1 with no real target CPU backends enabled, just the C backend, by hacking the configure script slightly: --- /home/foad/llvm/llvm-2.1/configure 2007-09-17 22:37:52.000000000 +0100 +++ configure 2007-12-13 10:29:41.000000000 +0000 @@ -4762,7 +4762,7 @@ done ;; esac -TARGETS_TO_BUILD="CBackend MSIL $TARGETS_TO_BUILD"

Hi, I am trying to install llvm 2.5 in my PowerPC machine. I have already installed XCode Tools 2.4.1. I can compile programs using gcc run them. I try to configure llvm 2.5, the configuration aborts with following message: checking build system type... powerpc-apple-darwin8.11.0 checking host system type... powerpc-apple-darwin8.11.0 checking target system type... powerpc-apple-darwin8.11.0

On Wed, 2004-12-22 at 22:09, Markus F.X.J. Oberhumer wrote: > Below you will find a small patch for llvm/autoconf/configure.ac that fixes > wrong AC_SUBST usage and adds AMD64 detection. Please review. > > ~Markus > --- autoconf/configure.ac 22 Dec 2004 05:56:56 -0000 1.147 > +++ autoconf/configure.ac 23 Dec 2004 06:06:04 -0000 > @@ -139,7 +139,8 @@ >

>Since MCJIT works on x86, please don't remove it from the supported >platforms list. One downside of using the macro trick is that the test names >are still printed even when they are disabled. It sounds like you need to >modify the macro to also check for the target triple as well... This was just a temporary change to see how it works. >There isn't anything in MCJIT as

On Wed, 2004-12-22 at 22:38, Markus F.X.J. Oberhumer wrote: > Hello Reid, > > > > @@ -167,7 +168,7 @@ > > > if test ${enableval} = "no" ; then > > > AC_SUBST(ENABLE_OPTIMIZED,[[]]) > > > else > > > - AC_SUBST(ENABLE_OPTIMIZED,[[ENABLE_OPTIMIZED=1]]) > > > + AC_SUBST(ENABLE_OPTIMIZED,[[1]]) > > > > This is not

Hi, LLVMers, I notice that there are two versions of printInstruction() generated by tablegen: (1) XXXInstPrinter::printInstruction(const MCInst *MI, raw_ostream &os), like for X86. (2) XXXAsmPrinter::printInstruction(const MachineInstr *MI, raw_ostream &os), like for Sparc. I guess Sparc backend directly transform MachineInstr objects into ostream, while X86 backend convert

You need to add your target to autoconf/configure.ac. Here are the directions from http://llvm.org/docs/WritingAnLLVMBackend.html To get LLVM to actually build and link your target, you need to add it to the TARGETS_TO_BUILD variable. To do this, you modify the configure script to know about your target when parsing the --enable-targets option. Search the configure script for TARGETS_TO_BUILD,

Hello everyone! I've started to implement a ColdFire backend, but there are some troubles during configuring: $ ../llvm/configure --enable-targets=x86,x86_64,coldfire ... ... ... checking whether byte ordering is bigendian... no configure: error: Unrecognized target coldfire configure: error: ../../../llvm/projects/sample/configure failed for projects/sample I've added ColdFire to : 1)

Thanks. More below. > On Jul 3, 2019, at 12:06 PM, Justin Clift <justin at postgresql.org> wrote: > > Not sure personally, as I've not touched the libcxx source before. Looking > at line 876 for libcxx/include/chrono, gives this: > > https://github.com/llvm/llvm-project/blob/d2298e74235598f15594fe2c99bbac870a507c59/libcxx/include/chrono#L876

On Fri, Feb 01, 2013 at 04:43:59PM +0200, Vadim Khoptynets wrote: > Hello everyone! > > I've started to implement a ColdFire backend, but there are some troubles > during configuring: > > $ ../llvm/configure --enable-targets=x86,x86_64,coldfire > ... > ... > ... > checking whether byte ordering is bigendian... no > configure: error: Unrecognized target

I'm experimenting with a new backend, hoping to build a cross compiler, and reading "Writing an LLVM Compiler Backend". Early on, in "Preliminaries", it suggests editing my configure script to add my new target to the TARGETS_TO_BUILD variable, suggesting some creativity may be required. I'm perhaps not creative enough, 'cause I can't get it to work. I tried a

On Fri, Feb 1, 2013 at 4:01 PM, Tom Stellard <tom at stellard.net> wrote: > On Fri, Feb 01, 2013 at 04:43:59PM +0200, Vadim Khoptynets wrote: >> Hello everyone! >> >> I've started to implement a ColdFire backend, but there are some troubles >> during configuring: >> >> $ ../llvm/configure --enable-targets=x86,x86_64,coldfire >> ... >>

Hi I am interested in developing a new target for LLVM and wanted to check where my new code should reside. Should I just add a new sub-directory to lib/Targets and populate that with the necessary files? I am using ARM as a template, as I am most familiar with that architecture, so I assume copying files from that directory is a good starting point. I have tried a trivial build of a new

Hi all, I am in charge of the controlled introduction of clang into our builds at my workplace. Since all our tools must run from a ClearCase view for automatic dependency tracking, we have been biten by a Linux bug, and readlink("/proc/self/exe", ...) gives nonsensical results. So we need to introduce a configure option for disallowing this method of executable discovery (the other one

Thank you for replying to me. As you recommended, I modified configure.ac in autoconf folder. But I’m not sure about how to regenerate configure. Sorry… I tried to follow the way introduced in README.TXT in the autoconf folder. It asks me to run autoupdate on all the m4 and configure.ac. And then it asks me to regenerate configure script with AutoRegen.sh. However, when I did that, I got an error