search for: llvmalignment

While writing bindings to LLVM for another language via the c api I noticed that LLVMAlignment and LLVMStackAlignment do not use 1<<x like all the others, but 31<<x and 7<x respectively (see below, or here: http://llvm.org/docs/doxygen/html/Core_8h_source.html#l00148). It's likely this is as it is intended, but it does look out-of-place enough that I thought it might be...

Thank you guys for the fast replies (!), now I can continue without worrying about it. -- Moritz On 2/17/2013 1:46 PM, Daniel Murphy wrote: > These values are masks for numbers. LLVMAlignment uses 5 bits, so the > mask is 31 (0b11111) and these bits (16-20) cannot be used by other > flags so the next available bit is 21. Same thing for LLVMStackAlignment. On 2/17/2013 1:53 PM, Benjamin Kramer wrote: > This is intentional. LLVMAlignment is not just a bit, it's a 5 bit va...

On Thursday 10 February 2005 21:47, Markus F.X.J. Oberhumer wrote: > In order to get more familiar with the llvm sources I've recently > decided to try to add support for the always_inline and noline function > attributes. I believe it is better to let the compiler decide when or not to inline a function. Most of the times a developer goes overboard with inlining and ends up with a