similar to: [LLVMdev] [Questions] clang cross compilation and SimpleScalar simulation

Simplescalar is not compatible with llvm because the binutils simplescalar is based on is ancient. Jim On Sep 26, 2012, at 12:21 AM, 陳奕梅 <ymchen at sslab.cs.nctu.edu.tw> wrote: > Dear all > > I use arm-linux-gcc 2.95.2, because the code generated by version 3.X and 4.X can not run on SimpleScalar. > So I use the arm-linux-gcc 2.95.2 *only*, the version is recommended by

Dear all I use arm-linux-gcc 2.95.2, because the code generated by version 3.X and 4.X can not run on SimpleScalar. So I use the arm-linux-gcc 2.95.2 *only*, the version is recommended by SimpleScalar. The code generated by arm-linux-gcc 2.95.2 can run on SimpleScalar. Now I want to use llvm/clang to generate ARM assembly code and arm-linux-gcc 2.95.2 to be assembler. Unfortunately, I got some

These errors are from the assembler, not LLVM. Specifically, your binutils is too old. Given that it doesn't even recognize the ".syntax" directive, they're *very* much too old. You need to upgrade. -Jim On Sep 24, 2012, at 3:31 AM, 陳奕梅 <ymchen at sslab5.cs.nctu.edu.tw> wrote: > Hello, > > I want to compile MiBench by clang, and the target-ISA is armv4. The

Hi Jim, On Tue, Sep 25, 2012 at 10:52:58AM -0700, Jim Grosbach wrote: > These errors are from the assembler, not LLVM. Specifically, your binutils is > too old. Given that it doesn't even recognize the ".syntax" directive, they're > *very* much too old. You need to upgrade. > -Jim She said in her previous mail, P.S. Because I got error when I use

I tried llvm/clang-3.1 previously. It was not work, so I use version 2.9 now. Best regards, Yi Mei Chen 2012/9/25 陳韋任 (Wei-Ren Chen) <chenwj at iis.sinica.edu.tw> > > generated using llvm-2.9, clang-2.9, and arm-linux-gcc (gcc version > 2.95.2), > > simulator is sim-panalyzer 2.0.3 . > > LLVM/Clang 2.9 is too old. Please use LLVM/Clang 3.1 release or svn. > >

Hi, I want to explorer affection of compiler on low power. For the project background, I tend to process this work via LLVM, rather than GCC. And the Target is ARM. For this purpose, clang(3.2) + arm-gcc + simplescalar-arm(and panalyzer) seems to be a good choice. But I encounter several problems in the processing of setup the environment. ---------------------------------- 1. Firstly, arm

> generated using llvm-2.9, clang-2.9, and arm-linux-gcc (gcc version 2.95.2), > simulator is sim-panalyzer 2.0.3 . LLVM/Clang 2.9 is too old. Please use LLVM/Clang 3.1 release or svn. Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799 #1667 Homepage: http://people.cs.nctu.edu.tw/~chenwj

