similar to: [LLVMdev] target hexagon and sparcv9 lead to llc crack

sorry, llc -march=hexagon -mcpu=hexagonv2 test.ll -o test.s works. 2012/7/3 Triple Yang <triple.yang at gmail.com>: > hi, > > does someone notice that llc options "-march=hexagon" and > "-march-sparcv9" do not work well under llvm 3.1? > > Following is a brief description: > (1) test.c file > > int cmp(int i, int j) { > return

On 7/3/2012 5:01 AM, Duncan Sands wrote: > Hi, > >> (4) llc -march=hexagon test.ll -o test.s >> >> '' is not a recognized processor for this target (ignoring processor) >> 0 llc 0x08c2512b >> Stack dump: >> 0. Program arguments: llc -march=hexagon test.ll -o test.s >> 1. Running pass 'Function Pass Manager' on module

On Tue, Jul 3, 2012 at 9:27 PM, Sebastian Pop <spop at codeaurora.org> wrote: > Hi, > > On Tue, Jul 3, 2012 at 9:48 AM, Tony Linthicum <tlinth at codeaurora.org> wrote: >> On 7/3/2012 5:01 AM, Duncan Sands wrote: >>> Hi, >>> >>>> (4) llc -march=hexagon test.ll -o test.s >>>> >>>> '' is not a recognized

Hi, > (4) llc -march=hexagon test.ll -o test.s > > '' is not a recognized processor for this target (ignoring processor) > 0 llc 0x08c2512b > Stack dump: > 0. Program arguments: llc -march=hexagon test.ll -o test.s > 1. Running pass 'Function Pass Manager' on module 'test.ll'. > 2. Running pass 'Hexagon DAG->DAG Pattern Instruction

Hi, On Tue, Jul 3, 2012 at 9:48 AM, Tony Linthicum <tlinth at codeaurora.org> wrote: > On 7/3/2012 5:01 AM, Duncan Sands wrote: >> Hi, >> >>> (4) llc -march=hexagon test.ll -o test.s >>> >>> '' is not a recognized processor for this target (ignoring processor) >>> 0 llc 0x08c2512b >>> Stack dump: >>> 0. Program

Hi Sebastian, On 19/07/12 05:57, Sebastian Pop wrote: > On Tue, Jul 3, 2012 at 9:27 PM, Sebastian Pop <spop at codeaurora.org> wrote: >> Hi, >> >> On Tue, Jul 3, 2012 at 9:48 AM, Tony Linthicum <tlinth at codeaurora.org> wrote: >>> On 7/3/2012 5:01 AM, Duncan Sands wrote: >>>> Hi, >>>> >>>>> (4) llc -march=hexagon

Hi, It seems the only one VLIW target Hexagon in LLVM 3.2 devel uses a straightforward way to emit its VLIW-style asm codes. It uses a list scheduler to schedule on DAG and a simple packetizer to wrap the emitted asm instructions. Both scheduling and packetizing work on basic blocks. so, is there any plan to implement better optimization methods such as trace scheduling, software pipelining, ...

Yang, There is work currently underway to add SW pipelining and some sort of global scheduling to Hexagon, but if there is some interest to it from other targets, it would be helpful to know. What is your involvement with this? Sergei Larin -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum. > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu

Larin, Thank you for telling me about this. Our lab is planning to design a VLIW DSP and has to make a choice between GCC and LLVM, for which I take responsibility. As we all know that GCC's codes possess a long history and has a somewhat bad learning curve, I suggest choosing LLVM. It seems now the only drawback is its poor support for VLIW architecture. And so if we can count on

the example is more like what i need,it is so nice. but,i am indefinite if "RUN: FileCheck < %t.s %s" can pass,i understand that t.s was translate from t.ll,%s means read the local source,are they the same? On Wed, Aug 22, 2012 at 1:55 PM, Triple Yang <triple.yang at gmail.com> wrote: > I did an experiment just now with a test case like: > // RUN: clang %s -S -emit-llvm

Wang, Attachment is a simple example, you may put it in test/CodeGen, and run with llvm-lit C90 It worked ok in my llvm 3.2 devel. Let know if you run into any trouble. Regards. 2012/8/27 Changcheng Wang <changcheng at multicorewareinc.com>: > hi,Yang: > if you can give me a examle,which check out a string(such as "abcd") > from a file(such as aaa.c) with fileCheck?

2012/8/28 Changcheng Wang <changcheng at multicorewareinc.com>: > hi,yang: > another question，i write a test like this: > /*****test start******/ > ; RUN: llc -march=c < %s | FileCheck %s > > ; ModuleID = 'hello.c' > target datalayout = "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64- >

hi,yang: thanks,i replaced "{helloworld}" with "helloworld" as you said,and the test run well on llvm version 3.0,but fail on llvm 162227,is it right? llvm version 162227 do not support it? your, changcheng On Tue, Aug 28, 2012 at 2:28 PM, Triple Yang <triple.yang at gmail.com> wrote: > 2012/8/28 Changcheng Wang <changcheng at multicorewareinc.com>: >>

You are welcome. /* example.c */ // RUN: clang %s -S -O0 -emit-llvm -o %t.ll // RUN: llc %t.ll -O0 -march=x86 -o %t.s // RUN: FileCheck < %t.s %s // CHECK: fct unsigned int fct(unsigned int n) { if(n>0) return fct(n-1)*n; else return 1; } /* end example.c */ /* lit.local.cfg */ config.suffixes = ['.c', '.cpp', '.ll'] targets =

hi,Yang: if you can give me a examle,which check out a string(such as "abcd") from a file(such as aaa.c) with fileCheck? i tried to write it but failed. thanks for your help! best wished! changcheng On Wed, Aug 22, 2012 at 9:30 PM, Triple Yang <triple.yang at gmail.com> wrote: > I guess so. > FileCheck has powerful extensions than just matching some strings so that >

Hi, all, I have been recently porting a backend for our experimental DSP. It has a regular register file for ALU, naming it R registers, and another register file (J registers) for memory access. Both R registers and J registers are 32-bit. Since LLVM cannot distinguish 32-bit integers or pointers during register allocation, I have to define J as 64-bit, although it's physically 32-bit. This

hi,yang: i had delete the temporary files,sorry to trouble you. it is so easy: // RUN: rm .... Regards changcheng On Wed, Aug 29, 2012 at 2:41 PM, Changcheng Wang <changcheng at multicorewareinc.com> wrote: > hi,yang: > how can i remove the temporary files? > if i can remove them,all is ok! > > yours: > > changcheng > > On Wed, Aug 29, 2012 at 2:14 PM, Changcheng

hi,yang: sorry to trouble you another time,i used your example and it run well,but a problem came,it create severel temporary files i chaged the RUN: line but failed. i changed it like this,can you give me some suggestions? // RUN: clang %s -S -emit-llvm | llc -march=c | clang -S -emit-llvm | lli | FileCheck %s thanks, best wishes, changcheng On Wed, Aug 29, 2012 at 8:39 AM, Changcheng Wang

hi,yang: thanks for your help! my net is so poor that i can not donwload your attachment. would you like to paste here,or send to my other email:200005275 at 163.com? yours changcheng On Tue, Aug 28, 2012 at 11:43 AM, Triple Yang <triple.yang at gmail.com> wrote: > Wang, > > Attachment is a simple example, you may put it in test/CodeGen, and run with > > llvm-lit C90 >

Sorry, this is the attachment. 2014-02-19 15:08 GMT+08:00 杨勇勇 <triple.yang at gmail.com>: > Thank you. > > Here is an example and the attchment contains extra files including object > file and executable file. > I want to print for example the value of "a", but lldb command "frame > variable a" displays "0" and so does "b", and