llvm useability?

What about ARM target ? I mean iPhone/iPod Touch has an ARM11 with a FPE and a VFPE. Does llvm-gcc 2.2 generates better code for them ?

I'm a bit disappointed about the llvm-gcc 2.0 I tried for my iPod Touch as I saw it generated ARM code not very optimically : r7(apparently used like a frame pointer even when -fomit-frame-pointer is given) largely overused, generated code like "mov rx, imm8;orr rx, rx, imm8';add rx, rx, ry" instead of "add rx, ry, imm8;add rx, rx, imm8'", etc.

I'm also wondering if the official SDK expected for February offers a llvm-gcc as a c/c++ compiler. Which version ?

Regards.

What about ARM target ? I mean iPhone/iPod Touch has an ARM11 with a FPE
and a VFPE. Does llvm-gcc 2.2 generates better code for them ?

I don't know, I haven't tried. Again, you should try your own code if you care about performance.

I'm a bit disappointed about the llvm-gcc 2.0 I tried for my iPod Touch
as I saw it generated ARM code not very optimically : r7(apparently used
like a frame pointer even when -fomit-frame-pointer is given) largely
overused, generated code like "mov rx, imm8;orr rx, rx, imm8';add rx,
rx, ry" instead of "add rx, ry, imm8;add rx, rx, imm8'", etc.

llvm-gcc 2.0 has little to do with it, because it is just a front-end. You're asking about the status of the arm backend, which is tied to an llvm release. Code generated by llvm mainline is generally better than code generated by older releases.

I'm also wondering if the official SDK expected for February offers a
llvm-gcc as a c/c++ compiler. Which version ?

You'd have to ask apple marketing about that. This is an open source project.

-Chris