search for: powepc

...nger optional", but maybe we could flesh this text out a little to make it easier for users? Eric: do you want to add anything for out-of-tree targets after your TargetMachine changes, etc? I stumbled across http://article.gmane.org/gmane.comp.compilers.llvm.devel/83858, for example Hal: the PowePC notes have a note saying "QPX - Hal, please say a few words" :-) Alex: I think MIR is new for 3.7. Do you want to add something to the notes? Quentin: How far did your shrinkwrap work get in 3.7? If it mostly landed after the branch, maybe add it to the 3.8 (trunk) notes. Alexey: Would...

Specifying -no-implicit-float prevents LLVM from using non-GPR registers for purely integer operations. This is useful for operating systems (such as Wind River's VxWorks) that support tasks that do not save all registers on context switch. This presents an interesting problem for variadic functions that may optionally take non-integer arguments (e.g. printf style functions). Should non-GPR

...ng optimizations and codegen as follows: - It inhibits some optimizations like vectorization - It is used to determine optimal set of operations for things like inlined memcpy / memset implementations These features are common across middl-end and across various backends (x86, arm, aarch64 and powepc includes). However, x86 has one important difference: noimplicitfloat actually *changes ABI*. Even more, it breaks varargs. Here is how: it is only taken into account when receiving arguments. Essentially if we're having varargs function, then it would force it to receive floating point argume...