search for: krait

...answers to the name Rameses. This is the problem that > Renato is working on. Renato needs to be able to see the name Rameses and > map this to the correct John Smith (or at least someone very much like him). > This is the gist of what ARMTargetParser is/was doing. A good example is "krait", a CPU design from Qualcomm. Krait used to be mapped to Cortex-A15 because it has VFP4 and HDIV, but architecturally, it is a lot closer to a Cortex-A9 than an A15. So assuming that Krait == A15 means making a lot of bad optimisation decisions in the back-end, and the code performed poorly....

...That’s not quite accurate. It’s not A9+HDIV+VFP. It uses the A9 scheduling model, yes, but has its own completely distinct list of sub target features and such: Well, this is the target description in the TableGen files, and not exactly what I was talking about. when available, A9 has VFP3, while Krait has VFP4. Which brings the other side of the discussion, around the TargetParser, that the information in Clang is completely disconnected from the TableGen descriptions, but it's not relevant to the discussion. > Having the triple, or anything else outside this level of implementation de...

Hi, Hi, I was going through Code of LLVM instruction code generation for ARM. I came across VMLA instruction hazards (Floating point multiply and accumulate). I was comparing assembly code emitted by LLVM and GCC, where i saw that GCC was happily using VMLA instruction for floating point while LLVM never used it, instead it used a pair of VMUL and VADD instruction. I wanted to know if there is

...nstruction. It looks like Clang allows the formation by default, but you need to be compiling for a CPU that actually supports the instruction (the key feature is called "VFPv4". That means one strictly newer than cortex-a8: cortex-a7 (don't ask), cortex-a9, cortex-a12, cortex-a15 or krait I believe. With that I get: $ cat tmp.c float foo(float accum, float lhs, float rhs) { return accum + lhs*rhs; } $ clang -target armv7-linux-gnueabihf -mcpu=cortex-a15 -S -o- -O3 tmp.c [...] foo: @ @foo @ BB#0: @ %entry v...

I recently got a tegra TK1 and was curious how fast it was compared to my previous arm "build machine": the original arm Samsung chromebook. I timed running ninja to build just llvm in Release+Asserts using clang as the host compiler. chromebook: real 84m30.939s user 163m50.145s sys 4m0.100s TK1: real 34m7.376s user 132m44.417s sys 3m3.543s A really nice

On 18 December 2013 09:42, Tim Northover <t.p.northover at gmail.com> wrote: > That means one strictly newer than > cortex-a8: cortex-a7 (don't ask), cortex-a9, cortex-a12, cortex-a15 or > krait I believe. > Hi Tim, Cortex A8 and A9 use VFPv3. A7, A12 and A15 use VFPv4. cheers, --renato -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131218/4d77d09c/attachment.html>

...CS, extensions, ILPXX, IEEE support, CPUs with the same revision belonging to two different architectures and vice-versa. Not to mention that we have two back-ends, and one architecture (ARMv8 is split between the two). And all the brand names that people mad up during the years (StrongARM, XScale, Krait, Tegra) which map to custom features, etc. But the way we're solving this, via out TargetParser, is to create tables of default/allowed values, so that users will often get what they want, even if they don't specify most of it. I imagine that MIPS would also benefit from a TargetParser. An...

> > The Triple object will remain unchanged. > > The Tuple will be the API to handle getting/setting parameters > depending on the Triple, compiler flags, attributes, etc. > > This part doesn't seem obvious from the direction the patches are going. > There will be no string representation of all options, as that would > be impossible, or at least, highly

> > (from the context, you might have meant 'tuple' where you've written 'triple'. I'm answering based on the assumption you meant 'triple') > I did mean what I wrote. I thought I ought to check since it's very easy to mix up triples and tuples and the context sounded off. I'm glad I picked the right assumption. > > The proposed TargetTuple

On 16 September 2015 at 21:56, Jim Grosbach <grosbach at apple.com> wrote: > Why do we care about GAS? We have an assembler. It's not that simple. There are a lot of old code out there, including the Linux kernel which we do care a lot, that only compiles with GAS. We're slowly moving the legacy code up to modern standards, and specifically some kernel folks are happy to move up