search for: v7r

...the Driver/Triple/Tuple knows which, depending on other > information, then they should be the ones encoding this. > > Adding an *Arch Name* ARMv7L will make no progress in understanding > what it is. Encoding the correct fields in the Triple/Tuple will, and > for that, ARMv7A or ARMv7R are the *correct* "arch names". > > cheers, > --renato > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev -------------- next part -------------- An...

...all. As far as I could test, all major architectures (v4/v5/v6 + v7-A-R-M), although I'm still fighting with some Thumb code generation. Could be my old gcc/binutils version (that still doesn't even recognizes cortex-R4). You should check that yours is really new (at least 2010) if you want v7R support. >>  3/ what are the supported tools for ARM targets: >>      a/ llvm-gcc (gcc 4.2)? >>      b/ dragonegg (gcc 4.5)? >>      c/ clang? I haven't tested dragonegg, but clang and llvm-gcc do the job. llvm-gcc seems to be more in sync with the ARM backend (for obv...

> There isn't one at the moment, ideally it should figure it out, but I haven't looked much into it - it may be that this isn't working yet. I should say that I'm still a bit confused: Is it possible to build for ARM CPUs now? 1/ from which hosts (x86-*-* ?) 2/ for which targets (arm-*-* ?) 3/ what are the supported tools for ARM targets: a/ llvm-gcc (gcc 4.2)?

...t that means RaspberryPi, and add a number of > FIXMEs to the parser: > 1. To remove both L/B variants as aliases > 2. To implement L/B in getCanonical in the same way as EB/BE > 3. But only once Triple/Tuple can replace the "v7l" -> "v7a when > Linux" OR "v7R when RTLinux" logic (I have no idea how this will pan > out). > > To know about the progress on Tuple, check with Daniel Sanders and > Eric Christopher (CC'd). > > Adding this hack to the Driver now could make the mess even worse at this stage. > > cheers, > -...