On Sat, Sep 6, 2008 at 2:14 PM, David Given <dg@xxxxxxxxxxx> wrote: > The end result is that my call statement turns into: > > call func, $0, %r3, %arg1, %arg1 > > ...which is wrong. > > I assume that Clue's odd configuration is violating some assumption > somewhere, but I'm not well-enough versed with the sparse internals to > know where. It does seem odd to me that it's generating an OP_SCAST to > convert the int to a double, rather than an OP_FPCAST like in the float. Sparse assume that float and double have different size than int. On the linearized instruction level, it does not have the full type information any more. All it got is the size of the type. So it is tricky to distinguish int vs float. It generate cast to double because your third argument is a double type. Because the kernel does not have any floating pointer code. Sparse did not take floating point very seriously. The change require the instruction to have more type information than size. I am tempting to just put a full ctype pointer there. Chris -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