Hello, Running some examples to see how LLVM work, I found that some pseudo operations are unknown. Details are shown below. This is the command sequence that I am using: > llvm-gcc -O3 -emit-llvm hello.c -c -o hello.bc > llc -march=arm hello.bc -o hello-arm.s > arm-linux-gcc hello-arm.s -o hello-arm ************************ hello.s:6: Error: Unknown pseudo-op: `.eabi_attribute'

Hi, I do not get your result. Do I miss something? $COMP_ROOT/clang++ --target=arm-arm-eabihf -march=armv8.2a+fp16 arm.cpp -S -o - -O3 .text .syntax unified .eabi_attribute 67, "2.09" .eabi_attribute 6, 14 .eabi_attribute 7, 65 .eabi_attribute 8, 1 .eabi_attribute 9, 2 .fpu crypto-neon-fp-armv8 .eabi_attribute 12, 4

Hi Andrea, That is because the LR is the fixed register as per the http://infocenter.arm.com/help/topic/com.arm.doc.ihi0042e/IHI0042E_aapcs.pdf and out_char() function is not the leaf function ,Hence compiler tends to save and restore the LR and the save and restore of register r11 is to align stack for 8 bytes as per ARM EABI. Thanks ~Umesh On Tuesday, October 15, 2013, Umesh Kalappa

I'm trying to find a way to emulate a floating point instruction, say a floating point add. My understanding is that in order to do that I need to execute setOperationAction(ISD::FADD, (MVT::f32, Expand); setOperationAction(ISD::FADD, (MVT::f64, Expand); in MyTargetISelLowering.cpp, MyTargetLowering::MyTargetLowering(...). However for some reason I'm still seeing a floating point add in

Hi andrea, R11 treated as frame pointer at arm backend , which is fixed again . Thanks Umesh On Tuesday, October 15, 2013, Andrea Mucignat <andrea at nestlabs.com> wrote: > Umesh, > Makes some sort of sense to me, OTOH: > If instead of choosing r11 as a "dummy" to align the stack we had chosen some other register in the range r0-r7 then we could have emitted the PUSH

Umesh, Makes some sort of sense to me, OTOH: If instead of choosing r11 as a "dummy" to align the stack we had chosen some other register in the range r0-r7 then we could have emitted the PUSH encoding T1 (2 bytes opcode) as opposed to the encoding T2 (which is a 4 bytes opcode). A On Tue, Oct 15, 2013 at 2:59 AM, Umesh Kalappa <umesh.kalappa0 at gmail.com>wrote: > Hi

On 10 September 2010 04:47, Liu <proljc at gmail.com> wrote: > trying this: > clang -march=armv7-a -mcpu=cortex-a9 -ccc-host-triple > arm-none-linux -ccc-gcc-name arm-none-linux-gnueabi-gcc a.c Hi Liu, That doesn't work for me. $ clang -march=armv7-a -mcpu=cortex-a9 -ccc-host-triple arm-none-linux -ccc-gcc-name arm-none-linux-gnueabi-gcc alias.c clang: warning: unknown

Hello > hello.s:6: Error: Unknown pseudo-op:  `.eabi_attribute' How old is your arm toolchain? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

> Thanks for the review and checkin. Thanks for the patch! > Regarding elf-thumbfunc-reloc.ll, it seems to me that current ARMAsmParser > doesn't recognize "(PLT)", so something like "bl foo(PLT)" doesn't work > consequently. And I don't know how to write .s to test this without (PLT). NP. Can you just add that as a FIXME in elf-thumbfunc-reloc.ll?

On Tue, May 17, 2011 at 12:29 AM, Rafael Avila de Espindola <rafael.espindola at gmail.com> wrote: > On 11-05-16 09:21 AM, Koan-Sin Tan wrote: >> >> splited patches and test cases >> >> mc-elf-thumbfunction-bit.diff: for 1 >> mc-elf-arm-backend-bl-blx-sign-bit.diff: for 2. >> mc-elf-thumb-bl-blx-relocation-table-entry.diff: for 3. >>

Hi, I am using a cross compiler to compiler for the arm5 architecture. For this architecture it is not allowed that a destination register is also used as source register. In 2007 a patch was discussed at the mailing list, however my compiler still is producing this result. Does anyone know if this patch is actually applied? * I use the following arguments: llvm-gcc -mfpu=vfp -mlittle-endian

Hiya I am trying to compile a test case with latest LLVM 3.3 release using integrated assembler. I have looked through previous mailing discussion on this subject and it appears that perhaps by now the appropriate changes are checked-in however my test case is failing. Maybe I am missing something and not specifying appropriate options on the commandline. My setup: Host operating System: Ubuntu

I am using SimpleScalar cross-compiler 2.95.2 ( http://www.simplescalar.com/v4test.html) On Thu, Jun 18, 2009 at 3:30 PM, Anton Korobeynikov <anton at korobeynikov.info > wrote: > Hello > > > hello.s:6: Error: Unknown pseudo-op: `.eabi_attribute' > How old is your arm toolchain? > > -- > With best regards, Anton Korobeynikov > Faculty of Mathematics and