similar to: [LLVMdev] Unknown pseudo-op with -march=arm

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

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

wow... Tell me, what cross compiler can I use for ARM if I am working in a i686-Linux machine? At the same time, how I can simulate it? But the way, If I deleted the unknown pseudo-op and change section .rodata definition, I can use my stone age cross compiler. I am just wondering why it works without them. Thanks in advance. On Thu, Jun 18, 2009 at 4:26 PM, Anton Korobeynikov <anton at

> I am using SimpleScalar cross-compiler 2.95.2 (http://www.simplescalar.com/v4test.html) It's really ancient. Consider upgrading to something not from stone age :) I doubt you'll be able to assemble anything generated by, for example, with mainline gcc. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

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

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

Hello, I want to compile MiBench by clang, and the target-ISA is armv4. The code generated using llvm-2.9, clang-2.9, and arm-linux-gcc (gcc version 2.95.2), simulator is sim-panalyzer 2.0.3 . I use these commends: $ clang -O3 -o hello.ll -c -emit-llvm hello.c $ llc -O3 -o hello.s -march=arm -mcpu=strongarm1100 hello.ll $ arm-linux-gcc -O3 -march=armv4 -mcpu=strongarm1100 -static

Thanks Misha, However, I could not find the crosstool. Could you please check the name of the script? Regards, Juan Carlos On Mon, Jun 29, 2009 at 5:23 PM, Misha Brukman <brukman at gmail.com> wrote: > I have not used llvmc to build ARM binaries, but llvm-gcc does work.There's > a script to build llvm-gcc x86 -> ARM cross-compiler in > llvm/utils/crosstool/ARM/ . >

Jello Juan, The interpreter is quite useless in its current state. Try using a JIT compiler for you computer from the lli command and it should work. --Sam > >From: Juan Carlos Martinez Santos <juanc.martinez.santos at gmail.com> >To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> >Sent: Thursday, June 25, 2009 1:04:17 PM >Subject: [LLVMdev] Problems with lli

llvm/utils/crosstool/ARM/build-install-linux.sh On Tue, Jun 30, 2009 at 11:18 AM, Juan Carlos Martinez Santos < juanc.martinez.santos at gmail.com> wrote: > Thanks Misha, > > However, I could not find the crosstool. Could you please check the name of > the script? > > Regards, > > Juan Carlos > > -------------- next part -------------- An HTML attachment was

On Wed, Jul 1, 2009 at 12:01 PM, Juan Carlos Martinez Santos<juanc.martinez.santos at gmail.com> wrote: >  as -meabi=4 -o /tmp/ccYxnIEs.o /tmp/ccy6iYri.s > as: unrecognized option '-meabi=4' [snip] > Any idea what could be wrong? It's probably not finding the right assembler (i.e. using the x86-64 as instead of the arm as). -Eli

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

Hello, I just install the new newest version of LLVM. When I ran the hello.c example I got the below message. Somebody has an idea what is wrong? The problem is just with lli, the other commands worked as I expected. ********************** :~/LLVM/my-test$ lli hello.bc Tried to execute an unknown external function: i32 (i8*)* puts 0 lli 0x0861fab8 Stack dump: 0. Program arguments: lli

Did you try changing the name from Hello to MyHello or something like that? I seem to remember having a similar problem. My tutorial code names the struct MyHello and then registers it as follows: RegisterPass<MyHello> X("myhello", "My Hello World Pass"); You will likely need to change the Makefile as well. Scott On Fri, Jun 19, 2009 at 11:15 AM, Juan Carlos Martinez

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

I have not used llvmc to build ARM binaries, but llvm-gcc does work.There's a script to build llvm-gcc x86 -> ARM cross-compiler in llvm/utils/crosstool/ARM/ . 2009/6/29 Juan Carlos Martinez Santos <juanc.martinez.santos at gmail.com> > I am using the below configuration: > > ./configure --with-llvmgccdir=/home/jcmartin78/LLVM/llvm-gcc4.2 >