search for: ha16

Hello Tom, > I took a look at lib/CodeGen/SelectionDAG/LegalizeDAG.cpp and it > doesn't look like there is an Expand operation implemented for > ISD::Constant. I think you'll either need implement Expand for > ISD::Constant or Custom lower it in your backend. thank you for that information. This exactly is what I feared. Well I did some more mostly unguided hacking and these

...for (i = 0; i < 1000; ++i) > Array[i] += X; > } > > Compile with -O3 on OS/X gave me this: > > _test: > mflr r5 > bcl 20,31,"L00000000001$pb" > "L00000000001$pb": > mflr r2 > mtlr r5 > addis r4,r2,ha16(L_Array$non_lazy_ptr-"L00000000001$pb") > li r2,0 > lwz r9,lo16(L_Array$non_lazy_ptr-"L00000000001$pb")(r4) > li r4,1000 > mtctr r4 > L9: > lwzx r7,r2,r9 ; load > add r6,r7,r3 ; add >...

...c-750-linux-gnu-as --version GNU assembler 2.16.1 However, the xgcc build during the seems to generate instructions that are not understood by the assembler. I forced xgcc to output assembly and tried to use the assembler on the result manually. There are instructions like this one "lis 30, ha16(completed.5554.b)" which are not understood apparently? Should this instruction be understood by the assembler? Thanks, Maarten -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: crtstuff.s URL: <http://lists.llvm.org/pipermail/llvm-...

...y setup then - I don't work with the PPC parts anyways. The system assembler is as --version GNU assembler (GNU Binutils for Ubuntu) 2.18.93.20081009 ... This assembler was configured for a target of `powerpc-linux-gnu'. perhaps it is too old? It chokes on the assembly lines: lis 3, ha16(.L.str) la 3, lo16(.L.str)(3) That assembly is generated out of a trivial hello world: @.str = private constant [14 x i8] c"Hello, world\0A\00" define i32 @main() nounwind { entry: %call = call i32 (i8*, ...)* @printf(i8* getelementptr inbounds ([14 x i8]* @.str, i32 0, i32 0))...

On Jan 5, 2011, at 1:47 PM, Erik de Castro Lopo wrote: > Kalle Raiskila wrote: > >> And I probably should file a bug. Is ppc32 still maintained? > > I have no concrete knowledge of this, but llvm compiles > and passes all tests on ppc32, so it seems to be maintained. > About once a week I grab the latest SVN head and check this. It is run by one of the automatic

On Tue, 4 May 2004, Patrick Flanagan wrote: > I was able to run through all the C/C++ benchmarks in SPEC using LLVM. > I'm on OS X 10.3.3. I did a quick comparison between LLVM (latest from > CVS as of 4/27) and gcc 3.3 (Apple's build 20030304). For simplicity's > sake, the only flag I used was -O3 for each compiler and I was using > the C backend to generate native

I was able to run through all the C/C++ benchmarks in SPEC using LLVM. I'm on OS X 10.3.3. I did a quick comparison between LLVM (latest from CVS as of 4/27) and gcc 3.3 (Apple's build 20030304). For simplicity's sake, the only flag I used was -O3 for each compiler and I was using the C backend to generate native code for PPC. Most of the LLVM results were close to gcc

On May 17, 2011, at 9:47 AM, Maarten Faddegon wrote: > LLVM is building ok, but the second step: building llvm-gcc fails with a > rather strange error which I appended to the end of this e-mail. > Am I doing something wrong or is this a bug? Looks like you don't have an assembler for your target installed that llvm-gcc can find. -eric -------------- next part -------------- An

...amples, for example: // Arbitrary immediate support. Implement in terms of LIS/ORI. def : Pat<(i32 imm:$imm), (ORI (LIS (HI16 imm:$imm)), (LO16 imm:$imm))>; // ADD an arbitrary immediate. def : Pat<(add GPRC:$in, imm:$imm), (ADDIS (ADDI GPRC:$in, (LO16 imm:$imm)), (HA16 imm:$imm))>; // OR an arbitrary immediate. def : Pat<(or GPRC:$in, imm:$imm), (ORIS (ORI GPRC:$in, (LO16 imm:$imm)), (HI16 imm:$imm))>; // XOR an arbitrary immediate. def : Pat<(xor GPRC:$in, imm:$imm), (XORIS (XORI GPRC:$in, (LO16 imm:$imm)), (HI16 imm:$imm))>;...

Are there any examples of using tablegen to generate multiple machine instructions from a single pattern? Or do these cases always have to be manually expanded? -Dave

...function: int Array[1000]; void test(int X) { int i; for (i = 0; i < 1000; ++i) Array[i] += X; } Compile with -O3 on OS/X gave me this: _test: mflr r5 bcl 20,31,"L00000000001$pb" "L00000000001$pb": mflr r2 mtlr r5 addis r4,r2,ha16(L_Array$non_lazy_ptr-"L00000000001$pb") li r2,0 lwz r9,lo16(L_Array$non_lazy_ptr-"L00000000001$pb")(r4) li r4,1000 mtctr r4 L9: lwzx r7,r2,r9 ; load add r6,r7,r3 ; add stwx r6,r2,r9 ; store...

Hi All, I try to build a cross-compiler that compiles for powerpc but runs on my pentium. As a base I used the arm cross-compiler script but changed: CROSS_HOST="x86_64-unknown-linux-gnu" CROSS_TARGET="powerpc-linux" CROSS_MARCH="750" LLVM is building ok, but the second step: building llvm-gcc fails with a rather strange error which I appended to the end of this

Looking through the archives I have seen talk of making CPU specific optimisations for Vorbis, a la MMX/3DNow!/SSE. The feeling I gather is to wait until something is working well in C before committing to any kind of specific optimisation. What if oft used and needed DSP functions were identified and standardised DSP functionality be written for Vorbis? This would seperate the basically

...VMbuilder.research.nokia.com> > Content-Type: text/plain; charset="UTF-8" > > On ons, 2011-05-18 at 16:04 +0200, ext Maarten Faddegon wrote: > > I try to build a cross powerpc compiler, but llvm-gcc fails. > > > There are instructions like this one "lis 30, ha16(completed.5554.b)" > > which are not understood apparently? > > If I recall correctly, this was a bug when generating 32bit ppc assembly > on linux. 64bit assembly might work better on linux. > > > kalle > > -- > "Modern computing machines are very complex...