similar to: [LLVMdev] building LLVM with just the C backend

I've built a debug build of llvm 2.6, and llvm-gcc 2.6 for arm-elf with --enable-checking=yes. On the attached test case (which is g++.dg/expr/bitfield4.C from the GCC 4.2 testsuite) I get: $ cc1plus bitfield4.ii -emit-llvm-bc -o bitfield4.o -quiet cc1plus: /home/foad/svn/antix/toolchain/branches/w/foad/2757llvm26/toolchain/llvm/llvm-gcc/gcc/llvm-convert.cpp:999: llvm::Value*

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

Hello, I am looking to employ a graduate developer who can demonstrate experience of working with the LLVM technology and community and who is willing to take on an exciting and challenging role at Antix Labs limited. There is a job spec posted on our web site: http://antixlabs.com/aboutUs/vacancies.html If you are interested, or would like to know more, please contact us through

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

I'm seeing a lot of build failures recently: (1) on x86-64 linux, gcc 4.1.2: ... llvm[3]: Compiling Hello.cpp for Debug build (PIC) llvm[3]: Linking Debug Loadable Module LLVMHello.so /usr/bin/ld: .../llvm/build/llvm/lib/Transforms/Hello/Debug/.libs/Hello.o: relocation R_X86_64_PC32 against `std::basic_string<char, std::char_traits<char>, std::allocator<char>

Hello EveryOne, I am building customized tools for ARM using a crosscomplier. I am currently building a tool similar to lli but it only jits code. I enabled jit when I was configuring LLVM. On linking my code with help from llvm-config to the libraries I get this error: Can't exec "which": No such file or directory at llvm2/bin/llvm-config line 69. Use of uninitialized value in

With the TableGen problem circumvented the build proceeds quite well up until: llvm[2]: Linking Debug executable llc /home/neale/LLVM/llvm/tools/llc/Debug/llc.o: In function `ForceCodegenLinking': /home/neale/LLVM/llvm/include/llvm/CodeGen/LinkAllCodegenComponents.h:45: undefined reference to `llvm::createBURRListDAGScheduler(llvm::SelectionDAGISel*, bool)'

Hi all, llvm newbie here. I'm trying to learn porting with llvm for study purpose. This is my first query on llvm mailing list.I have some idea about GCC. I choose 'rx' as a target to port as it is also available in GCC. I have done some initial changes with llvm source code to register target with llvm. I need to verify these changes. Can anyone please take a chance to verify it.

I ran with VERBOSE=1 and see: g++ -I/home/neale/LLVM/llvm/include -I/home/neale/LLVM/llvm/tools/llc -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -g -fno-exceptions -fPIC -Woverloaded-virtual -pedantic -Wall -W -Wwrite-strings -Wno-long-long -Wunused -Wno-unused-parameter -g -Wl,-R -Wl,/home/neale/LLVM/llvm/Debug/bin -Wl,-export-dynamic

> To test clang: > 1) Compile llvm and clang from source. LLVM fails to build for me on Cygwin. I get: make[1]: Entering directory `/home/foad/llvm/objdir-2.6/runtime' make[2]: Entering directory `/home/foad/llvm/objdir-2.6/runtime/libprofile' llvm[2]: Compiling BasicBlockTracing.c for Release build (PIC) llvm[2]: Compiling BlockProfiling.c for Release build (PIC) llvm[2]:

2009/10/20 Tanya Lattner <lattner at apple.com>: > > On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: > >>> To test clang: >>> 1) Compile llvm and clang from source. >> >> LLVM fails to build for me on Cygwin. I get: >> > > Does TOT build? If not, please file a bug. No. Theres the runtime install bug (below), and llvm-gcc has a bug that I

Hi, If I configure llvm-gcc 2.6 with --target=mips or --target=mips-elf, I get: c++ -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wwrite-strings -pedantic -Wno-long-long -Wno-variadic-macros -Wmissing-format-attribute -fno-common -DHAVE_CONFIG_H -Wno-unused -DTARGET_NAME=\"mips-elf\" -frandom-seed=0 -I. -I. -I/home/foad/toolchain/llvm/llvm-gcc/gcc

On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >> To test clang: >> 1) Compile llvm and clang from source. > > LLVM fails to build for me on Cygwin. I get: > Does TOT build? If not, please file a bug. Unfortunately Cygwin is not in our release criteria. I'd like to have a buildbot running (if there is not one already) and then get someone to qualify it for the

2009/10/20 Tanya Lattner <lattner at apple.com>: > > On Oct 20, 2009, at 12:05 PM, Aaron Gray wrote: > >> 2009/10/20 Tanya Lattner <lattner at apple.com>: >>> >>> On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >>> >>>>> To test clang: >>>>> 1) Compile llvm and clang from source. >>>> >>>> LLVM

On Oct 20, 2009, at 12:05 PM, Aaron Gray wrote: > 2009/10/20 Tanya Lattner <lattner at apple.com>: >> >> On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >> >>>> To test clang: >>>> 1) Compile llvm and clang from source. >>> >>> LLVM fails to build for me on Cygwin. I get: >>> >> >> Does TOT build? If not,